Opened on 03/26/2014 at 08:58:59 AM
Closed on 03/26/2014 at 10:45:03 AM
Last modified on 03/26/2014 at 10:49:04 AM
#214 closed defect (fixed)
ABP forum just shows an nginx error
| Reported by: | philll | Assignee: | trev |
|---|---|---|---|
| Priority: | P1 | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Platform: | ||
| Ready: | no | Confidential: | no |
| Tester: | Verified working: | yes | |
| Review URL(s): | |||
Description
How to reproduce
Observed behaviour
The following note is displayed:
An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. If you are the system administrator of this resource then you should check the error log for details. Faithfully yours, nginx.
Expected behaviour
The Forum should be displayed
Attachments (0)
Change History (8)
comment:1 Changed on 03/26/2014 at 09:05:57 AM by trev
comment:2 Changed on 03/26/2014 at 09:19:56 AM by trev
- Resolution set to fixed
- Status changed from new to closed
Fixed but not really sure about what caused this issue. The issue report processing jobs started piling up, first issue reported at 8:27 today. It seems that the database was the bottleneck here, right now there isn't any noteworthy load there however.
comment:3 Changed on 03/26/2014 at 09:24:54 AM by philll
- Verified working set
comment:4 Changed on 03/26/2014 at 09:38:42 AM by trev
I think it is simply way too much running on that one server...
comment:5 Changed on 03/26/2014 at 09:46:37 AM by trev
Actually, what apparently made this box run out of memory was AWStats.
comment:6 Changed on 03/26/2014 at 10:30:58 AM by philll
- Resolution fixed deleted
- Status changed from closed to reopened
- Verified working unset
The forum does not respond in reasonable time again, and at some attempts also shows the nginx note.
comment:7 Changed on 03/26/2014 at 10:45:03 AM by trev
- Resolution set to fixed
- Status changed from reopened to closed
The tasks that were supposed to finish overnight were still executing, all at once. That caused a rather high load on that server. The load already went way down, in the current state I would consider it acceptable. Resolving again.
The long term solution is of course migrating more tasks away from that server, this is in progress already.
comment:8 Changed on 03/26/2014 at 10:49:04 AM by philll
- Verified working set
Looks like the cron jobs hanged up and made this server run out of memory...