Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Get staging8 and staging10 back up and running (recover from "mysqlserver has gone away" error)
» Get staging6, staging8, and staging10 back up and running (recover from "mysqlserver has gone away" error)
I think I've figured out what happened to these three sites (staging6 is now borked, too) - someone tries to copy the mysql files of another staging site over directly (e.g., not dump files) and tries to use the restore script on it. This process seems to work fine for files originated from the staging site in question, but not well across staging sites. The really unfortunate thing is that not only does it not work, but it also results in it being *impossible* to sustain a connection to the db with either command line mysql, or via a browser. It messes the db up but good. :p
Think the only way to fix this issue with staging6,8,10 is to have mysql root and drop tables, possibly the dbs and re-import. I do not have mysql root, and I cannot sustain a connection using the normal db user and password. (read - this will need nnewton to fix).
Setting as critical because I'm blocked on doing anything with these three staging sites until they get unborked enough to at least let a db connection.
Comments
Comment #1
rfaystaging8 and staging10 suffer from "mysql server has gone away".
I believe staging9 is OK.
I recommend that we just drop and rebuild the databases for these two.
Comment #2
calebgilbert commentedRestore script doesn't work "Cannot find a table in the database you want to restore!".
I will give dumping in the brand new db a try once I get that sorted out in my sandbox (staging7).
Comment #3
calebgilbert commentedI think I've figured out what happened to these three sites (staging6 is now borked, too) - someone tries to copy the mysql files of another staging site over directly (e.g., not dump files) and tries to use the restore script on it. This process seems to work fine for files originated from the staging site in question, but not well across staging sites. The really unfortunate thing is that not only does it not work, but it also results in it being *impossible* to sustain a connection to the db with either command line mysql, or via a browser. It messes the db up but good. :p
Think the only way to fix this issue with staging6,8,10 is to have mysql root and drop tables, possibly the dbs and re-import. I do not have mysql root, and I cannot sustain a connection using the normal db user and password. (read - this will need nnewton to fix).
Comment #4
calebgilbert commentedSetting as critical because I'm blocked on doing anything with these three staging sites until they get unborked enough to at least let a db connection.
Comment #5
rfayhttp://groups.drupal.org/node/36744 has been created to track staging site status. Please update it when progress is made on this.
Comment #6
Amazon commentedRfay and Calebg got all these sites up and running.