MailScanner defunct processes

[Julian Field]

Dave Jones wrote:
> I have installed the latest beta code 4.69.6-1 to test the latest
> feature that Julian added for us.  I have installed this version on 4
> servers with nearly identical configurations.  Three of the four
> servers are running perfectly.  Two of these servers are identical.
> One of the 2 twin servers (call it "server2") is running perfectly but
> the second one starts up it's children and 15 or 16 of the 20
> MailScanner processes go defunct after apparently running through a
> batch of processing. Four to five MailScanner processes appear to be
> normal either "waiting for messages", "checking with SpamAssassin", or
>  "MCP checks", etc.
>
> [root at server2 MailScanner]# ps -ef | grep MailScanner
> root      8594     1  0 20:56 ?        00:00:00 MailScanner: starting child
> root     17727  8594  2 21:06 ?        00:00:03 MailScanner: checking
> with SpamAssassin
> root     18639  8594  0 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     18723  8594  0 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     18787  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     18856  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     18929  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     19012  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     19125  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     19188  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     19259  8594  1 21:07 ?        00:00:00 [MailScanner] <defunct>
> root     19333  8594  1 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19407  8594  2 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19478  8594  2 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19554  8594  2 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19656  8594  3 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19737  8594  3 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19805  8594  5 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19871  8594  8 21:08 ?        00:00:00 [MailScanner] <defunct>
> root     19925  8594 10 21:08 ?        00:00:00 MailScanner: checking
> with SpamAssassin
> root     19992 19925  0 21:08 ?        00:00:00 MailScanner: checking
> with SpamAssassin
> root     19993  8594  0 21:08 ?        00:00:00 MailScanner: waiting
> for messages
> root     19996 17727  0 21:08 ?        00:00:00 MailScanner: checking
> with SpamAssassin
> [root at server2 MailScanner]# MailScanner --debug
> In Debugging mode, not forking...
> Trying to setlogsock(unix)
> SpamAssassin temp dir = /mnt/ramdisk/SpamAssassin-Temp
> Use of uninitialized value in concatenation (.) or string at
> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin.pm line 1088.
> Use of uninitialized value in concatenation (.) or string at
> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin.pm line 1090.
> Building a message batch to scan...
> Have a batch of 30 messages.
> Error PPS:0
>   
There's your problem. I don't know what is generating "Error PPS:0" but 
that's certainly the problem. Do a
    grep -rl 'Error PPS' /usr/lib/perl5
and see what it says.

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.