https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6303
--- Comment #5 from Guido Allione <[email protected]> 2010-02-08 05:09:18 UTC --- (In reply to comment #4) > (In reply to comment #3) > > 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? > > > Ops... if you know the best configuration, welcome! Can you get my one or two > example (or link for this example)?? > > > > Anyway, back to the reported problem. There are no defunct (zombie) > > processes on your system according to the output of top(1). > > > > True! But is sure that the idle CPU are high for this problems (I don't know > if > is for spamd, amavis or other....) > > this morning after same problems, I have search parent (PPID) of spamd defunct > process. The parent was /usr/sbin/spamd -d -c -L -r /var/run/spamd.pid . > I stop the deamon and after, the same defunct process after change parent in > the PPID 1 (init). Is correct?? > > > > 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. > > > > I'm sorry, i have restart server after read this part. one or two day (next > problems) and I test with lsof the process join this close_wait > > > 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?). > > The system are openSUSE 11.1 (i586) with amavis, spamassassin etc standard > (with yast utility and NOT force manual version!). > The volume work into drbd disk for fault-tollerance. > > The only events join this problems is backup but are not sure! The backup is a > tar command and mysql-dump and the cpu go tu 2 or 3. > > Thank's. News for this problem? Thank's -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
