> > I have scheduled a cronjob to update rulesets of spamassassin:
> >   sa-update --gpgkey 6C6191E3 --channel sought.rules.yerp.org --
> channel
> >   updates.spamassassin.org && /usr/sbin/rcamavisd reload
> > I get the bad surprise that - after Amavisd-new reloading - the mail
> > gateway is stopped.
> >
> > I have investigated and I have found several messages:
> >   dsn=4.4.2, status=deferred (delivery temporarily suspended: lost
> >   connection with 127.0.0.1[127.0.0.1] while sending RCPT TO)
> > server:~ # telnet localhost 10024
> > 421 4.3.2 Service shutting down, closing channel
> 
> > Finally, I looked at at amavisd-new temporary directory and was
full:
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/shm                262144    262144    0 100% /var/amavis/scan
> 
> It is possible that with every shutdown a set of up to $max_servers
> temporary directories is left behind. This is usually insignificant
> (and should be cleaned manually every once in a while), but if you
> are restarting amavisd often, it can amount to a large number
> in a long run. Also, if there was some other problem occasionally
> encountered by amavisd, it would preserve its temporary directory,
> slowly filling up the disk.
> 
> Your (memory) disk partition is quite small. This is one reason
> why I'm not in favour of ram-based temporary workspace for amavisd.
> With a couple of gigabytes to spare, you'd probaby notice it
> before disaster struck.
> 
> > Now, I ask:
> > 1) It was Amavisd-new that interrupted SMTP transaction after reload
> or
> > the filesystem was fullfilled and Amavisd-new stopped to work
> (closing
> > SMTP transaction everytime)
> 
> It was probably filling up gradually and you didn't notice.
> Or there was a repeated failure, and you weren't monitoring the log.
> 
> > 2) Is there a safe way to reloading amavisd-new?
> 
> One way to do it is to:
>   amavisd stop
>   rm -rf /var/amavis/scan
>   mkdir /var/amavis/scan
>   chown vscan:vscan /var/amavis/scan
>   amavisd start
> 
> > But I fear that the real problem is that amavisd-new at reload time
> is
> > overcomed by the flow of messages queued by Postfix to be injected
> into the
> > amavis content filter.
> 
> Probably not, or you would have noticed it during your busy times.

Thanks Mark,

I'm sure that amavisd-new is a great product. So, I totally agree with
your analisys.

I'll update the startup script so that the memory file system is cleaned
every time that Amavisd-new is started.

rocsca

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/ 

Reply via email to