On Mon, Apr 7, 2014 at 5:44 PM, Bryan Talbot <[email protected]> wrote: >> > I finally captured some 504s in the debug logging. 129 since yesterday >> > afternoon. They all seem to look like this: >> > Mar 30 14:46:19.000 haproxy-k49 haproxy[19450]: x.x.x.x:49638 >> > [30/Mar/2014:14:45:19.533] frontend_https~ tapp_http/tapp-m2t >> > 77/0/4/60000/60081 504 343 - - ---- 1255/1255/17/4/0 0/0 "GET /data/?a=b >> > HTTP/1.1" >> > >> > I'm guessing that the 60000/60081 means that 60s is some timeout >> > threshold, >> > and 60.081 seconds were reached, which caused the 504. Is that correct? >> > > > Just got around to reading this older post and this doesn't look like a > timeout in haproxy to me since the termination code is "----". Don't haproxy > client / server timeouts result in a termination code starting with "sH" or > "cH"? Seems like the backend (or something else in the chain) is returning > the 504 to me. > > > -Bryan >
504 may have been generated by a proxy/server/whatever behind HAProxy. Or there might be a bug in HAProxy :) Baptiste
