Re: Status code "-1" in logs

2017-01-19 Thread Andrew Smalley
Hello John Thank you for your clarification, I guess its an easy mistake to make when you see a 503 and assume its the error when I knew you were talking about the "-1" issue. Regards Andrew Smalley Loadbalancer.org Ltd. On 19 January 2017 at 00:24, Skarbek, John wrote: > Hey Andrew, >

Re: Status code "-1" in logs

2017-01-18 Thread Skarbek, John
Hey Andrew, On January 18, 2017 at 16:11:55, Andrew Smalley (asmal...@loadbalancer.org) wrote: Hello John The problem is you are getting a 503 error or no servers available. 503 when no server was available to handle the request, or in response to

Re: Status code "-1" in logs

2017-01-18 Thread Michael Ezzell
On Jan 18, 2017 4:06 PM, "Skarbek, John" wrote: Good Morning, I was spying on my logs and something out of the ordinary popped out at me. We are getting a status code of -1. This (-1) is the marker for a null/nil/NaN/non-existent/inapplicable values. The associated timer is not applicable to

Re: Status code "-1" in logs

2017-01-18 Thread Andrew Smalley
Hello John The problem is you are getting a 503 error or no servers available. 503 when no server was available to handle the request, or in response to monitoring requests which match the "monitor fail" condition And the CDNN is actually two errors CD and NN CD The client unexp

Status code "-1" in logs

2017-01-18 Thread Skarbek, John
Good Morning, I was spying on my logs and something out of the ordinary popped out at me. We are getting a status code of -1. The status CDNN is odd enough as it is… Why would this be? Jan 18 13:47:18 example.com Jan 18 20:47:18 haproxy[23541]: 10.0.0.1:24550 [18/Jan/2017:20:47:16.412] fe~ be/