Comments on: Solution for: MySQL server has gone away at mysqlhotcopy line 528 http://joshhighland.com/blog/2009/01/19/solution-for-mysql-server-has-gone-away-at-mysqlhotcopy-line-528/ the living internet Mon, 14 May 2012 13:25:16 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Coly Moore http://joshhighland.com/blog/2009/01/19/solution-for-mysql-server-has-gone-away-at-mysqlhotcopy-line-528/comment-page-1/#comment-6992 Coly Moore Fri, 30 Oct 2009 04:31:51 +0000 http://joshhighland.com/blog/?p=501#comment-6992 Thank you! I was completely baffled by this error until you clued me in that it was a timeout. I put in 3600 and got a good run. 3600 (one hour) seems like a bit much, though. mysqlhotcopy ended with: Copying 362 files... Copying indices for 0 files... Unlocked tables. mysqlhotcopy copied 120 tables (362 files) in 162 seconds (171 seconds overall). So for me 180 seconds (3 minutes) looks like plenty. I'm so happy I now know where to look in case of future "mysql server has gone away". :D Thank you! I was completely baffled by this error until you clued me in that it was a timeout. I put in 3600 and got a good run.
3600 (one hour) seems like a bit much, though.

mysqlhotcopy ended with:
Copying 362 files…
Copying indices for 0 files…
Unlocked tables.
mysqlhotcopy copied 120 tables (362 files) in 162 seconds (171 seconds overall).

So for me 180 seconds (3 minutes) looks like plenty. I’m so happy I now know where to look in case of future “mysql server has gone away”. :D

]]>