Check to backend tcp server marked wrongfully as down

@shpa wrote:

Hey all,

Seeing a weird issue with HAProxy in TCP Mode.

I have the following configuration:

global
  description haproxy-1
  log 127.0.0.1 local0 info
  maxconn 2000
  uid 200
  gid 200
  chroot /var/empty
  daemon

defaults
  mode tcp
  log global
  option tcplog
  option logasap
  option log-health-checks
  option redispatch
  option tcpka
  retries 3
  timeout connect 5s
  timeout client 50000
  timeout server 50000

listen TM_IN
  bind :7101
  timeout client 3h
  timeout server 3h
  option tcp-check
  balance roundrobin
  server prime_tm server1:7101 check inter 1000
  server backup_tm server2:7101 check inter 1000 backup

listen TC_OUT
  bind :7201
  timeout client 3h
  timeout server 3h
  option tcp-check
  balance roundrobin
  server prime_tc server1:7201 check inter 1000
  server backup_tc server2:7201 check inter 1000 backup

listen stats
  bind :80
  mode http
  option httplog
  option contstats
  stats enable
  stats realm Haproxy\ Statistics
  stats hide-version
  stats uri /stats
  stats auth user:pass

With both servers up and listening:
On the status page the TC_OUT prime is getting marked as 'L4CON in 0ms' with 'Connection Refused' yet data is still flowing to that server. The TC_OUT backup is marked as 'OK'

When I turn off TC_OUT prime listening on 7201 it switches the traffic to backup but the log shows that the health checks now start failing on the backup.

I am wondering why that is happening on only the TC_OUT proxy and not TM_IN. They are logically the same yet TM_IN's prime and backup are both shown as 'OK' and 'UP' when both servers are up and correctly marked as down if either goes down.

Thanks!

Posts: 3

Participants: 2

Read full topic