Re: haproxy / Python 'tornado' framework - digging into 502/504 errors

Hi Alex,

Le Mercredi 14 Septembre 2011 07:20:33 Alex Davies a écrit :
> 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:
>
> [root#frontend2 log]# ps aux | grep haproxy
> haproxy 21242 6.6 0.1 133176 47984 ? Rs 07:17 0:00
> /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid
> [root#frontend2 log]# service haproxy stop; service rsyslog stop; rm -f
> /var/log/haproxy.log; service rsyslog start; service haproxy start;
> Stopping haproxy: [ OK ]
> Shutting down system logger: [ OK ]
> Starting system logger: [ OK ]
> Starting haproxy: [ OK ]
> [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"
> ^C

Are you sure you still have 504 errors just after a restart ? The lines you've provided are not 504 but 502 errors. Your "grep" matched on the client port (3504, 49504).

-- 
Cyril Bonté