Topic on Project:Support desk

Tracked in Phabricator
Task T371849

Hi,

I am upgrading mediawiki from 1.33.1 to 1.42.1. I used a 1.35 version to upgrade DB without error. But now I get an error logging in

[eb40b7f6f59133a091c0fa4a] /index.php/Speciale:Entra Wikimedia\Rdbms\DBQueryError: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading or after adding a new extension?

Please see <nowiki>https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Upgrading</nowiki> and <nowiki>https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:How_to_debug</nowiki> for more information.

Error 1146: Table 'my_wiki.oathauth_devices' doesn't exist

Function: MediaWiki\Extension\OATHAuth\OATHUserRepository::loadKeysFromDatabase

Query: SELECT oad_id,oad_data,oat_name FROM `oathauth_devices` JOIN `oathauth_types` ON ((oat_id = oad_type)) WHERE oad_user = 1

So i tried the web-version of the upgrader. and I get this error.

Running /var/www/html/mediawiki/extensions/OATHAuth/maintenance/UpdateForMultipleDevicesSupport.php...

An error occurred:

Error 1049: Unknown database 'virtual'

Function: Wikimedia\Rdbms\DatabaseMySQL::doSelectDomain

Query: USE `virtual`

Any clue? I think that the upgrading script it's getting stucked in that part. Oauth is not something I need I think

Multiple people have reported this, however we are having trouble seeing the error ourselves and haven't been able to figure out the cause. If there is anything special about your install please let us know.

Yes, a work around is to disable the oathAuth extension if you dont need 2fa.

Thanks for reply We are testing if we can use it as a company repository for guides and internal know how. If you need some file to track the bug I can send it to you

If I'll need oauth maybe I'll export the few pages and put it into a new fresh install

Best

We believe this is a problem with the web upgrader that can be worked around by using the command line update.php script

I am experiencing the same problem after upgrading from v1.40 to 1.42.1.

Running php maintenance/run.php update does not solve the problem.

Only workaround for now was to disable the extension.