Danita, > My biggest issue with these "lazy amavis processes" as I've come to > call them, is that I can never seem to find a common solution that will > fix it each time, and also because it's generally so far between > incidents (I've had it happen about 5 times in the 3 or so years I've > used this setup) that when it happens I start pulling my hair out. And > then it almost seems like as suddenly as the problem occurs, it goes > away. I really have no idea if the clamav issue had anything at all to > do with the bigger problem, but it did eventually all get sorted out.
To investigate such mystery cases, it pays off to keep a debug log for the last few days, then throw it away automaticaly. Syslog allows to have multiple logs at different syslog priorities, so I keep one essential amavisd log collected at user.notice level for the archival purposes, and I have a second throw-away log at user.debug level for forensic purposes. (actually I also have an intermediate log to be able to analyse timing reports) /etc/syslog.conf: user.notice /var/log/amavisd.log user.info /var/log/amavisd-info.log user.debug /var/log/amavisd-debug.log amavisd.conf: $log_level = 5; # verbosity 0..5 $DO_SYSLOG = 1; # log via syslogd $syslog_facility = 'user'; $syslog_priority = 'debug'; Mark ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
