Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've following setup:

HA-Proxy version 1.4.24 2013/06/17

I am using it to balance load on my Windows terminal services, with following configuration:

global
    log         127.0.0.1 local2
    chroot      /var/lib/haproxy
    pidfile     /var/run/haproxy.pid
    maxconn     4000
    user        haproxy
    group       haproxy
    daemon

# turn on stats unix socket
stats socket /var/lib/haproxy/stats


defaults
    mode http
    balance roundrobin
    timeout connect 4000
    timeout client 90s
    timeout server 90s

listen VIP1 *:3389
    mode tcp
    #tcp-request inspect-delay 5s
    #tcp-request content accept if RDP_COOKIE
    stick store-request src
    stick-table type ip size 204k expire 120m
    stick on src
    balance source
    option tcpka
    option redispatch
    option abortonclose
    log         127.0.0.1 local2
    option tcplog
    server R1 server1:3389 weight 40 check port 3389 inter 2000 rise 2 fall 3 
    server R2 server2:3389 weight 25 check port 3389 inter 2000 rise 2 fall 3
    server R2 server3:3389 weight 25 check port 3389 inter 2000 rise 2 fall 3

Why clients regularly get to other server after reboot?

Checked dhcp lease time - it is 7200 seconds, so it can't be that client changed it's ip address.

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.