You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Stuck global renames
Jump to navigation Jump to search
Recovering a "locked" account
- This section needs review for accuracy.
Sometimes you'll find that a rename becomes stuck at a project (see for example phab:T137973). In that case, please follow this instructions:
- Wait at least 3 hours since the rename started. The system will automatically retry failed renames a few times.
- Please open a task in Phabricator (direct link with title and projects already added). In there please post a link to the Special:GlobalRenameProgress link to the account whose rename has become stuck.
- Developers should see if there are exceptions or errors in flourine/Logstash before continuing. Searching/grepping for "Rename" should catch most things.
- Any user with access to
terbiumcan run the fixStuckGlobalRename.php maintenance script to requeue the job. Before running the script, verify if the jobs are running. This is important. That can be done using
showJobs.php. If jobs aren't running, you can proceed with:
you@terbium:~$ mwscript extensions/CentralAuth/maintenance/fixStuckGlobalRename.php --wiki= --logwiki=metawiki "OldName" "NewName"
wiki: the database name of the wiki where the rename job has become stuck, i.e. ptwiki. If it is stuck on multiple wikis, use the one that comes first alphabetically.
logwiki: the database name of the wiki where the global rename was started and will always be metawiki.
"OldName": the old username. Should be in quotations.
"NewName": the new username. Should be in quotations.
--ignorestatusis a parameter that can be added to fix a global rename when we want the script to ignore any running jobs; use with caution.