https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6303
--- Comment #7 from Guido Allione <[email protected]> 2010-02-10 18:05:18 UTC --- (In reply to comment #6) > > > 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 me > > one or two example (or link for this example)?? > > Unless you explicitly disable spam checking in amavisd.conf (by > @bypass_spam_checks_maps or its derivatives), amavisd is calling > SpamAssassin by default. You may need to adjust score thresholds > and what should happen to spam, but that is basically all. > > Something like: > @bypass_spam_checks_maps = (); > $sa_tag2_level_deflt = 5.0; # labels passed mail as spam > $sa_kill_level_deflt = 8.5; # blocks & quarantines at this level > $sa_spam_subject_tag = '***SPAM*** '; > $final_spam_destiny = D_DISCARD; > $spam_quarantine_to = 'spam-quarantine'; > $spam_quarantine_method = 'local:spam-%m.gz'; > > or to just label spam but deliver anyway: > $final_spam_destiny = D_PASS; > it's alsoit is already thus in my amavis.conf it is present this row: @bypass_spam_checks_maps = (1); and, if i restart amavis, into /var/log/mail it is present this log: Feb 10 18:50:24 xxxx amavis[24757]: ANTI-SPAM code NOT loaded Feb 10 18:50:24 xxxx amavis[24757]: ANTI-SPAM-SA code NOT loaded > > > > Anyway, back to the reported problem. There are no defunct (zombie) > > > processes on your system according to the output of top(1). > > 86.8%id - idle is good, host is only lightly loaded. > yes, but all mail is delivery after many minutes (and not second as usual). I think's burn for this problem (CPU or spamd defuct... I don't know). > > 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?? > > Yes, this is correct behaviour. It is a function of the init process to > garbage collect all orphaned process entries and clear them. After a short > while the reparented defunct entries should be removed by the init process. > > So that spamd parent process which you had to kill was the culprit. > It failed to collect exit statuses of (i.e. to ripe) its child processes > which had already terminated some time ago. > > Don't know why this would happen. It was stuck for some reason, or lost track > of its child processes. Was this process dormant when you killed it, or was > it spinning CPU? Was it still able to accept connections and process them? > Running it with debugging enabled and examining log from such process > when a problem reoccurs might shed some light. > The next incident, verify if idle process are on defunct process. But after killed, the CPU averange not change. I don't know if it still also accept connection. How I verify? :-( .... help me for activate, read and send you this debugging. Excuse me, but not know debug procedure. (or done me sample howto link). > > > > 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 > > > > 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. > > For some reason that parent spamd process which you had to kill got stuck > when you are running a backup. Now that you mention a mysql dump, perhaps > this causes bayes/awl tables to be locked during a backup, thus blocking > spamd operations. No. postfix use mysql table but not spamassasin. If is this the question. For now, thank's for this Comment'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.
