Is there any mechanism in place to "ping" the database and restore the child process pool when the database is back up? Otherwise we've traded a bad situation that hobbles the machine with a bad situation. Would be good to gracefully handle the bad situation, too.
Aaron On Tue, Apr 19, 2005, Paul J Stevens <[EMAIL PROTECTED]> said: > I've fixed this bug. But please take note: when the backend goes away, > dbmail servers in preforking mode will now shut down completely. > > In the future I may change this behaviour to allow for temporary > failures to talk to the backend, as such a need arises. But it seems > better for now to simply have the daemons die than have them trash the > machine they're on. > > Fixed both in 2.0 and in trunk. > > > [EMAIL PROTECTED] wrote: >> Summary: huge load if database crash >> Description: >> if you have 2 different server, one for dbmail and one for mysql, and the >> connection to the database is lost, dbmail >> don't establish a new connection and the load of the dbmail >> machine go up to and freeze the machine for long time
