Last modified: 2012-12-17 12:16:30 UTC
During an upgrade from 1.18.3 to 1.19.0 the update script failed with an mysql connect error. At this point I couldn't connect to the mysql server using any means, for a minute or so, and then I was able to connect fine. Ran the script again, and the same thing happened, so it seems the script is causing the mysql server to start rejecting connections temporarily. Tail of output from update.php... ...have rd_interwiki field in redirect table. ...transcache tc_time already converted. ...eu_wiki_id already renamed to eu_local_id. ...*_mime_minor fields are already long enough. ...iwlinks table already exists. ...index iwl_prefix_title_from already set on iwlinks table. ...have ul_value field in updatelog table. ...have iw_api field in interwiki table. ...iwl_prefix key doesn't exist. ...iwl_prefix_from_title key doesn't exist. Adding cl_collation field to table categorylinks...DB connection error: Lost connection to MySQL server at 'reading initial communication packet', system error: 111 (mysqlsvr)
(In reply to comment #0) > During an upgrade from 1.18.3 to 1.19.0 the update script failed with an mysql > connect error. > > At this point I couldn't connect to the mysql server using any means, for a > minute or so, and then I was able to connect fine. > > Ran the script again, and the same thing happened, so it seems the script is > causing the mysql server to start rejecting connections temporarily. Is mysql still running? It sounds like it died
I presume so, as I have nothing that automatically restarts it, and it is available to connect to moments later.
Craig: Was this reproducible, also when upgrading to MW 1.19.3 or 1.20.2?
It looks like this was a result of poorly configured mysql server. No problem with the upgrade script