One other thing. If you don't do a DBI->connect() during each and every http request Apache::DBI's ping method will not get called, which sets you up for these errors.
I had some logic that short-circuited the Apache::DBI calls like this: $DBH ||= ..... and got bitten by the same error. On Thu, Mar 18, 2004 at 10:55:29AM -0500, Chris Miller wrote: > Think I should up the max packet size?? > > Thanks, > > Chris Miller > Compuville > www.compuville.net > > > From: Andrew Green [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 18, 2004 10:55 AM > To: Chris Miller > Cc: [EMAIL PROTECTED] > Subject: Re: "MySQL server has gone away" > > On Thu, 18 Mar 2004 10:23:42 -0500, Chris Miller wrote: > > > DBD::mysql::st execute failed: MySQL server has gone away at > > /usr/local/lib/perl/5.6.1/Mysql.pm line 175. > > I was bitten by this once when trying to write records to the MySQL > server that were bigger than the server's configured maximum packet > size -- the MySQL server would simply drop the connection, prompting > DBI to give that error. > > I imagine that if you're using Apache::DBI, restarting Apache would > appear to fix the connection, leading you to suspect a mod_perl problem. > -- Paul Lindner [EMAIL PROTECTED] ||||| | | | | | | | | | mod_perl Developer's Cookbook http://www.modperlcookbook.org/ Human Rights Declaration http://www.unhchr.ch/udhr/
pgp00000.pgp
Description: PGP signature
