Actions
Bug #2441
closedhaproxy, rgw: returns 502
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We see occasional 502 responses that originate at haproxy. The apache and rgw logs don't have any indications about something going wrong. I do see a correlation to xinetd on the rgw machine being restarted a few seconds after the event, not sure if that's a symptom of the issue or a result of it.
Updated by Yehuda Sadeh almost 12 years ago
Our haproxy configuration was broken (values are in milliseconds, not in seconds):
timeout check 6 timeout connect 2 timeout http-request 3
This probably has caused the problem, though the issue takes some time to trigger so I'll wait a bit before closing this bug.
Updated by Yehuda Sadeh almost 12 years ago
- Status changed from New to Resolved
Ok, hasn't reproduced anymore. Resolving.
Actions