On Tue, Jan 13, 2009 at 6:06 PM, Dan <d...@entropy.homelinux.org> wrote: > On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner > <andrew.b.gar...@gmail.com> wrote: > >> This sounds like you need to raise max_allowed_packet for mysqldump >> (and possibly mysqld) - these are separate settings for both the >> client and the server. You can do this via the my.cnf (or ~/.my.cnf) >> or specify it as an option on the command line "mysqldump --opt ... >> --max_allowed_packet=1G dbname > backup-file". > > This is certainly the most common advice for this error, yes. I increased > the max_allowed_packet size from 1M to 128M when the problem initially > occured. This didn't fix anything.
My apologies. I hadn't read up-thread where this was discussed, and given that, max_allowed_packet is almost certainly not the problem. Sorry for the noise. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
