Hi,
indeed after removing the option tcp-check line the checks now work as
expected. Thanks for the pointer.

Regards,
  Dennis

On 19.09.2014 20:02, PiBa-NL wrote:
> Hi Dennis,
> 
> option tcp-check << that requires more send/expect options to actually
> perform L7 checks.
> For a simple L4 check remove the line completely or add :  tcp-check
> connect
> You might also want to look at option httpchk. Which is more friendly
> for basic http checks.
> 
> Greets PiBa-NL
> 
> Dennis Jacobfeuerborn schreef op 19-9-2014 19:45:
>> Hi,
>> I just configured the load-balacing for systems that are yet to be
>> installed yet according to the tcp-check of haproxy these systems are
>> all available. This is the backend config I'm using right now:
>>
>> backend back-api
>>      bind-process 1
>>      option tcp-check
>>      mode http
>>      balance roundrobin
>>
>>      stick-table type ip size 100k expire 20m
>>      stick on src
>>      server web1 10.2.0.224:80 check
>>      server web2 10.2.0.254:80 check
>>      server web3 10.2.0.223:80 check
>>      server web4 10.2.0.253:80 check
>>      server web5 10.2.0.222:80 check
>>      server web6 10.2.0.252:80 check
>>
>> When I look at the stats page all servers are marked active and LastChk
>> says "Layer7 check passed: (tcp-check)" even though none of the servers
>> are online yet.
>>
>> Does anyone know the reason for this?
>>
>> Regards,
>>    Dennis
>>
> 
> 


Reply via email to