Error 1146: Table 'periloustimeswiki.mws_title_index' doesn't exist -- Yep

Error 1146: Table 'periloustimeswiki.mws_user_index' doesn't exist
Function: MWStake\MediaWiki\Component\CommonWebAPIs\UserIndexUpdater::store
Query: INSERT INTO mws_user_index (mui_user_id,mui_user_name,mui_user_real_name) VALUES (78,'amanda catherine','') ON DUPLICATE KEY UPDATE mui_user_id = 78,mui_user_name = 'amanda catherine',mui_user_real_name = ''

In T10927#220335, @AmandaCath wrote:

In T10927#220291, @AmandaCath wrote:

Wiki is completely inaccessible.

[37c67317f876c29df5a31809] 2023-06-06 22:10:43: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"

Wiki is completely inaccessible.

Config change has been merged to remove read only, leaving the task open as a long-term goal for tuning mysql better.

Unfortunately due to IRL circumstances I don't currently have the time to build or maintain the wiki, so I'm not going to go through with any major changes right now.

Will you proceed with this? Otherwise, this task will be closed soon.

Read only on restart will be addressed here whenever I or someone else get the chance to deploy it.

This has continued to happen as of late. Moving priority to high as it affects all wikis on db121, though if wished to be moved back down, that's fine as well.

I believe the database has been unlocked now by Reception123, so marking this as resolved.

Confirmed wiki database name does not exist, so triaged this. Your request is in the queue.

https://goalvision.miraheze.org/wiki/Main_Page already exists and as such is not available for being renamed to.

Can someone else please confirm that ManageWiki backups aren't restorable? Not that I don't trust you, but it seems like a major bug that should be addressed.

There is no way to reset the user table unfortunately as it breaks MediaWiki entirely.

If ManageWiki backups aren't restorable, that kind of defeats the purpose of having them, doesn't it? Why is this a feature in DataDump if it doesn't work?

I believe ManageWiki backups aren't restorable at the moment so you'll have to restore ManageWiki configurations once reset. As for the dump import, please request that on Meta via Special:RequestImportDump and once that's done, we'll proceed with the reset.

Fixed. I would propose to Infrastructure (SRE) that read only for db121 is disabled until the issue is definitively fixed.

SREs are aware but unfortunately, there is no one with access to handle unlocking the database.

Thanks!

Once again, this pings dozens of people. I will send you a Meta talk page message.

Isai I had made a request if we could just set it so images don't display or even to delete all images as a last-resort alternative to deleting the entire thing, so that we could at least retain records for the text and source code and rebuild the images from scratch w/ mandatory disclaimer prompts.

I intend to reevaluate this task at some point soon, hopefully. It seems likely, based on the changes MW side that this is most likely caused by something on the configuration side of the DB. I can't guarantee that I have the knowledge/ability to solve, but I'll see what I can do.