On Sun, 2011-06-19 at 22:33 +0200, Reindl Harald wrote: > there goes something terrible wrong if mysqld is not ready > at start, playing ariund with fedora 15 and systemd ends > most time in > > "warning: problem talking to server > /var/spool/postfix/dbmail-postfix-policyd/socket: > Connection timed out"
Ie. that is a postfix error indicating dbmail-postfix-policyd hasn't created that unix socket? Is dbmail-postfix-policyd still running? If so, it might be some logic that doesn't create that socket on an initial db connection failure or somesuch. > would it be possible to try reconnect to mysql on errors or > even exit the process would be better because "systemd" would > start it again I need to do a little improvement in reconnecting for idle sockets at least with postgres, I could try to catch what's going on here, too, if we can nail it down. Ironically, wasn't one of your most recent requests just the opposite - if there's a database problem you wanted it to not exit and allow mail to pass, since a quota check isn't a show stopper? ;) For the moment maybe put a "sleep 30" in your init script, and I'll try to look for that socket creation problem. The reconnect logic might take a bit longer and I'm short on time at the moment. Thanks, Jesse -- Jesse Norell Kentec Communications, Inc. [email protected] _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
