Last modified: 2014-02-28 21:20:25 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 T58487, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56487 - "Lock wait timeout exceeded; try restarting transaction" while deleting
"Lock wait timeout exceeded; try restarting transaction" while deleting
Status: NEW
Product: Wikimedia
Classification: Unclassified
Media storage (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-01 19:31 UTC by Yann Forget
Modified: 2014-02-28 21:20 UTC (History)
7 users (show)

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


Attachments

Description Yann Forget 2013-11-01 19:31:41 UTC
Hello,

I got an error message while deleting files:
https://commons.wikimedia.org/w/index.php?title=File:Moraglia_serve_alla_mensa_dei_poveri_Ca_Letizia_24-03-2012.jpg&action=delete
A database query error has occurred. This may indicate a bug in the software.

Function: WikiPage::pageData
Error: 1205 Lock wait timeout exceeded; try restarting transaction
(10.64.32.29)

Also for
https://commons.wikimedia.org/wiki/File:Krystal_Jung.png
https://commons.wikimedia.org/wiki/File:Demy_The_Sun.jpg
https://commons.wikimedia.org/wiki/File:Yuri_boyka_brother..jpg
https://commons.wikimedia.org/wiki/File:Sampaio_1972_campe%C3%A3o.png
https://commons.wikimedia.org/wiki/File:Sampaio_1938.png

It is a serious problem if we can't delete files.
Comment 3 Bawolff (Brian Wolff) 2013-11-01 19:49:26 UTC
To clarify something - Given some file, does this error always appear when deleting, or is it more intermittent - If you try deleting it a couple times, it eventually succedes?
Comment 4 Yann Forget 2013-11-01 19:54:47 UTC
No, it appears every time.
Comment 8 Jesús Martínez Novo (Ciencia Al Poder) 2013-11-01 20:45:25 UTC
The problem does happen when editing the page, not just deleting. This doesn't seems to be related to MediaStorage:

    Function: Revision::insertOn
    Error: 1205 Lock wait timeout exceeded; try restarting transaction (10.64.32.29)

But other file description pages seem to be editable without problem (as seen in Special:RecentChanges.

What's going on?
Comment 10 Bawolff (Brian Wolff) 2013-11-01 21:06:36 UTC
When I purge one of these files I get:

A database query error has occurred. This may indicate a bug in the software.

    * Function: Title::invalidateCache
    * Error: 1205 Lock wait timeout exceeded; try restarting transaction (10.64.32.29)

So basically no matter what operation you do to these pages, you get lock contention from some different method (although always the same method for any given operation).
Comment 11 Yann Forget 2013-11-01 21:11:20 UTC
Null edit, then delete works.
Comment 12 Bawolff (Brian Wolff) 2013-11-01 21:12:15 UTC
I think related to global usage.

I was previously unable to edit https://commons.wikimedia.org/wiki/File:Ugglas.jpg - I removed the file from its use at ukwikipedia. Waited a couple seconds for global usage section to disappear, after that I could edit the file. (Just one test, so could be some sort of coincidence, but something to follow up at least)
Comment 13 Marco 2013-11-01 21:32:22 UTC
All files which are listed here were deleted by now
Comment 14 Bawolff (Brian Wolff) 2013-11-01 21:50:18 UTC
hmm, perhaps comment 11 and comment 12 are coincidences. According to https://icinga.wikimedia.org/cgi-bin/icinga/history.cgi?host=db1059&service=MySQL+Idle+Transactions there were alerts for the commons db from "2013-11-01 19:10:08" to about "2013-11-01 21:04:53". I don't really know enough about how mysql works to know what that means (My knowledge of the inner workings of mysql is pretty much nill), but I'd guess it means server had some sort of problem which server got over. The timeline corresponds with those reported in this bug.
Comment 15 Marco 2013-11-01 22:05:00 UTC
(In reply to comment #14)
Thanks for the link.
Also lowering priority.

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


Navigation
Links