On Sunday 30 July 2006 11:37, Benu wrote: > I am running postfix2.2.8 +mysql+sasl+tls+cyrus plus spamassassin-3.1.4, > clamav-0.87, dspam-3.6.2, razor-2.82-14, pyzor-0.4.0-9, dcc-1.3.26-1.53, > and amavis-new 2.4.2 configuration on FC4. > > There are no complaints from amavisd debug, amavisd debug-sa or > spamassassin --lint --debug > > This configuration WAS working before I decided it was time to update the > FC4 system. > > Now, I have observed the following and have been able to rollback the > changes from the updates: > > (1) amavisd's child processes stop responding after calls to spamassassin, > whence, 127.0.0.1 timeouts > (2) the command 'service amavisd stop' only shutdown the master amvasid > process > (3) the spamassassin rpm calls /etc/dcc/dccproc instead of /var/dcc/dccproc > (4) With spamassassin rpm install postfix defer queue fills with messages > labeled: "SPAM (in reply to end of DATA command )) > (5) Changing postfix's smtp-amavis master.cf entries from LMTP to SMTP did > not fix the "end of DATA" errors > (6) Removing spamassassin the rpm and reloading perl related > Mail::Spamassassin modules produces the following in postfix's defer > queue: "1E1052F60937 2634 Fri Jul 28 10:56:05 [EMAIL PROTECTED] (delivery > temporarily suspended: connect to 127.0.0.1[127.0.0.1]: read timeout)" > (7) When comparing the command 'lsof|grep clamav' output from another > working system (FC5) with this system only the following stands out: > amavisd 17996 clamav 12u unix 0xc2ea38c0 1866467 > socket 237 amavisd 17996 clamav 13u sock 0,4 > 1837129 can't identify protocol > 238 amavisd 17996 clamav 14u IPv4 1866337 > TCP hostname.domain.net:10024->hostname.domain.net:48261 (CLOSE_WAIT) > (8) Using command 'netstat -nat|grep 10024' reveals over 100 processes > like: tcp 1 0 127.0.0.1:10024 127.0.0.1:53816 > CLOSE_WAIT > > Is any of this familiar to anyone? I can supply amavisd.conf, postfix's > conf files, etc. if that will help. > > Regards > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > AMaViS-user mailing list > AMaViS-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amavis-user > AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 > AMaViS-HowTos:http://www.amavis.org/howto/
It appears that the timeouts were occurring because of bayes MySQL failure that was quite. Although I had performed many amavisd debug-sa and spamassassin --lint the bayes failure was not apparent. For whatever reason that I had at the time, in local.cf, I had bayes_store_module Mail::SpamAssassin::BayesStore::SQL it should have been BayesStore::MySQL instead. After I made that change to bayes in local.cf, everything returned to "normal", meaning no timeouts. thanks ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
