I'm running HAProxy version 1.5-dev21-6b07bf7 and have a strange behaviour
issue with the check command.
Here's my config:
backend nginx
modehttp
balance leastconn
server app1app1.prod:81check inter 3s port 9700 rise 1 fall 2
maxconn 2000
Hi Jeremy,
You're checking with a TCP handshake only, which is not aware of HTTP
status response.
add option httpchk in your backend and add the keyword check-ssl
on your server lines to tell HAProxy the health check must be
ciphered.
Baptiste
On Thu, Feb 13, 2014 at 2:42 PM, Jeremy Wilson
On 2014-02-13, at 11:11 AM, Baptiste bed...@gmail.com wrote:
You're checking with a TCP handshake only, which is not aware of HTTP
status response.
add option httpchk in your backend and add the keyword check-ssl
on your server lines to tell HAProxy the health check must be
ciphered.
But
While this does not answer your question per se you can use the track
option to eliminate the duplicate check.
In other words, the SSL backend can track the checks done by the non-SSL
backend.
backend nginx-ssl
modetcp
balance leastconn
server app1
Baptiste gave you the proper answer already. The SSL backend is using TCP
mode, so the check is a TCP check without the `option httpchk` defined on
the backend, which just checks that the port is open. Add the httpchk
option without check-ssl and you will be all set. Or you can use track to
skip
5 matches
Mail list logo