Hello Mark Mark Martinec wrote: > Thomas, > >>>> Since a few days I see many strange log entries like: >>>> amavis[64239]: Net::Server: Ran out of accept retries! >>>> amavis[64153]: Net::Server: Accept failed with 29 tries left: Software >>>> caused connection abort > >>> $ man 2 accept >>> [ECONNABORTED] >>> A connection arrived, but it was closed while waiting on the listen >>> queue. > >> content_filter = lmtp-amavis:[127.0.0.1]:10024 >> >> lmtp-amavis unix - - n - 10 lmtp >> -o lmtp_data_done_timeout=1200 >> -o lmtp_send_xforward_command=yes >> -o disable_dns_lookups=yes >> -o max_use=20 > >> No. No proxy, no milter. >> no firewall rules. >> I have five equal machines but only one shows this behaviour. > > Just guessing: could it be that you have less than 10 (maxproc > in your master.cf) amavisd child processes ($max_servers) ? > If yes, Postfix could time out its excessive connect attempts > before they get a chance to get accepted by amavisd. > lmpt postfix service is known to be quite persistent in keeping > its connection open for a long time even when idle, when > session caching is enabled. >
No $max_servers are set to 10. A very old running amavisd master process has caused it. It wasn't killed with amavisd stop script. I didn't spot it the first time with ps output. After i killed it, Net::Server: Accept failed with xx tries left: Software caused connection abort are gone. Sorry false alarm. Stupid. Regards Thomas vogt ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ 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/
