|
Hi,
A few weeks ago i posted a message saying that ldirectord suddenly stops. I
have located where the problem occurs, but i hava no idea how to solve this.
I suspect only a ldirectord maintainer can ...
Situation as it is: 2 test boxes running LVS-DR/heartbeat/ldirectord. Here
is my configuration
:: ldirectord.cf ::
# Global
logfile="local0"
callback="/etc/ha.d/scpsync"
autoreload = yes
# RDP Terminal Servers
virtual = 192.168.51.210:3389
protocol=tcp
scheduler=wlc
checkport=3389
checktype=connect
real=192.168.50.14:3389 gate 1
real=192.168.50.18:3389 gate 1
persistent=43200
# Citrix Terminal Servers
virtual = 192.168.51.211:1494
protocol=tcp
scheduler=wlc
checkport=1494
checktype=connect
real=192.168.50.121:1494 gate 1
real=192.168.50.122:1494 gate 1
# Local SSH
virtual = 192.168.51.212:22
protocol = tcp
scheduler = wlc
real=127.0.0.1:22 gate 1
:: the current situation of ipvsadm -ln output ::
rpzlvstest01 root # ipvsadm -ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.51.211:1494 wlc
-> 192.168.50.121:1494 Route 1 0 0
-> 192.168.50.122:1494 Route 0 0 0
TCP 192.168.51.212:22 wlc
-> 127.0.0.1:22 Local 1 0 0
TCP 192.168.51.210:3389 wlc persistent 43200
-> 192.168.50.18:3389 Route 1 0 0
-> 192.168.50.14:3389 Route 1 0 0
Okay, so the second citrix server (.122) is down (hardware problem).
Ldirectord picked this up immediately and set the server to weight=0.
Perfect. Except for the fact that right after that, ldirectord dies.
This is what i see when executing `/usr/sbin/ldirectord -d start` :
rpzlvstest01 root # /usr/sbin/ldirectord -d start
DEBUG2: Running exec(/usr/sbin/ldirectord -d start)
Running exec(/usr/sbin/ldirectord -d start)
DEBUG2: Starting Linux Director v1.77.2.37 with pid: 13604
Starting Linux Director v1.77.2.37 with pid: 13604
DEBUG2: Running system(/sbin/ipvsadm -E -t 192.168.51.210:3389 -s wlc -p
43200 )
Running system(/sbin/ipvsadm -E -t 192.168.51.210:3389 -s wlc -p 43200 )
DEBUG2: Changed virtual server: 192.168.51.210:3389
Changed virtual server: 192.168.51.210:3389
DEBUG2: Running system(/sbin/ipvsadm -E -t 192.168.51.211:1494 -s wlc )
Running system(/sbin/ipvsadm -E -t 192.168.51.211:1494 -s wlc )
DEBUG2: Changed virtual server: 192.168.51.211:1494
Changed virtual server: 192.168.51.211:1494
DEBUG2: Running system(/sbin/ipvsadm -E -t 192.168.51.212:22 -s wlc )
Running system(/sbin/ipvsadm -E -t 192.168.51.212:22 -s wlc )
DEBUG2: Changed virtual server: 192.168.51.212:22
Changed virtual server: 192.168.51.212:22
DEBUG2: Enabled server=192.168.50.14
DEBUG2: Enabled server=192.168.50.18
DEBUG2: Enabled server=192.168.50.121
DEBUG2: Enabled server=127.0.0.1
DEBUG2: Disabled server=192.168.50.122
DEBUG2: Checking connect: real
server=connect:tcp:192.168.50.14:3389:3389:1:\/:
(virtual=tcp:192.168.51.210:3389)
DEBUG3: Connected to (port 3389)
DEBUG2: Enabled server=192.168.50.14
DEBUG3: Activated service 192.168.50.14:3389
DEBUG2: Checking connect: real
server=connect:tcp:192.168.50.18:3389:3389:1:\/:
(virtual=tcp:192.168.51.210:3389)
DEBUG3: Connected to (port 3389)
DEBUG2: Enabled server=192.168.50.18
DEBUG3: Activated service 192.168.50.18:3389
DEBUG2: Checking connect: real
server=connect:tcp:192.168.50.121:1494:1494:1:\/:
(virtual=tcp:192.168.51.211:1494)
DEBUG3: Connected to (port 1494)
DEBUG2: Enabled server=192.168.50.121
DEBUG3: Activated service 192.168.50.121:1494
DEBUG2: Checking connect: real
server=connect:tcp:192.168.50.122:1494:1494:1:\/:
(virtual=tcp:192.168.51.211:1494)
DEBUG2: Disabled server=192.168.50.122
DEBUG3: Deactivated service 192.168.50.122:1494: Died at
/usr/sbin/ldirectord line 2009.
DEBUG2: Checking negotiate: real
server=negotiate:none:tcp:127.0.0.1:22::1:\/:
(virtual=tcp:192.168.51.212:22)
DEBUG2: Checking none
DEBUG2: Enabled server=127.0.0.1
Alarm clock
Weirdness .... If somebody can shed some light, i'd appreciate it :)
Léon
--
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
|
