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 unexpectedly aborted during data transfer. This can be
caused by a browser crash, by an intermediate equipment between the
client and haproxy which decided to actively break the connection,
by network routing issues between the client and haproxy, or by a
keep-alive session between the server and the client terminated first
by the client.
NN No cookie was provided by the client, none was inserted in the
response. For instance, this can be in insert mode with "postonly"
set on a GET request.
More information could be provided with a valid configuration
I hope this helps?
I took the information from the Documents available here
http://www.haproxy.org/download/1.8/doc/configuration.txt
Regards
Andrew Smalley
Loadbalancer.org Ltd.
On 18 January 2017 at 21:04, Skarbek, John <john.skar...@ca.com> 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. 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/10.1.0.1:3001 282/0/1490/-1/1824 -1 503 - -
> CDNN 2296/96/12/4/0 0/0 "GET /healthcheck HTTP/1.1"
> Jan 18 13:44:01 example.com Jan 18 20:44:01 haproxy[23445]: 10.0.0.1:2650
> [18/Jan/2017:20:43:59.295] fe~ be/10.1.0.1:3001 501/0/1349/-1/2079 -1 503 - -
> CDNN 2249/86/6/1/0 0/0 "GET /healthcheck HTTP/1.1"
>
>
