MySQL has gone away...how about YourSQL? Can't backup DB...

Permalink
So...I did like they said, and tried to backup my database before upgrading 5.4.1 to 5.4.1.1...

When I ran backup I got this red message...

mysql error: [2006: MySQL server has gone away] in EXECUTE("select tpID, tpHandle, tpName, tpDescription, pkgID from TaskPermissions where tpHandle = 'backup'")

...followed by this Fatal Error:

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysql error: [2006: MySQL server has gone away] in EXECUTE("insert into Logs (logType, logText, logIsInternal) values ('exceptions', 'Exception Occurred: mysql error: [2006: MySQL server has gone away] in EXECUTE("select tpID, tpHandle, tpName, tpDescription, pkgID from TaskPermissions where tpHandle = \'backup\'")\n\n#0 /nfs/c06/h04/mnt/96533/domains/coronadocougars.net/html/updates/concrete5.4.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1037): adodb_throw(\'mysql\', \'EXECUTE\', 2006, \'MySQL server ha...\', \'select tpID, tp...\', false, Object(ADODB_mysql))\n#1 /nfs/c06/h04/mnt/96533/domains/coronadocougars.net/html/updates/concrete5.4.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(993): ADOConnection->_Execute(\'select tpID, tp...\')\n#2 /nfs/c06/h04/mnt/96533/domains/coronadocougars.net/html/updates/concrete5.4.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1605): ADOConnection->Execute(\'select tpID, tp...\', Array)\n#3 /nfs in /nfs/c06/h04/mnt/96533/domains/coronadocougars.net/html/updates/concrete5.4.1/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php on line 78.

Anybody have a solution? I sure do appreciate ya.

View Replies:
Mnkras replied on at Permalink Reply
Mnkras
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
contact your host
Vokankh replied on at Permalink Reply
It's not always fault of mysql administrator. There are cases where big load of data is in one table. Through insert optimalization MySQL construct single insert with many rows to insert, that is called packet. It looks like this:
insert into table values( 1,2,3 )(4,5,6)... etc.
When packet get's too big (there's a lot of data in the end of insert) it may exceed max_packet_size variable.
Another case are low timeouts to database with poor database optimalization (no indexes etc)