Big problem using the amavisd-new package crashing: debug log
Hello,
We use amavisd-new in our control panel to have all our mail passed to
clamav and spamassassin for virus and spam scanning.
Since Etch is out, we are experiencing very bad problems with the
current stable Amavisd-new package that often crashes. We were up to the
extremes to have a cronjob to check if amavis is crashed or not...
We finally had a debug log of it, that I just pasted bellow. Before I
send it as a bug report against the amavisd-new package in the BTS, I
wanted to have other people's opinion about this trouble, in case we did
a mistake in the configuration or something like that.
Please let me know if you experienced the same errors, or if you think
it's a misconfiguration on our side (which is, to me, very unlikely, as
this is quite about the same configuration as for Sarge, adapted to the
new version of the package).
Here is the log:
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) lookup_re("xue@mountainzone.com"), no matches
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) query_keys: xue@mountainzone.com, xue@, mountainzone.com,
.mountainzone.com, .com, .
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) lookup_hash(xue@mountainzone.com), no matches
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) lookup (score_sender<xue@mountainzone.com>) => undef,
"xue@mountainzone.com" does not match
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) SpamControl: calling spam scanner
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) spam_scan: DSPAM not available, skipping it
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) timer set to 314 s for SA (was 472 s)
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) calling SA parse, SA version 3.1.7-deb
Nov 9 13:50:55 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) CALLING SA check
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4380]:
Net::Server: 2007/11/09-13:50:56 Server closing!
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04389-02-23) child_finish_hook: invoking DESTROY methods
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04389-02-23) Amavis::Cache DESTROY called
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) Amavis::DB::SNMP DESTROY called
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) Amavis::DB::SNMP DESTROY called
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) Amavis::In::SMTP DESTROY called,
sock=Net::Server::Proto::TCP=GLOB(0xa4c50e8), normal=0
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) ESMTP> 421 4.3.2 Service shutting down, closing channel
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) switch_to_client_time 480 s, smtp response sent
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) Amavis::TempDir::DESTROY called
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) Amavis::In::SMTP DESTROY called,
sock=Net::Server::Proto::TCP=GLOB(0xa4c50e8), normal=0
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) ESMTP> 421 4.3.2 Service shutting down, closing channel
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) switch_to_client_time 480 s, smtp response sent
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4389]:
(04389-02-23) Amavis::TempDir::DESTROY called
Of course, the important bit is here:
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) Amavis::In::SMTP DESTROY called,
sock=Net::Server::Proto::TCP=GLOB(0xa4c50e8), normal=0
Nov 9 13:50:56 mx.node6503.gplhost.com /usr/sbin/amavisd-new[4388]:
(04388-02-25) ESMTP> 421 4.3.2 Service shutting down, closing channel
Please let me know what you think of this. I'd be very happy if we can
find where is the trouble, this is annoying us a lot.
Regards,
Thomas Goirand
Reply to: