> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:amavis-user-
> [EMAIL PROTECTED] On Behalf Of Clifton Royston
> Sent: Monday, February 12, 2007 10:03 PM
> To: Bryan K. Walton
> Cc: [email protected]
> Subject: Re: [AMaViS-user] No space left on device
>
> On Mon, Feb 12, 2007 at 11:01:26AM -0600, Bryan K. Walton wrote:
> > On Mon, Feb 12, 2007 at 10:49:26AM -0600, Noel Jones wrote:
> > > >-- begin snip --
> > > >Feb 9 20:31:59 gw1.machlink.com amavis[11299]: (11299-03) (!!)
> > > >TROUBLE in check_mail: mime_decode-1 FAILED: MIME::Parser: can't
> > > >close: No space left on device at /usr/share/perl5/MIME/Parser.pm
> line
> > > >834.
> > > >
> > > >-- end snip --
> > >
> > > To get back going, you will need to stop amavisd-new and clean out
> > > the tmpfs. You can save those files elsewhere for later analysis, or
> >
> > Yes, I did this Saturday morning. Clearing out all of the tmpfs files
> > in /var/amavis/tmp got Amavisd-New working again.
> >
> >
> > > Is the snip above the earliest TROUBLE message amavisd-new logs? If
> > > so, move that particular mail message out of the way (postsuper -h
> > > QUEUEID) and see if mail then processes normally. Then you can
> > > analyze that message to see why amavisd-new choked on it. Maybe it
> > > has a big archive that filled up the tmpfs.
> >
> > Unfortunately, I simply deleted everything in /var/amavis/tmp rather
> > than move it out of the way. The log snippet above wasn't the first
> > trouble message, but it appears to be the second. What is peculiar is
> > that /var/amavis/tmp usually only has 7 tmp files in it (one for each
> > running amavis server). However, on Saturday morning, there were
> > THOUSANDS. Therefore I'm inclined to believe that the problem wasn't
> > simply one message.
>
> It can happen with the same message being retried until it completely
> fills up the system. It can also happen that there's a highly
> compressed message ("zip bomb") which fills up the tmpfs, and then
> everything else fails to uncompress.
>
> Unfortunately if the initial problematic message is no longer
> available, it's hard to narrow it down.
> -- Clifton
I'm using the following cronjob to ensure I won't have this kind of
situation:
*/40 * * * * /bin/bash -c "(find /var/spool/amavis -type d -name 'amavis-*'
-prune -mmin +30 -exec rm -rf {} \;)"
Regards,
Leon Kolchinsky
>
> --
-------------------------------------------------------------------------
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
[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/
