Last modified: 2014-09-25 05:26:53 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 T37792, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35792 - SUL account recently created with no attached or unattached accounts, and undeletable
SUL account recently created with no attached or unattached accounts, and und...
Status: RESOLVED DUPLICATE of bug 39996
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal with 3 votes (vote)
: ---
Assigned To: Chris Steipp
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-07 13:22 UTC by Snowolf
Modified: 2014-09-25 05:26 UTC (History)
18 users (show)

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


Attachments
Maldez1 CentralAuth Problem (87.06 KB, image/png)
2012-05-15 13:55 UTC, Mark A. Hershberger
Details

Description Snowolf 2012-04-07 13:22:45 UTC
https://meta.wikimedia.org/w/index.php?title=Special:CentralAuth&target=NorthernSoul has no attached accounts, nor unattached ones, clearly shows up and, as I understand it, prevents local account creation, yet is undeletable from CentralAuth as "Error: the global account "NorthernSoul" does not exist." shows up, despite it clearly not being the case.
Comment 1 mabdul 2012-04-07 13:25:30 UTC
Error message while trying to create:

[14:57:55] <mabdul|busy> A database error has occurred. We apologise for any inconvenience this might have caused. The most likely cause of this problem is a search or other operation that took too long. Possible reasons include: 
[14:57:55] <mabdul|busy> A search where all words are in quotes. Try searching without the quotes initially or add a few more words outside the quotes to restrict the search; 
[14:57:55] <mabdul|busy> An exceptionally large personal watchlist (probably over 10,000 items); or 
[14:57:55] <mabdul|busy> Exceptionally heavy load on the database servers. 
[14:57:55] <mabdul|busy>  
[14:57:55] <mabdul|busy>  Technical details about this error:
[14:57:55] <mabdul|busy>  Last attempted database query: (SQL query hidden)
[14:57:55] <mabdul|busy>  Function: User::saveOptions
[14:57:55] <mabdul|busy>  MySQL error: 1213: Deadlock found when trying to get lock; try restarting transaction (10.0.6.48)
Comment 2 Jeff G. 2012-04-08 00:05:03 UTC
The URL also shows "Home wiki: unable to determine".
Comment 3 Simon Walker 2012-04-08 01:43:53 UTC
From what I can tell from looking in the cut-down toolserver replica, the global account (globaluser) doesn't actually appear to exist. It only "exists" in the "list of global names" (globalnames), which I think is used to check conflicts. Hence, the name exists so can't be created, but the global account doesn't exist so can't be deleted. I could be wrong, but that may help someone actually fix it.
Comment 4 Jeff G. 2012-04-08 14:16:34 UTC
Now 'There is no global account for "NorthernSoul"'.
Comment 5 mabdul 2012-04-08 14:25:38 UTC
account was now created as noted at https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=&user=&page=User%3ANorthernSoul&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_review_log=1

----
strange bug, any ideas why the SUL account disappeared?
Comment 6 Snowolf 2012-05-14 22:46:42 UTC
Now the same with Maldez1, I don't understand why this was marked as fixed, it clearly isn't.
Comment 7 Mark A. Hershberger 2012-05-15 13:24:37 UTC
(In reply to comment #6)
> Now the same with Maldez1, I don't understand why this was marked as fixed, it
> clearly isn't.

Bumping priority, notifying Robla and Sumana.
Comment 8 Mark A. Hershberger 2012-05-15 13:55:03 UTC
Created attachment 10598 [details]
Maldez1 CentralAuth Problem

(In reply to comment #6)
> Now the same with Maldez1, I don't understand why this was marked as fixed, it
> clearly isn't.

Added screenshot of current problem to help with troubleshooting.  Bumping priority, notifying Robla and Sumana.
Comment 9 Sam Reed (reedy) 2012-05-15 22:50:01 UTC
(In reply to comment #3)
> From what I can tell from looking in the cut-down toolserver replica, the
> global account (globaluser) doesn't actually appear to exist. It only "exists"
> in the "list of global names" (globalnames), which I think is used to check
> conflicts. Hence, the name exists so can't be created, but the global account
> doesn't exist so can't be deleted. I could be wrong, but that may help someone
> actually fix it.

Indeed. For "Maldez1" it was still showing entries, and a global user id that didn't exist. Manually invalidating the cache for the user then made it disappear on Special:CentralAuth and gave the more sensible error message of 'There is no global account for "Maldez1"'
Comment 10 Chris Steipp 2012-05-15 23:30:19 UTC
In this case, it looks like Maldez1 was inserted into globalnames, but not globaluser. The user id shown in the attachment was missing from the globaluser table, so possibly there was an error later on in the creation process, and the globaluser row was deleted/rolled-back. I'm trying to track down what cases would cause that..
Comment 11 Simon Walker 2012-06-19 19:50:40 UTC
Just happened again with Rubiks99... any progress on this?
Comment 12 Peter Symonds 2012-06-19 22:25:54 UTC
I was asked by Stwalkerster to comment on the bug after I hacked my way around this problem for Rubiks99. I created a temporary account on mediawiki.org (Rubiks99-temp) and renamed it to Rubiks99. This had the effect of disabling the global account so it could be created on enwiki. Not sure if this helps.
Comment 14 Sumana Harihareswara 2012-07-25 06:17:27 UTC
Can we still reproduce this problem, even after the most recent deployment?
Comment 15 Simon Walker 2012-07-25 17:08:54 UTC
(In reply to comment #14)
> Can we still reproduce this problem,

This bug was/is temperamental - we've noticed four or five instances of this in a few months, it may of course be happening more but unnoticed if it's happening to newbies rather than the ACC team. It may take a month or two to notice that it's "not happened in a while".


(In reply to comment #14)
> even after the most recent deployment?

Has anything actually been committed/merged to do something about this? I had a quick glance over the page at [[mw:MediaWiki_1.20/wmf7]] but couldn't spot anything.
Comment 16 Rob Lanphier 2012-09-27 21:10:44 UTC
This has been a background task for Chris for a while.  Until we can figure out a reliable repro case, it's going to be difficult to diagnose how to fix this.  Chris is going to look into ways we can log failures and possibly catch this in the act.
Comment 17 Platonides 2012-10-11 22:05:54 UTC
Looks like we add the items to memcached before they are really stored in the db.

I'd need to dig on which paths of CentralAuth are called on creation.

As a way to reproduce, unconditionally sending an exception at User::saveOptions() should do it.
Comment 18 Simon Walker 2013-03-30 06:32:08 UTC
Bump. Just happened again with Blinking5
Comment 19 Andre Klapper 2013-04-25 11:46:55 UTC
(In reply to comment #16 by RobLa)
> Chris is going to look into ways we can log failures and possibly catch this
> in the act.

Chris: Has this happened, or is this still on the to-do list?
Comment 20 Andre Klapper 2013-08-14 14:12:46 UTC
(In reply to comment #16 by RobLa)
> Chris is going to look into ways we can log failures and possibly catch this
> in the act.

Chris: Has this happened, or is this still on the to-do list?
Comment 21 callanecc.wiki 2013-10-27 07:14:36 UTC
Adding a bit more info to this one. The error message which appears when the bug occurs has changed. It appears as below:
A database query error has occurred. This may indicate a bug in the software.
* Function: CentralAuthUser::register
* Error: 1062 Duplicate entry 'Ahmad Komarudin' for key 'gu_name' (10.64.16.28)
Comment 22 callanecc.wiki 2013-10-27 07:18:30 UTC
(In reply to comment #21)
> Adding a bit more info to this one. The error message which appears when the
> bug occurs has changed. It appears as below:
> A database query error has occurred. This may indicate a bug in the software.
> * Function: CentralAuthUser::register
> * Error: 1062 Duplicate entry 'Ahmad Komarudin' for key 'gu_name'
> (10.64.16.28)

However the global and local enwiki account was created [https://en.wikipedia.org/w/index.php?title=Special%3ACentralAuth&target=Ahmad_Komarudin].
Comment 23 Technical 13 2014-02-12 13:13:37 UTC
I got the same error as mabdul in Comment 1 trying to create [[Special:CentralAuth/Moyokel]] last night.
Comment 24 Nemo 2014-09-25 05:26:53 UTC
Hopefully, this was fixed for good, at bug 39996.

(Kunal Mehta (Legoktm) on bug 39996 comment #93)
> There have been no new broken accounts since Sept 5th (possibly earlier).
> Yay!
> 
> Closing this as fixed, but I'll keep an eye on it to make sure it doesn't
> come back.

*** This bug has been marked as a duplicate of bug 39996 ***

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


Navigation
Links