newest ldirectord won't add https real servers
tlyons at ivenue.com
Tue Jan 18 19:07:26 GMT 2005
I was working with it last week. There is good news and there
is bad news. ldirectord 22.214.171.124 comes with heartbeat 1.2.2 and
ldirectord 126.96.36.199 comes with heartbeat 1.2.3.
188.8.131.52 fixes the problem of multiple VIPs with identical RIPs:ports.
Https load balancing doesn't work any more (all stay quiescent).
Mysql load balancing barely works (sometimes comes right up, other times
takes a while before real servers show up in ipvsadm).
I received identical results by putting both versions of heartbeat
(1.2.2 and 1.2.3) on both loadbalancers and trying various tests. In
all cases, 1.2.2 resulted in proper operation except for the multiple
RIPs to multiple VIPs problem, and 1.2.3 resulted in the good/bad
description above. I now have both systems back with heartbeat 1.2.2 to
keep things stable.
Looking through CVS, I see some changes to the check_https code since
184.108.40.206. I don't define a url to check for my https, maybe that has
something to do with 220.127.116.11 not working for me. But 18.104.22.168 works
with the identical configuration. At any rate, I'll keep digging.
Is there any further suggestions for me to try other than wait for a new
release? Is anybody else using ldirectord 22.214.171.124 to balance htts? If
so, could we compare ldirectord.cf settings? With obfuscated IPs, mine
virtual = 126.96.36.199:https
real = 10.1.1.2->10.1.1.3:https gate 100
persistent = 300
checktype = negotiate
scheduler = wrr
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. --Benjamin Franklin
Linux kernel 188.8.131.52-12mdkenterprise 2 users, load average: 1.29, 1.17, 1.10
More information about the lvs-users