#2728 - Website gateway time-outs and freezes
-
By PDStig
- Added
- 0 views
| Identifier | #2728 |
|---|---|
| Issue type | Major issue (breaks an entire feature) |
| Title | Website gateway time-outs and freezes |
| Status | Closed (no changes needed) |
| Handling member | Chris Graham |
| Addon | core |
| Description | My Composr CMS 10 RC13 website lovinity.org has been experiencing random issues. Specifically, every now and then it will stop responding for me and throw a gateway timeout error after 30+ seconds of trying to load something.
This usually happens when first accessing the site as it tries to log me in via. Facebook Connect. Thus, I suspect it may be a Facebook Connect addon issue. However, it also just happened to me when trying to reply to something on a forum topic. My facebook app is showing no API errors. |
| Steps to reproduce | |
| Additional information | It seems a little odd also that when the add reply did work, the server threw a 302 moved temporarily header. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
I believe you have both cloudflare and nginx as reverse proxies in front of Apache, so most likely the complexity of this configuration is leading to complex issues. A gateway timeout comes from a reverse proxy, obscuring any error behind it (if there is one). It could be the queueing behaviour of these products, and therefore some issue somewhere else entirely.
You'd need to be able to do intensive diagnostics in a complex configuration like this, checking server load, queued processes at each server level, free memory, process counts, CPU usage, blocking IO, MySQL processlist, etc etc.
I wouldn't advise anyone create a configuration more complex than is truly needed, and with complexity requires a lot of sysadmin experience. Particularly I doubt nginx is needed, as there's already static caching and DOS prevention in Composr which are the usual 'selling points' of putting nginx in front of Apache.