Last modified: 2014-03-25 17:41:57 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 T62382, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60382 - Database problems. Unable to write and intermittent problems on reading
Database problems. Unable to write and intermittent problems on reading
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-23 22:47 UTC by bgwhite
Modified: 2014-03-25 17:41 UTC (History)
3 users (show)

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


Attachments

Description bgwhite 2014-01-23 22:47:03 UTC
I'm unable to write to the database.  Programs are just hanging.  Having troubles reading in that it can take awhile to receive data. Things were ok 12 hours ago.  Looks like problem has been happening atleast for 3 hours.
Comment 1 bgwhite 2014-01-23 22:49:48 UTC
Now unable to connect to database via the website.  

I get "Could not connect to database: User 'p50380g50450' has exceeded the 'max_user_connections' resource (current value: 80)"

I only have on hung program on the queue and nothing else that should be doing so many connctions.
Comment 2 bgwhite 2014-01-24 00:36:53 UTC
I can access the database again.  Coincidentally(?), about 50 mysql processes are no longer running on tools-login.  Though there are still a few running by users since last year.
Comment 3 Tim Landscheidt 2014-01-24 01:03:22 UTC
Which database server were you connecting to, i. e. tools-db or the replicas?

(We had a full disk on tools-db, so that could have saturated that server (accepting connections, but then not being able to answer queries).)
Comment 4 bgwhite 2014-01-24 06:19:24 UTC
Sorry, that would have been helpful:  tools-db
Having a full disk could have caused.  Thanks for telling me.
Comment 5 Marc A. Pelletier 2014-03-25 17:41:57 UTC
This was, indeed, caused by a disk full on the (now gone) old database instance.

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


Navigation
Links