Re: Process did not exit cleanly.
This is a just a caution to anyone updating their OS's or more precisely, versions of perl.
This is a bug as best I can tell to do with mailscanners handling of spamassassin, if SA is disabled, MS appears to work fine, else it constantly bails as below, leaving copies of mail and all in work dirs, mail is however still delivered, so appears nothing is lost.
It's down to modern versions of perl, perl modules, but it seems not enough of us use 5.10.1 or greater (no issue with 5.10.0), so no other people see it for it to be given any real urgency at present. (we stopped using mailscanner, will use it again once this bug is fixed) Julian was made aware of two months or more ago, but is unable to reproduce it.
Since most of you use antiquated CentOS and Debian versions, you likely wont be stung for some years yet :)
But anyone using current Gentoo, Slackware and report of Archlinux as well, be forewarned.
On Wed, 2010-12-29 at 08:51 +0200, Paul Malherbe wrote:
I am continually getting the following messages in my messages file:
Dec 29 02:44:20 server MailScanner: Process did not exit cleanly, returned 1 with signal 0
Dec 29 02:44:35 server last message repeated 3 times
Dec 29 02:44:40 server MailScanner: Process did not exit cleanly, returned 0 with signal 13
How can I find out what is causing them?
I have the following versions running on a vmware virtual server:
Linux server 2.6.35-gentoo-r12 #1 Thu Dec 2 09:26:26 SAST 2010 i686
Intel(R) Core(TM)2 Quad CPU Q8400 <at> 2.66GHz GenuineIntel GNU/Linux
Perl version 5.012002 (5.12.2)
MailScanner version 4.79.11
SpamAssassin version 3.3.1
Postfix version 2.7.1
Clamav version 0.96.5
+27 (0) 21 6711866
+27 (0) 82 9005260
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner mailing list
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!