haproxy, rgw: returns 502
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.
#1 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.