[00:06:13] Yeah after some pondering I think these are generally short intermittent issues that just hit a few people every minute because we just have that much traffic, so I think it should be safe to ignore... Though one of our users says right now that they sometimes have to null-edit to fix broken links after moving images... [00:08:00] The server is quite overloaded a lot of the time (and it's a crappy cheap "VPS" read Virtuozzo container from Strato AG) so maybe the jobs to auto-update don't run quick enough sometimes. [00:08:40] "load average: 5.51, 6.50, 8.08" 8 cores so a load average of 8.08 is ... impressive xD [06:00:49] gromit: hi, thanks! could you leave a comment on https://phabricator.wikimedia.org/T330367 ? also just to make sure, you're the same person who did the most recent update, right? (ty!) [08:39:46] legoktm: did so! Yes, I am christian-heusel on GitHub [14:12:42] I upgraded a wiki from 1.32 to 1.39.5 last night, and I've gotten a couple reports from users that some pages show as "Error" and say that revision 0 is missing when trying to edit. I came across a recommendation to use FindAnomalies.php, but that has been removed and the source code is non-functional when re-added. I confirmed that the pages do still exist in the database, but I'm not sure how to proceed from here. [14:28:21] Since Version 1.36, MediaWiki only commits to supporting upgrades from two LTS releases ago (see phab:T259771). Upgrades from older versions of MediaWiki will have to be performed in multiple steps. This means that if you want to upgrade to 1.40 from 1.34 or earlier, you'll first have to upgrade your 1.34 wiki to 1.35 (or 1.39), and, from 1.35 (or 1.39), you'll be able to upgrade to 1.40. [14:28:22] T259771: RFC: Drop support for older database upgrades - https://phabricator.wikimedia.org/T259771 [14:28:28] per https://www.mediawiki.org/wiki/Manual:Upgrading [14:54:29] That's good to know, thank you. [14:54:50] Glad I found this out quick. I'll just restore the backup and do it in two stages. [14:56:38] jfolv: be sure you run update.php from the command line and watch for any errors. If you get an error running any of the scripts, stop and analyze it before continuing [14:59:33] the update.php from 1.32 to 1.35 runs maintenance/migrateActors.php internally, which is known to fail under some circumstances because of referential integrity issues (due to historical errors, external imports or extensions that delete user accounts improperly) [15:01:03] The script "cleanupUsersWithNoId.php" is usually needed to run first to correct most of those errors. However, if it fails to find or fix all of them (to the point it runs without errors but migrateActors.php fails), you can try my modification at https://gist.github.com/ciencia/7cbe63b8520d4816ec36733454a2cb9a