Re: mysqldump problem with large innodb tables...

2007-06-19 Thread Dušan Pavlica
Try to look for Lost connection error in MySQL manual and it can give your some hints like http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html Dusan Hartleigh Burton napsal(a): Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed

RE: {Spam?} Re: mysqldump problem with large innodb tables...

2007-06-19 Thread John Mancuso
-Original Message- From: Dušan Pavlica [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 19, 2007 5:08 AM To: Hartleigh Burton Cc: MySql Subject: {Spam?} Re: mysqldump problem with large innodb tables... Try to look for Lost connection error in MySQL manual and it can give your some hints

Re: mysqldump problem with large innodb tables...

2007-06-19 Thread Hartleigh Burton
Hi Dusan, You replied to a forum post of mine on mysql.com yeah? ;) I have tried adjusting the max_allowed_packet on both the server and client. Both are set to 1G now (apparently the highest value accepted) even though each row is no larger than 100M at very most. I am thinking this may

Re: mysqldump problem with large innodb tables...

2007-06-18 Thread Baron Schwartz
My backups use mysqldump, but they have always just worked. I would suggest you try to make a minimal test case that can reproduce the problem and submit it as a bug report, if possible. I'm not familiar with the error message off-hand, but the InnoDB manual is large and complete, so I'm

mysqldump problem with large innodb tables...

2007-06-17 Thread Hartleigh Burton
Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Baron Schwartz
Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Hartleigh Burton
Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Baron Schwartz
How about in c:\Program Files\MySQL\MySQL Server 5.0\data\hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Hartleigh Burton
H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \hostname.err?

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Baron Schwartz
Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure.

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Hartleigh Burton
No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Baron Schwartz
I'm out of ideas right now. I don't actually use mysqldump that much and have never had this happen. Hopefully someone else on the mailing list can help, or perhaps you can try #mysql on Freenode IRC. Baron Hartleigh Burton wrote: No there is no indication of that at all. The server service

Re: mysqldump problem with large innodb tables...

2007-06-17 Thread Hartleigh Burton
Ok... this error has just started popping up in my .err log file... 070618 14:31:10 InnoDB: ERROR: the age of the last checkpoint is 237821842, InnoDB: which exceeds the log group capacity 237813351. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of