Hi, please increase your interactive_timeout variable to some big number and also try to log the erros if any thing by using the command:
mysqldump --opt db_name > db_name.sql -p 2>>bkp.err check if you get some thing in the bkp.err file. Regards, Chandru, www.mafiree.com On Mon, Jan 12, 2009 at 9:07 AM, Daniel Kasak <d...@entropy.homelinux.org>wrote: > Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have > always done nightly backups with: > > mysqldump --opt db_name > db_name.sql -p > > Recently this started failing with: > Error 2013: Lost connection to MySQL server > > I have checked all tables for corruption - nothing found. Also as far as > I can tell there are no issues with clients using the database. There > have been no crashes since I did a full restore. So I assume we can rule > out corruption. > > I have searched around for the error message, and found people > discussing the max_allowed_packet option. I've tried increasing the > server's max_allowed_packet to many different values. Currently it's at > 128M, which is *way* over the default. I have also used the > --max_allowed_packet option simultaneously with mysqldump. And lastly, I > have been restarting the server after each my.cnf change. > > The data was inserted via the 'dbmail' application > ( http://www.dbmail.org ), while the server was set up with the default > max_allowed_packet size. DBMail breaks up message into chunks, and > stores these chunks in individual records. I'm not sure what the default > size of these chunks is, but I belive it's a reasonable value anyway. > > What next? I *must* get regular backups working again ... > > Dan > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=chandru....@gmail.com > >
