https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6303
Mark Martinec <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|Undefined |3.3.1 --- Comment #3 from Mark Martinec <[email protected]> 2010-01-27 08:22:06 UTC --- So you are indeed running both amavisd as well as spamc/spamd. Your postfix feeds mail first to amavisd, which returns it to postfix on port 10025, which then spawns spamc and feeds mail to it through a pipe, which in turn transfers it to spamd on port 783, and then spamc (based on the result) pipes the message to a mail submission program 'sendmail', which stores the message into a maildrop queue, to be picked up by a postfix pickup daemon for further delivery. Ugh, doable, but quite complicated and not very efficient. Since you are already running amavisd-new, why do you not let it call SpamAssassin directly, and save yourself and your mailer the trouble of dealing with two content filters? Anyway, back to the reported problem. There are no defunct (zombie) processes on your system according to the output of top(1). There are indeed lots of open TCP sessions to localhost port 783 in a CLOSE_WAIT state. Unfortunately you have not provided a full list of processes as reported by ps(1). According to the port number and the CLOSE_WAIT state I can assume each of these correspond to an existing spamd child process, where its spamc client has long gone, but for some reason spamd failed to close its end of the socket. This can be confirmed by a lsof utility and ps. It would be interesting to know what ps reports on a state of these spamd child processes. The next step would be to run spamd with debugging enabled, and when the situation reoccurs, see what were the last logged entries of each of the hung processes, and to what event on the system these correspond (nfs trouble? disk down? network outage? backup? running out of swap space?). -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
