On Sat, Oct 8, 2016 at 12:46 AM, cloud maverick <xcloudmaver...@gmail.com>
wrote:
> haproxy check is
> like
> option httpchk HEAD /HTTP/1.1\r\nHOST:xxxxxxxx.
> com/api/checkusername/zabbix
> http-check expect rstring true
>
> Response in status log
>
> Health check for server BE_Services_HTTPS_VIP/node1 failed, reason: Layer7
> invalid response, info: "b'
> {<22>success<22>:true}
>
> '", check duration: 137ms, status: 0/2 DOWN.
> Server BE_Services_HTTPS_VIP/node1 is DOWN. 1 active and 0 backup servers
> left. 0 sessions active, 0 requeued, 0 remaining in queue.
> Health check for server BE_Services_HTTPS_VIP/node2 failed, reason: Layer7
> invalid response, info: "b'
> {<22>success<22>:true}
>
> '", check duration: 205ms, status: 0/2 DOWN.
> Server BE_Services_HTTPS_VIP/node2 is DOWN. 0 active and 0 backup servers
> left. 0 sessions active, 0 requeued, 0 remaining in queue.
> proxy BE_Services_HTTPS_VIP has no server available!
>
What does curl show you for the page you are checking?
curl -ksSLi xxxxxxxx.com/api/checkusername/zabbix
<http://xxxxxxxx.com/api/checkusername/zabbix>
<http://xxxxxxxx.com/api/checkusername/zabbix>
