[Maia-users] web pages hang on maia, forced to reboot server. ..

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kurt Buff wrote:

> I'll wait for a while to see if commenting out interactive-timeout cures it,
> but this seems a bit unlikely. Why I say this is because we receive mail for
> 3 offices, one in the US, one in the UK and one in AU, and we receive
> between 300 and 500 emails each day, from midnight to each day.

Eight hours seems like a long time for a connection to be idle, yes, but
remember that each amavisd-maia child establishes its own connection to
the database.  When your traffic levels are low, some of those children
sit idle because they're only needed during your peak traffic period.
Your server may not get busy enough to need those additional children
for many hours, even though the first child is busy almost constantly.
The next time a connection needs to get handed to one of the idle
children, that child's database connection could well have timed out, if
it's been more than 8 hours since that child was last needed.

That's why increasing the timeout to 24 hours (or more) tends to help,
since you're likely to encounter another peak traffic period within that
timeframe, during which every amavisd-maia child should receive at least
one mail item.  If your weekend traffic never peaks high enough to
require all of the children, you might even consider increasing the
timeout to 72 or 96 hours, to cover you from your Friday peak to
Monday's peak.

Of course as Mike points out, if you've got more amavisd-maia children
than you really need for your traffic levels, another way to solve the
problem is to reduce that figure so that all of your amavisd-maia
children are kept busy.  At the traffic levels you're describing--500
emails a day--you'd be fine with the default of 2 amavisd-maia children.

- --
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGslZCGmqOER2NHewRAorHAJ9inT4iNYKzvry4UHLSQv3nnlOjSACdErlZ
YmHxwCuAo8Z+6ljl3PfoXAQ=
=URBf
-----END PGP SIGNATURE-----