Hi,
I've run (find /var/spool/amavis -type d -name 'amavis-*' -prune -mmin +30
-exec rm -rf {} \;
Restarted amavisd-new, clamAV and postfix, and it seems to work OK now,
But I want to avoid this in the future and find the cause of that bug.
These are the versions installed on my server:
amavisd-new-20030616p9-3.6 Tue Sep 6 16:46:59 2005
spamassassin-2.64-3.2 Tue Sep 6 16:46:51 2005
perl-spamassassin-2.64-3.2 Tue Sep 6 16:46:30 2005
As far as I can see I've started to get "status=deferred" messages at Dec 22
04:24:01 and this message repeated every 16 min.
not only for [EMAIL PROTECTED] user but also for other users:
-----------------------------------------------------------------
Dec 22 04:24:01 mail postfix/pipe[24644]: 054301BB9B: to=<[EMAIL PROTECTED]>,
relay=cyrus, delay=231660, status=defer
red (temporary failure)
Dec 22 04:24:01 mail postfix/pipe[24641]: 49FB41F5F9: to=<[EMAIL PROTECTED]>,
relay=cyrus, delay=142821, status=defer
red (temporary failure)
Dec 22 04:24:01 mail postfix/pipe[24644]: 9D4321F5CA: to=<[EMAIL PROTECTED]>,
relay=cyrus, delay=230213, status=defer
red (temporary failure)
Dec 22 04:24:31 mail postfix/smtp[24635]: connect to 24.on.cc[66.246.195.41]:
Connection timed out (port 25)
Dec 22 04:24:31 mail postfix/smtp[24635]: 2DD121F5CB: to=<[EMAIL PROTECTED]>,
relay=none, delay=202768, status=deferred (connect t
o 24.on.cc[66.246.195.41]: Connection timed out)
Dec 22 04:24:31 mail postfix/smtp[24637]: connect to
linux.uovs.ac.za[196.21.181.2]: Connection timed out (port 25)
Dec 22 04:24:31 mail postfix/smtp[24639]: connect to 24.on.cc[66.246.195.41]:
Connection timed out (port 25)
Dec 22 04:24:31 mail postfix/smtp[24640]: connect to
linux.uovs.ac.za[196.21.181.2]: Connection timed out (port 25)
Dec 22 04:24:31 mail postfix/smtp[24637]: 801141F5E5: to=<[EMAIL PROTECTED]>,
relay=none, delay=202450, status=deferred (
connect to linux.uovs.ac.za[196.21.181.2]: Connection timed out)
Dec 22 04:24:31 mail postfix/smtp[24639]: 8F64F1C4EE: to=<[EMAIL PROTECTED]>,
relay=none, delay=202451, status=deferred (connect t
o 24.on.cc[66.246.195.41]: Connection timed out)
Dec 22 04:24:31 mail postfix/smtp[24640]: E771C1B44E: to=<[EMAIL PROTECTED]>,
relay=none, delay=202770, status=deferred (
connect to linux.uovs.ac.za[196.21.181.2]: Connection timed out)
-------------------------------------------------------------------
It seems that some users got this message and some got their mail as they
should.
I see "TROUBLE" message on Dec 25 22:45:48 (See below):
----------------------------------------------------------------
Dec 25 22:45:48 mail amavis[27727]: (27727-04) TROUBLE in check_mail:
decoding2-get-file-types FAILED: timed out
Dec 25 22:45:48 mail amavis[27727]: (27727-04) PRESERVING EVIDENCE in
/var/spool/amavis/amavis-20051225T222829-27727
Dec 25 22:45:48 mail amavis[27727]: (27727-04) TIMING [total 627447 ms] - SMTP
EHLO: 1 (0%), SMTP pre-MAIL: 0 (0%), SMTP pre-
DATA-flush: 3 (0%), SMTP DATA: 46 (0%), body hash: 1 (0%), mime_decode: 31
(0%), rundown: 627363 (100%)
Dec 25 22:45:49 mail postfix/smtpd[28010]: too many errors after RCPT from
bzq-224-205.red.bezeqint.net[212.179.224.205]
Dec 25 22:45:49 mail postfix/smtpd[28010]: disconnect from
bzq-224-205.red.bezeqint.net[212.179.224.205]
Dec 25 22:45:50 mail postfix/smtpd[28010]: connect from
mr1.haifa.ac.il[132.74.1.39]
-------------------------------------------------
Any thoughts/suggestions?
Regards,
Leon
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary V
Sent: Monday, December 26, 2005 6:53 PM
To: [email protected]
Subject: Re: [AMaViS-user] RE: How to clean /var/spool/amavis directory
automatically
lkolchin wrote:
> I'm getting a lot of the following messages in the logs:
> Dec 26 15:07:04 mail postfix/smtp[17889]: C73D183AEA: to=<[EMAIL PROTECTED]>,
> orig_to=< [EMAIL PROTECTED] >, relay=127.0.0.1[127.0.0.1], delay=141564,
> status=deferred (lost connection with 127.0.0.1[127.0.0.1] while sending end
> of data -- message may be sent more than once)
> I'm using postfix along with amavisd-new (SA and ClamAV) on SLES9 machine,
> latest updated versions.
I'm showing the latest SUSE packaged version of amavisd-new is 20060616-p9,
which is rather old (but still should be able to process mail). Do you
know what version of amavisd-new you are actually running?
http://www.novell.com/products/linuxpackages/enterpriseserver/i386/index_all.html
> I've seen on the list archive, that someone suggested to "
> Add status code 2 along with 0 to the success "if" branch
> (file ./amavis/av/sophos), or upgrade to amavisd-new-20021227-p2.
> "
That looks ancient and unrelated to me. There are a lot of possible
reasons for amavisd-new to not work properly, often it is a problem
with one of the external Perl modules or external programs or even a
malformed message that amavisd-new or one of the external
modules/programs chokes on. Read http://www.ijs.si/software/amavisd/#faq-gen
(The Berkeley DB notes will not apply to version 20060616).
It can also be some sort of resource issue, such as running out of
swap space (maybe not enough ram or too many amavisd-new child
processes) or reaching an open file limit. If you have several
gigabytes of amavisd temp directories, this can also be a problem in
itself (snowball effect).
> I don't really understand what should I add and to what file to make
> local delivery work again.
It's not possible for anyone to know until the source of the problem
is found.
> In the following page (see the link) claimed that it is the amavisd fault:
> http://www.irbs.net/internet/postfix/0208/0894.html
It is not a problem with Postfix.
> What should I do to fix it please?
> Regards,
> Leon
Before you can fix it, the problem must first be found. In order to
find the problem, we would need to see if your logs provide clues.
I would start by temporarily increasing the $log_level to 5 (then shut
down and restart amavisd-new), then look through the log for clues. Try
to trace a message from beginning to end, looking for errors reported by
amavis. If you find a good error message or two, this may be where to
start looking for a solution. Look for text like ERROR (or) TROUBLE (or)
error (or) Can't. Also use 'top' to monitor the amavisd-new processes
and memory usage.
Gary V
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
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/
