On Wed, Sep 14, 2011 at 07:20:33AM +0100, Alex Davies wrote:
> Hi Willy, Cyril,
>
> Thank you for your detailed analysis. I still notice 504 errors almost
> immediately on a HAproxy start, and the PID matches the new process:
Sorry, but this is not possible as it requires the timeout to be elapsed.
> [root@frontend2 log]# tail -f haproxy.log | grep 504
> Sep 14 07:16:14 localhost haproxy[21178]:
> 94.197.40.185:3504[14/Sep/2011:07:16:08.216] main
> python_8001/python_8001_fe1 80/0/0/-1/6449
> 502 204 - - SH-- 3375/3375/950/950/0 0/0 "POST /xxx/chat/status/updates
> HTTP/1.1"
> Sep 14 07:16:15 localhost haproxy[21178]:
> 118.101.95.88:49504[14/Sep/2011:07:16:10.298] main
> python_9003/python_9003_fe1 22/0/0/-1/5088
> 502 204 - - SH-- 3312/3312/386/386/0 0/0 "POST /xxx/chat/message/3/updates
> HTTP/1.1"
Look closely, those are 502 not 504.
The most important are the termination flags. SH means connection aborted
by the server ('S') while haproxy was waiting for it to emit response
headers ('H').
Regards,
Willy
