Page MenuHomePhabricator

MediaWiki periodic job update-special-pages-s7 failed
Closed, ResolvedPublicPRODUCTION ERROR

Description

Common information

  • alertname: MediaWikiCronJobFailed
  • label_cronjob: update-special-pages-s7
  • label_team: mediawiki-special-pages
  • prometheus: k8s
  • severity: task
  • site: codfw
  • source: prometheus
  • team: mediawiki-special-pages

Firing alerts


Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Production Error". · View Herald TranscriptFeb 10 2026, 6:57 AM
Restricted Application added subscribers: A_smart_kitten, Aklapper. · View Herald Transcript

Hello serviceops! Please could you get the stack trace and error time for this when an SRE has some time spare?

@Blake this seems similar to T416440 , could you PTAL?

Also I know that @Clement_Goubert did some work in T412799 (and parent task) to allow those alerts to be more self service, could it be used here?

I cleared the job out this morning, it was identical to the failure mode in T416440, which means (imo) that we should address it in the same way we address the category of mw-cron failures we examine in T416576.

From logstash:

@timestamp
	Feb 10, 2026 @ 06:51:37.026

fawiki Mostlinkedtemplates            [QueryPage] Wikimedia\Rdbms\DBQueryError from line 1226 of /srv/mediawiki/php-1.46.0-wmf.14/includes/libs/Rdbms/Database/Database.php: Error 1290: The MariaDB server is running with the --read-only option so it cannot execute this statement

I'm not sure what logstash ACLs are like. @A_smart_kitten, are you able to use the logstash links in these tickets, or are those locked down? Thanks!

@A_smart_kitten, are you able to use the logstash links in these tickets, or are those locked down?

No, I'm not personally able to access those links.


(In case you're interested -- for some context about why I do anything with these cron-job failure tickets myself...

[...] I just try to do a bit of volunteer initial triaging of the cron-job failure tasks that get filed in unstewarded components...to try to prevent them from just sitting here forever, lol. [...]

See also T341555#10760093 & the following comments there for some additional context.)

Ah, okay, thanks very much - hopefully the work in T416576 will reduce the number of unactionable cron failures we receive alerts for.

For now, the failed job has been cleaned up, and there's nothing more to do here.