On Fri, Sep 22, 2006 at 02:54:14PM -0400, Dave wrote: > Hi, > Thanks for your reply. Yes i did check that site, and none of the causes > of the error seem applicable to my situation. I haven't had a server crash, > i don't have any large commits going in either from bacula or from other > mysql apps.
There was a change in the default behavior of MySQL from 4.1 to 5.0 that disables the automatic recconect feature that bacula uses. Bacula opens a connection to the catalog, spends a few hours backing up data during which the db connection times out, and then bombs when it tries to use the db handle. http://paramount.ind.wpi.edu/wiki/doku.php?id=faq#mysql_server_has_gone_away Rumor was that a patch taht went into 1.38.7 fixed this, but it appears that the glitch is still there in some cases. -- Frank Sweetser fs at wpi.edu | For every problem, there is a solution that WPI Network Engineer | is simple, elegant, and wrong. - HL Mencken GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
