Toolforge: 404 handler fourohfour returns 504
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• aborrero
	Feb 3 2021, 12:36 PM

Description

In the toolforge kubernetes ingress setup there is a default route that should handle 404 errors, the fourohfour tool https://k8s-status.toolforge.org/namespaces/tool-fourohfour/

There should be some error somewhere, because when visiting a random page it returns 504 instead:

The message referring to openresty indicates that the 504 is produced by the nginx-ingress inside k8s.

Event Timeline

• aborrero created this task.Feb 3 2021, 12:36 PM

Restricted Application edited projects, added cloud-services-team (Kanban); removed cloud-services-team. · View Herald TranscriptFeb 3 2021, 12:36 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

• aborrero added a subscriber: bd808.Feb 3 2021, 12:36 PM

• aborrero updated the task description. (Show Details)Feb 3 2021, 12:39 PM

• Phamhi claimed this task.Feb 3 2021, 2:00 PM

• Phamhi moved this task from Inbox to Doing on the cloud-services-team (Kanban) board.Feb 3 2021, 2:26 PM

Mentioned in SAL (#wikimedia-cloud) [2021-02-03T15:20:52Z] <wm-bot> <bd808> Restarting to see if anything changes for T273746

In T273746#6800393, @Stashbot wrote:

Mentioned in SAL (#wikimedia-cloud) [2021-02-03T15:20:52Z] <wm-bot> <bd808> Restarting to see if anything changes for T273746

This seems to have fixed the problem. The pods for fourohfour had 54 to 131 days of uptime (3 pods) and no logged errors. I didn't check the ingress there before restarting which I really should have done.

Aklapper removed • Phamhi as the assignee of this task.Apr 5 2021, 5:40 AM

• aborrero closed this task as Resolved.May 11 2021, 4:24 PM

• aborrero claimed this task.

Toolforge: 404 handler fourohfour returns 504Closed, ResolvedPublicActions

Description

Event Timeline

Toolforge: 404 handler fourohfour returns 504
Closed, ResolvedPublic
Actions