Closed
Bug 1350282
Opened 7 years ago
Closed 7 years ago
update Etherpad to see if newer version fixes recurring hang
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Usul, Assigned: danielh)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4482])
https://public.etherpad-mozilla.org/p/ace-community-meeting-2017-03-22 doesn't load I end up with : Service Unavailable The service is temporarily unavailable. Please try again later. no alerts on our monitoring that alerted me.
Reporter | ||
Comment 1•7 years ago
|
||
Tried to create a new pad. it failed with service unavailable.
Reporter | ||
Comment 2•7 years ago
|
||
11:08:26 <TheOne> example: https://public.etherpad-mozilla.org/p/ace-community-meeting-2017-03-22 does not load
Reporter | ||
Updated•7 years ago
|
Assignee: server-ops-webops → dhartnell
Reporter | ||
Comment 3•7 years ago
|
||
11:49:00 Hey Usul: I think it should be coming back up now.
Assignee | ||
Comment 4•7 years ago
|
||
I restarted the Etherpad service and it came back up. I noticed that the following log entries were common until 02:47. At that point, they seem to stop and users began leaving pads. I suspect that's when the issue started?
>[2017-03-24 02:47:54.521] [INFO] ueberDB - Flushed 1 values
>[2017-03-24 02:47:55.125] [INFO] ueberDB - Flushed 3 values
>[2017-03-24 02:47:55.630] [INFO] ueberDB - Flushed 3 values
>[2017-03-24 02:48:06.196] [INFO] access - [LEAVE] Pad
So my guess is that the problem lies within the ueberDB Node module. Whatever is happening in returning non-200 responses codes and then it looks like the load balancer is failing to detect a healthy node when it performs a health check. I'm guessing that Supervisor is not restarting the service (it is configured to do so) because the Node app itself never crashes.
Let's git pull etherpad. It's been a year or so.
Summary: Etherpad is slow → update Etherpad to see if newer version fixes recurring hang
Assignee | ||
Comment 6•7 years ago
|
||
I have run git pull on etherpad2.webapp.scl3.mozilla.com. We confirmed that it is functioning after restarting the Node application. I noticed the src/package.json file was updated so I also ran npm install in the src directory to try and install any new packages.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•