Last modified: 2008-12-16 02:06:21 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 1274 - deadlock error on edit save
deadlock error on edit save
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: High major with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 1296 5166 5824 5876 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-06 22:05 UTC by Dan Keshet (English Wikipedia)
Modified: 2008-12-16 02:06 UTC (History)
8 users (show)

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


Attachments

Description Dan Keshet (English Wikipedia) 2005-01-06 22:05:16 UTC
I was editing List of US Supreme Court Cases on en when I got this error:

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

    SELECT cur_id,cur_namespace,cur_title FROM `cur`,`links` WHERE cur_id=l_to
AND l_from=102337 FOR UPDATE

from within function "LinkCache::preFill". MySQL returned error "1213: Deadlock
found when trying to get lock; Try restarting transaction (10.0.0.1)".
Comment 1 Brion Vibber 2005-01-29 07:17:17 UTC
*** Bug 1296 has been marked as a duplicate of this bug. ***
Comment 2 Tim Starling 2005-03-09 04:44:38 UTC
This can be fixed at any time by setting $wgDumbLinkUpdates = true. This
elimates any chance of a deadlock on the heavily-updated link table.
Unfortunately (according to JamesDay) that causes the slaves to choke and die. A
strategy of reducing lock time may be a better approach, and a few such tweaks
have been made. Deadlocks should be much less frequent than they once were.

As far as I'm concerned, a friendlier error message allowing the user to
resubmit their edit easily would close this bug.
Comment 3 Brion Vibber 2005-03-09 06:55:15 UTC
Couldn't we restart the transaction automatically in this case, by at some level re-callling a function?
Comment 4 Brion Vibber 2006-01-22 04:21:55 UTC
Restored from flood attack.
Comment 5 Brion Vibber 2006-05-04 08:12:13 UTC
*** Bug 5824 has been marked as a duplicate of this bug. ***
Comment 6 Brion Vibber 2006-05-09 00:12:56 UTC
*** Bug 5166 has been marked as a duplicate of this bug. ***
Comment 7 Brion Vibber 2006-05-09 00:13:01 UTC
*** Bug 5876 has been marked as a duplicate of this bug. ***
Comment 8 a.steffan 2007-11-14 11:29:23 UTC
The same error appeared on your mediawiki today.
Mediawiki 1.11.0
Mysql 5.0.22
PHP 5.1.2 (cgi-fcgi)

The error message:

In the function "MediaWikiBagOStuff::_doinsert"
MySQL returned the error "1213: Deadlock found when trying to get lock; try restarting transaction (localhost)"
Comment 9 Dan Barrett 2008-08-21 14:05:31 UTC
I got this error today on 1.13.0 on Windows 2003 Server when trying to view a page, not edit it. --~~~~

Comment 10 Aaron Schulz 2008-09-11 21:31:42 UTC
(In reply to comment #9)
> I got this error today on 1.13.0 on Windows 2003 Server when trying to view a
> page, not edit it. --~~~~
> 

These tables don't exist anymore, like the query
Comment 11 Chad H. 2008-12-16 02:06:21 UTC
Closing as WORKSFORME. As Aaron said, 'cur' doesn't exist anymore. Nor does this query, or even the method LinkCache::preFill. Any deadlock errors on save would be unrelated to this.

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


Navigation
Links