I attempted to launch Void-bot (which checks a config page on metawiki before connecting to IRC) and received an ambiguous error that the script could not login as Void-bot. I therefore opened a new browser and attempted a manual login and received the specific error (Cannot access the database: Cannot access the database: Unknown database '0' (81.4.125.112)). @John mentioned on IRC that 0 is impossible for a db name. When I view any page later, it treats it as though the login was successful. I do not recieve this error when logging into my main Void account.
Description
Description
Event Timeline
Comment Actions
https://meta.miraheze.org/w/index.php?title=Special%3ACentralAuth&target=Void-bot Confuses me as '0' definitely doesn't exist even if impossible, there's no reason for the database 0 to be called.
Comment Actions
Well, as a temporary solution, I could create a new account and attempt to use that in the meantime. I'll see if I can figure out anything else about it.
Comment Actions
I also experienced this issue when attempting to login as Void-test. I do not encounter it with the new account.
Comment Actions
I can now confirm this error when trying to also sign in with my alt account, but I did get signed in anyway.
Comment Actions
This just propagated to the account Void-bot2
Actually, it currently affects all the alternate accounts I have.
Comment Actions
Well there is definitely no database called '0' on db2, or an entry in cw_wikis like that, so I don't know why this database is being called upon login.
Comment Actions
15:10:33 mw1 metawiki: [64f3b206dedac3b17e53f55b] /w/api.php?format=xml&rawcontinue=1&maxlag=5&action=login Wikimedia\Rdbms\DBConnectionError from line 769 of /srv/mediawiki/w/includes/libs/rdbms/database/Database.php: Cannot access the database: Unknown database '0' (81.4.125.112)
Comment Actions
Please see upstream task https://phabricator.wikimedia.org/T167354. We want to backport https://gerrit.wikimedia.org/r/#/c/358152/ (https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsupported_release) to REL1_29, but using REL1_30 may be a quicker fix.