Last modified: 2014-10-08 02:50:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T73764, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71764 - Can't connect to MySQL on deployment-db1
Can't connect to MySQL on deployment-db1
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Normal critical
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-07 22:13 UTC by Rummana Yasmeen
Modified: 2014-10-08 02:50 UTC (History)
18 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Rummana Yasmeen 2014-10-07 22:13:51 UTC
Cannot save any edit on Betalabs, the following error is appearing on the save dialog:

Exception Caught: DB connection error: Can't connect to MySQL server on '10.68.16.193' (4) (10.68.16.193)
Comment 1 Rummana Yasmeen 2014-10-07 22:18:19 UTC
Cannot open VE for any page as well, showing the error:

Error loading data from server: readonly: The wiki is currently in read-only mode. Would you like to retry?
Comment 3 Greg Grossmeier 2014-10-08 02:39:29 UTC
All browser tests will fail, all users/developers will complain.

Marc/Andrew/Yuvi: Anything going on that might explain this? Any changes from production that might have caused havoc?

Sean: adding you because the database update script is failing on beta: any changes you made recently that might effect this?
Comment 4 Greg Grossmeier 2014-10-08 02:40:09 UTC
(due to a mid-air collision, re-adding Sean. Sean, see above)
Comment 5 Yuvi Panda 2014-10-08 02:41:54 UTC
So...

There was a 'rogue' mysql server on deployment-db1, which wasn't being recognized by the init script for... some reason. I killed it manually, and started mysql again, and all seems well...

This *might* have been because of the virt1005 failure related restart earlier (that is pure speculation). Should investigate more deeply if this happens again...
Comment 6 Greg Grossmeier 2014-10-08 02:50:17 UTC
Thanks Yuvi!

(Sorry for the pings Marc/Andrew/Sean :) )

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links