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 <[email protected]> wrote: > Hey Andrew, > > On January 18, 2017 at 16:11:55, Andrew Smalley ([email protected]) > 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 > monitoring requests which match the "monitor fail" condition > > > Just for clarification here, the position of 503 is in the spot where the > size of the data transfer is. So unless there's some awkward parsing, this > 503 is not the error code in this case. I don't have custom log > configurations, so I'm sitting here assuming that the -1 is where the > status code ought to be. 5 positions of timing sperated by a '/', all of > which look kinda legit considering the termination state. Followed by a > status code, in my case -1, followed by 'bytes read', in my case 503. > > > > 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 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.haproxy.org_download_1.8_doc_configuration.txt&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=GiiC4TVdGbzFCfZGDkpcTywIdoCnM1Kgv4suMqOzD4g&e=> > > Regards > > Andrew Smalley > > Loadbalancer.org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__Loadbalancer.org&d=DwQFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=9VAKw6fPcw4bgwa4ZZ5g30iBgrU8I87s2NLj9RtNS8k&e=> > Ltd. > > > > On 18 January 2017 at 21:04, Skarbek, John <[email protected]> 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 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__example.com&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=rVGKpj8lBzmpcsTWBeR-JR-YDkcA08JRHUsWpYebjsY&e=> >> Jan 18 20:47:18 haproxy[23541]: 10.0.0.1:24550 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.0.1-3A24550&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=OmZiLVKEJIeEmXvJsOVrjzEQXFB3hK697UGrmvHIwa0&e=> >> [18/Jan/2017:20:47:16.412] fe~ be/10.1.0.1:3001 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.1.0.1-3A3001&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=JAiA9z8KsgcL3oroTfHr9RRyoCD6Awkvs-6rgfQA--Q&e=> >> 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 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__example.com&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=rVGKpj8lBzmpcsTWBeR-JR-YDkcA08JRHUsWpYebjsY&e=> >> Jan 18 20:44:01 haproxy[23445]: 10.0.0.1:2650 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.0.1-3A2650&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=RneYJ3UQM4mmeZ5AWk23jTZmS9Y3JhjhsJ_9jBME3FM&e=> >> [18/Jan/2017:20:43:59.295] fe~ be/10.1.0.1:3001 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.1.0.1-3A3001&d=DwMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=b87qjQFK8K4apKyQD1BRDmLyeFvTP-6Rdt37uvE26rI&s=JAiA9z8KsgcL3oroTfHr9RRyoCD6Awkvs-6rgfQA--Q&e=> >> 501/0/1349/-1/2079 -1 503 - - CDNN 2249/86/6/1/0 0/0 "GET /healthcheck >> HTTP/1.1" >> >> > >
