Page MenuHomeMiraheze

503 Backend fetch failed errors lasting a few minutes
Closed, ResolvedPublic

Description

There were two first instances (first at 10:11 UTC second at 10:25 UTC). Not sure if there's much we could investigate but I think it's worth having a look to see if we can figure out what's going on.

UBN for now at least until it's back up

Edit: it seems to still be intermittently going up and down

Event Timeline

Reception123 triaged this task as Unbreak Now! priority.Jun 26 2021, 10:27
Reception123 created this task.
Reception123 lowered the priority of this task from Unbreak Now! to High.Jun 26 2021, 10:29

Back up now. I'm tagging as Site Reliability Engineering simply because I have no idea whether this is MW related or rather Infra related.

Reception123 raised the priority of this task from High to Unbreak Now!.Jun 26 2021, 10:39

The errors are back now, will keep this as UBN until we figure it out.

@PiscesKazeMGR Removed your comment as you inadvertently included your IP there. There's no need to share again as we're quite familiar with the error and unlike MWExceptions the ID isn't that useful, but thanks :)

It now seems that a new error has appeared: (Cannot access the database: Cannot access the database: Unknown error (db11.miraheze.org))

Db11 load is also unusually high.

Db11 load is also unusually high.

See subtask

GlobalNewFiles is currently disabled.

GlobaNewFiles is currently disabled.

You mean GlobalNewFiles?

GlobaNewFiles is currently disabled.

You mean GlobalNewFiles?

Corrected

Reception123 lowered the priority of this task from Unbreak Now! to High.Jun 26 2021, 13:13

Lowering status as this is now very likely temporarily fixed.

Reception123 closed this task as Resolved.EditedJun 26 2021, 13:13
Reception123 claimed this task.

Closing in favour of keeping T7532 to address the specific database-related problem rather than just the 503 whose cause is now known.