I've upgraded a box to fedora 5 today. There were no application upgrades as the core 4 was running Postfix 2.2.10, Amavisd-new 2.4, Spamassassin 3.1.1.
Things look like they are OK, but the Postfix queue is backing up. Turning up the log level I can see the following time-out problem: May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) (!) ESMTP ABORTING: timed out during waiting for input from client May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) TempDir::strip: /var/amavis/tmp/amavis-20060505T010059-02152 May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) rmdir_recursively: /var/amavis/tmp/amavis-20060505T010059-02152/parts, excl=1 May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) TIMING [total 480018 ms] - lookup_sql: 10 (0%)0, SMTP pre-DATA-flush: 5 (0%)0, unlink-0-files: 480004 (100%)100, rundown: 0 (0%)100 May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) SMTP session over, timer stopped May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) (!) ESMTP: NOTICE: ABORTING the session: timed out during waiting for input from client May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) ESMTP> 421 4.3.2 Service shutting down, timed out during waiting for input from client May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) prolong_timer smtp response sent: timer set to = 480 s May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) extra modules loaded: Mail/SpamAssassin/Plugin/TextCat.pm May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) exiting process_request May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) post_process_request_hook: timer was not running May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) idle_proc, bye: was busy, 480010.5 ms, total idle 0.234 s, busy 1463.178 s May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) load: 100 %, total idle 0.234 s, busy 1463.178 s May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) idle_proc, hi : was idle, 26.4 ms, total idle 0.261 s, busy 1463.178 s May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) loaded base policy bank May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) lookup_ip_acl (inet_acl): key="127.0.0.1" matches "127.0.0.1", result=1 May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) process_request: fileno sock=14, STDIN=0, STDOUT=1 May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) prolong_timer new request - timer reset: timer set to = 480 s May 5 01:25:22 mx1 amavis[2152]: (02152-03-2) process_request: suggested_protocol="" on TCP I'm assuming that this is spamassassin timing out because when I run with debug-sa it gets as far as these messages and stops: [3159] dbg: auto-whitelist: post auto-whitelist score: 2.906 [3159] dbg: rules: running body-text per-line regexp tests; score so far=2.906 [3159] dbg: uri: running uri tests; score so far=2.906 [3159] dbg: rules: running raw-body-text per-line regexp tests; score so far=2.906 [3159] dbg: rules: running full-text regexp tests; score so far=2.906 [3159] dbg: check: is spam? score=2.906 required=5 [3159] dbg: check: tests=MISSING_SUBJECT,NO_REAL_NAME,NO_RECEIVED,NO_RELAYS,TO_CC_NONE [3159] dbg: check: subtests=__HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__NONEMPTY_BODY,__SANE_MSGID,__SARE_WHITELIST_FLAG,__SOBER_P_MSGID,__UNUSABLE_MSGID I've been round and done the obvious version and perms checking and that config files have not been overwritten. All looks as it should - so far. I could do with a pointer of where to look next as I'm not sure where this problem is. thanks Alan ------------------------------------------------------- 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/
