Are you trying to run it on an unsupported architecture? We support x86_64, and I believe it’ll work on i386. Pretty sure I made all of our procmail-wrapper packages work on both.
Cheers Joe,
no, it’s a VPS from Binary Lane in Aus, nothing special about it.
Been running Virtualmin and Webmin for a while, had small issues with proemial but never quite figured it out.
had some issues with RAM a couple months ago, bumped it up to 4 cores, 8GB RAM
But to answer the question, it’s an x86_64 based VPS
Also, what output do you get from running procmail -v? Also, what are the outputs when you run /usr/bin/procmail-wrapper and ls -lsa /usr/bin/procmail-wrapper?
Thanks for the input everyone, here are the requested answers-
root@host:~# uname -I
x86_64
root@host:~# uname -a
Linux host.domain.com.au 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
root@host:~#
Also –
root@host:~# procmail -v
procmail v3.23pre 2001/09/13
Copyright (c) 1990-2001, Stephen R. van den Berg <srb@cuci.nl>
Copyright (c) 1997-2001, Philip A. Guenther <guenther@sendmail.com>
Submit questions/answers to the procmail-related mailinglist by sending to:
<procmail-users@procmail.org>
And of course, subscription and information requests for this list to:
<procmail-users-request@procmail.org>
Locking strategies: dotlocking, fcntl()
Default rcfile: $HOME/.procmailrc
It may be writable by your primary group
Your system mailbox: /var/mail/root
root@host:~#
root@host:~#
root@host:~# /usr/bin/procmail-wrapper
Illegal instruction (core dumped)
root@host:~#
root@host:~#
root@host:~# ls -lsa /usr/bin/procmail-wrapper
1388 -rwsr-xr-x 1 root root 1417756 Jan 27 2022 /usr/bin/procmail-wrapper
root@host:~#
That x86_64 repeated message also happens on an Oracle Linux VM at the same hosting company, so I don’t think it is significant.
I installed some PHP updates, rebooted, adjusted some firewall rules (external firewall) and it seems happier now, but I do wish I could fix it or at least know what to do next time…
It’s not clear what exactly is wrong! But I’d suggest trying to build it on a similar testing system and see how it goes. The program itself is quite basic – just a wrapper.