Hello, I've just configured a new cluster with ZLB v3.03. During the configuration, i've chosen Cluster ID = 2 because i've already another ZLB v2 running on this network and using ID 1.
Looking at the process, it looks fine (--vhid=2): /usr/local/zenloadbalancer/app/ucarp/sbin/ucarp -r 2 --interface=eth0 --srcip=192.168.135.232 --vhid=2 --pass=secret --addr=192.168.135.230 --upscript=/usr/local/zenloadbalancer/app/zenlat The configuration file on both node is fine as well: root@VMWZLB004:~# cat /usr/local/zenloadbalancer/config/cluster.conf MEMBERS:VMWZLB003:192.168.135.231:VMWZLB004:192.168.135.232 IPCLUSTER:192.168.135.230:eth0:clu TYPECLUSTER:equal:UP CABLE:-1 IDCLUSTER:2 DEADRATIO:2 However, when I reboot a node (nevermind which one) the carp process start with --vhid=1, so it doesnt seems to take care of what's in the config file (it also does not consider the deadratio as I do not see the "-r 2" parameter in the command line) /usr/local/zenloadbalancer/app/ucarp/sbin/ucarp --interface=eth0 --srcip=192.168.135.232 --vhid=1 --pass=secret --addr=192.168.135.230 --upscript=/usr/local/zenloadbalancer/app/zenlatency/z Restarting zenloadbalancer (/etc/init.d/zenloadbalancer restart) does not help. The only way to restore the situation is to go on the master node, click "Save" under Dead Ratio and then click "Configure cluster type" and let it finish the cluster config process again. Can you please help with a fix to make sure the cluster.conf is read correctly uppon startup ? Thanks tibz ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
