|
Hi,
First of all, thanks for the responses i got on my question about
real-server monitoring. Almost everybody that answered, advised me to use
keepalived instead of heartbeat+ldirectord since keepalived does the job by
itself, and more.
Unfortunately i'm quite short on time, and LVS is already in production, so
i couldn't switch to a whole new system and go testing again etc. I did some
reading in the manual pages of ldirectord and found that i could use these 2
lines to accomplish the real-server monitoring well enough:
checkport=3389
checktype=connect
I tested it by rebooting on of the Terminal Servers and sure enough, a few
seconds later the real-server was set to weight 0. When it came up again,
the weight was set to 1. Perfect.
This setup ran well until last night, when after the scheduled reboot of all
the terminal servers (at intervals of 10 minutes), ldirectord died. I don't
see a message in syslog or anything.. Only the last real-server wasn't added
back to the table. See what i mean in this piece of syslog:
Nov 26 02:25:02 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.13:3389 ( x 192.168.50.10:3389) (Weight set to 0)
Nov 26 02:25:08 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.18:3389 ( x 192.168.50.10:3389) (Weight set to 0)
Nov 26 02:27:08 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.13:3389 ( x 192.168.50.10:3389) (Weight set to 1)
Nov 26 02:27:08 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.18:3389 ( x 192.168.50.10:3389) (Weight set to 1)
Nov 26 02:35:24 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.17:3389 ( x 192.168.50.10:3389) (Weight set to 0)
Nov 26 02:37:28 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.17:3389 ( x 192.168.50.10:3389) (Weight set to 1)
Nov 26 02:45:04 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.16:3389 ( x 192.168.50.10:3389) (Weight set to 0)
Nov 26 02:45:49 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.15:3389 ( x 192.168.50.10:3389) (Weight set to 0)
Nov 26 02:47:05 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.16:3389 ( x 192.168.50.10:3389) (Weight set to 1)
Nov 26 02:47:45 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.15:3389 ( x 192.168.50.10:3389) (Weight set to 1)
Nov 26 02:56:52 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.121:1494 ( x 192.168.50.120:1494) (Weight set to
0)
Nov 26 02:58:05 rpzlvs01 ldirectord[2672]: Restored real server:
192.168.50.121:1494 ( x 192.168.50.120:1494) (Weight set to 1
)
Nov 26 02:56:49 rpzlvs01 heartbeat[2362]: info: Clock jumped backwards.
Compensating.
Nov 26 02:59:57 rpzlvs01 heartbeat[2362]: info: Clock jumped backwards.
Compensating.
Nov 26 03:01:42 rpzlvs01 ldirectord[2672]: Quiescent real server:
192.168.50.122:1494 ( x 192.168.50.120:1494) (Weight set to
0)
I know that after this ldirectord didn't run anymore, because 1) the
real-server didn't get added back anymore, and 2) next night, nothing was
modified (weight set to 0).
Help? :)
Leon
--
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
|
