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
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
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
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 2bkp.err
check if you get some thing in the bkp.err file.
Regards,
Chandru,
www.mafiree.com
On Mon, Jan 12, 2009
On Mon, 12 Jan 2009 16:25:12 +0530, Chandru chandru@gmail.com wrote:
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 2bkp.err
check if you get some
I'm also having a similar issue with some tables I've been trying to dump
(total data set is around 3TB). I'm dumping directly from one host to
another (mysqldump -hSOURCE DATABASE | mysql -hLOCALHOST DATABASE) using
mysql 4.1.22. One system is Solaris 10 SPARC, while the other is Solaris 10
x64
Hello everyone!
I just wanted to give everyone an update. I'm still getting this error
when I try to back up this database table. I don't get it at the same
row each time - today was at row 1,618, yesterday it was at row 24,566.
Just a reminder of my symptoms:
1. mysqldump is the only thing
Have a look here:
http://dev.mysql.com/doc/mysql/en/gone-away.html
Gleb,
Thanks for the response. The only one that seems to apply is this one:
You may also see the MySQL server has gone away error if
MySQL is started with the --skip-networking option.
I do start mySQL without networking
Gustafson, Tim [EMAIL PROTECTED] wrote on 08/29/2005 09:24:36 AM:
Hello
I am using mysqldump to backup my entire database (about 40GB total)
each night. I dump each table separetly, so that if mysqldump crashes
in the middle somewhere, the rest of the database still gets backed up.
Most
/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 9:35 AM
To: Gustafson, Tim
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump: Error 2013
Gustafson, Tim [EMAIL PROTECTED] wrote on 08/29/2005 09:24:36 AM:
Hello
I am using
Gustafson, Tim wrote:
When backing up this table, I get this error message every night:
/usr/local/bin/mysqldump: Error 2013: Lost connection to MySQL server
during query when dumping table `DocumentVariants` at row: 13456
The table actually has 94,916 rows in it. There are no entries in the
: Hassan Schroeder [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 9:51 AM
To: mysql@lists.mysql.com
Subject: Re: mysqldump: Error 2013
Gustafson, Tim wrote:
When backing up this table, I get this error message every night:
/usr/local/bin/mysqldump: Error 2013: Lost connection
Gustafson, Tim wrote:
No, max_allowed_packet is 100 megabytes, and the maximum data field
in the database is 50MB right now, and most are well below 10MB.
mmm. OK, not having any more bright ideas :-) I would try dumping
it using an explicit `--where=` claus to guarantee fixed ordering,
and
Hello.
Has anyone else had similar problems? Can anyone shed some light on how
to successfully back up this database?
Have a look here:
http://dev.mysql.com/doc/mysql/en/gone-away.html
Hello
I am using mysqldump to backup my entire database (about 40GB total)
each night. I
Hassan Schroeder wrote:
Does the size of the contents of that field exceed your defined
max_allowed_packet size?
Gustafson, Tim wrote:
No, max_allowed_packet is 100 megabytes, and the maximum data field in
the database is 50MB right now, and most are well below 10MB.
Tim Gustafson
MEI
I believe it's the size of the row, not the size of a
single field, that matters. Is it possible you have a
row which exceeds max_allowed_packet size?
No. There is one blob fields (always less than 50MB) and like 10 other fields,
all integers.
smime.p7s
Description: S/MIME cryptographic
16 matches
Mail list logo
