Last modified: 2005-03-05 17:28:50 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 896 - weird error while trying to rollback an edit
weird error while trying to rollback an edit
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-16 19:30 UTC by Schnee
Modified: 2005-03-05 17:28 UTC (History)
0 users

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


Attachments

Description Schnee 2004-11-16 19:30:59 UTC
Hi,

I just got the following error while rolling back an edit to
[[en:Actinobacteria]]. This is the second time I got an error like this (the
first time was a week or two ago); I have no idea what could have caused it.
Trying to rollback again worked fine.

-----

Database error

From Wikipedia, the free encyclopedia.
A database query syntax error has occurred. This could be because of an illegal
search query (see Searching Wikipedia), or it may indicate a bug in the
software. The last attempted database query was:

    REPLACE INTO
linkscc(lcc_pageid,lcc_cacheobj) VALUES(219865,
'x^íUËnÛ0ü݈¤sJ$-Ð4AôjPcE’‚Aþ½KŠ¶i;¹·€o’fŸ³»£V±¤UÝ‹àb#x{Ü\'½hù0ü‘6¹R_
¥ðñΘæ\'Ég¸p¶(cɵUgj.FiOÀº`
F-r÷BYraà@Ê<u$ ȤÝûáà´ØŽfPH‘¢\"ľºõE,g
BñyJ–ÜM¼Á©‚@–ëo=Õ«é
*âcÂó÷IB’\"-½#†î츱¡»`›¥{ƒãR(ÙêY‰•p¤¹\'>*Óãœä…n—Fµ«V=ï
())|…Pûµ„,J„QN*’튿ߊ¿3S@0©ršùêx?IÝ·|”쉿™Îèm°Ê³ê­
Ö½ÕãfÛî#åyVæÄÛÀî•°FCŒ¡7v7MšZùd(9JV›·U-×Ê÷uQLqéÇK¾4]A­Bjà-vòñ
„8‹?HX1Ó­†©nÔ«»!õ<aØÐ3GÙ5Qê‰À°vg†V®»I¯
\"»£ŽRb?O=zOá™ñ³&_sÞ8$¡~ãÝ­é¡7ni?¡*Ϫrž\"ÚÝ›Þ
éo\0üPšU1¯¾­ìGX‚Ø\"/h‰>æû¾á‡K†Íp—l^Õ(í
V¼uáCawæ+w1Ç#ÒßÀÎ7{ˆý
æÂXõ)ûø{ªw§usÙo¸»¯§µ@Ìm\'#–æ2¡”[Ë»\'B¡p
Ë/´0B¸ûž?ƒ$ý2‚Û&²„râöG‚xf\"‹1p‹;<¢UA¥G
@˜€Úås:UÏüCú‡æk¹—ß”½ƒ©;X½€»_#§˜“ìG+oUÛJ8ƒ
´P?´ÍEËgÝ¿hyôã¸hù‘úÿZîäÞóEÏÿU=ÿø.Ä‹n')

from within function "". MySQL returned error "1213: Deadlock found when trying
to get lock; Try restarting transaction".

-----
Comment 1 Antoine "hashar" Musso (WMF) 2005-03-05 17:28:50 UTC
dead locks error no more occuring.

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


Navigation
Links