Closed Bug 1122831 Opened 9 years ago Closed 9 years ago

504 when publishing new tiles

Categories

(Content Services Graveyard :: Tiles: Ops, defect)

Product:
Content Services Graveyard
Component:
Tiles: Ops
Type:
defect
Priority:
Not set
Severity:
normal
Points:
3

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Iteration:
38.1 - 26 Jan

People

(Reporter: Mardak, Assigned: relud)

References

Details

(Whiteboard: .002) 

Whether I publish or publish&deploy, I'm getting 504. I'm not sure if it's related to bug 1122828 where a previous upload might have been interrupted by the disconnect for not being keepalived.
I was able to publish and deploy existing tiles from last week. I'll try with the new tiles again.
Looks like republishing the old tiles got the server in an okay state. The new tiles are published. I don't really have much information from my side to help debug though.

While it was still giving 504, I tried to change the new tile url to see if it would generate a new tile id, but that didn't help.
The only message I got from the tiles authoring UI is "504" in red.
The issue currently appears to have been a gunicorn worker timeout. Gunicorn timeout has been increased from 180 seconds to 600 seconds.

Relevant log, indicating timeout:

2015-01-17 00:57:26 [10013] [CRITICAL] WORKER TIMEOUT (pid:27483)

and similar log entries.
relud ended up increasing the config for a longer timeout. The thinking is I happened to hit a burst of upload speed when I was successful. The last few tests of publish but not deploy took 90-100sec. That should have been within the original timeout though.
Assignee: nobody → dthornton
Status: NEW → RESOLVED
Points: --- → 3
Closed: 9 years ago
Component: Tiles: Administration Front-End → Tiles: Ops
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.