Last modified: 2005-10-28 09:52:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3602 - Locked articles on
Locked articles on
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
PC Linux
: Normal blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-10-04 20:41 UTC by dake
Modified: 2005-10-28 09:52 UTC (History)
0 users

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


Description dake 2005-10-04 20:41:46 UTC
Can't delete some articles, for example 

The database seems to be locked. Someone told me it already happened before.
Note that our "Articles for deletion" page is also locked, saving is impossible
and is extremely annoying. See,

Error : 

Un article de Wikipédia, l'encyclopédie libre.
Erreur de syntaxe dans la base de données. La dernière requête traitée par la
base de données était :

    (SQL query hidden)

depuis la fonction « Title::touchArray ». MySQL a renvoyé l'erreur « 1205: Lock
wait timeout exceeded; Try restarting transaction ( ».
Comment 1 Brion Vibber 2005-10-04 21:08:34 UTC
This is a transient error, run it again.
Comment 2 Brion Vibber 2005-10-04 21:56:26 UTC
Apparently this is continuous; some kind of stuck lock on the page entry. Got one of 
our MySQL guys helping look into this now...
Comment 3 Brion Vibber 2005-10-28 09:52:26 UTC
This incident was resolved weeks ago. :D

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