To add to this, this only happens in http-keep-alive mode and it appears to be closing the connection without sending a response back if it is not the first transaction in the keep-alive session and there is a server side connection timeout. If I use option httpclose there are no status codes of -1 but this is not a solution.
As our use of HAProxy in this case is server-to-server we need to always respond with valid HTTP, otherwise we get throttled as it appears to be an HTTP timeout. We use errorfile to inject a Connection: close header (and 204/200 response) for these cases that the calling server (client) library should respect and try to re-establish a connection. We are continuing to dig, just thought I'd update. On Wed, Nov 12, 2014 at 9:28 PM, Tait Clarridge <[email protected]> wrote: > Just saw this initial message in its plain text form - that's the last > time I send a mailing list message with that mail client. > > Here is the original message: > ---------------------------------------------------------- > Hello, > > Recently I noticed log lines with a status code of -1, not sure how > long this has been going on for however so not sure if it is a new > issue or an older one. > > In our environment we set strict timeouts as requests (once we get > them) need to be processed in < 80ms. > > A cleaned up version of the config is located > here:http://pastebin.com/FK3KG1Gi > > > They always happen with a backend server connect timeout, but I also > see 503 responded for the same type of timeout. > > Logs (custom log format removed): > > Nov 12 21:07:53 haproxy[13800]: x.x.x.x:xx [12/Nov/2014:21:07:53.646] > incoming bproxy-client1/server1 0/0/-1/-1/4 503 27 - - sC-- > 2046/2046/3/1/0 0/0 "POST /url/here HTTP/1.1" > Nov 12 21:07:53 haproxy[13800]: x.x.x.x:xx [12/Nov/2014:21:07:53.608] > incoming bproxy-client1/server1 38/0/-1/-1/43 -1 0 - - sC-- > 2047/2047/2/1/0 0/0 "POST /url/here HTTP/1.1” > > I know the default status of each txn is set to -1, so I’m not sure if > this is bailing out along the line. > > This issue is reproducible on 1.5.{dev24, 4, 8} > > I am working on reproducing this outside of production. > > Thanks! > Tait
