Hi,

 

I updated from v2rc3.1 to v2 stable yesterday. I'm experiencing some issues
with the manual maintenance failovers.

The "Force node as backup for maintenance" works fine:

 

                ucarp.log:

                Apr 11 15:56:45 zen-lb001 ucarp[5496]: [INFO] Local
advertised ethernet address is [00:22:19:52:68:88]

                Apr 11 15:56:45 zen-lb001 ucarp[5496]: [WARNING] Switching
to state: BACKUP

                Apr 11 15:56:45 zen-lb001 ucarp[5496]: [WARNING] Spawning
[/usr/local/zenloadbalancer/app/zenlatency/zenlatency-stop.pl eth0
xxx.xxx.xx.xxx]

 

                zenloadbalancer.log:

                Wed Apr 11 15:56:45 2012 - * -  - admin - Demoting the node
to backup for maintenance, please wait and not stop the process

                Wed Apr 11 15:56:45 2012 - * -  - admin -
/usr/local/zenloadbalancer/app/ucarp/sbin/ucarp  --interface=eth0
--srcip=xxx.xxx.xx.xxx --vhid=1 --pass=secret --addr= xxx.xxx.xx.xxx -k 100
--upscript=/usr/local/zenloadbalancer/app/zenlatency/zenlatency-start.pl --
downscript=/usr/local/zenloadbalancer/app/zenlatency/zenlatency-stop.pl -B
-f local6

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:3 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:18 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:10 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:4 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:5 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:7 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:12 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:2 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:15 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:6 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:14 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:cluster down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:8 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:9 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:13 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:20 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:11 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:19 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:1 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:16 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running
'/sbin/ifconfig eth0:17 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
route flush table table_eth1.2150'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
rule del from xxx.xxx.xx.xxx table table_eth1.2150'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
link set eth1.2150 down'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
route flush table table_eth1.2151'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
rule del from xxx.xxx.xx.xxx table table_eth1.2151'

                Wed Apr 11 15:56:50 2012 - * -  - admin - running '/sbin/ip
link set eth1.2151 down'

 

But when I choose to "Return node from maintenance", it does exactly the
same instead of becoming MASTER?

 

                ucarp.log:

                Apr 11 16:01:43 zen-lb001 ucarp[5879]: [INFO] Local
advertised ethernet address is [00:22:19:52:68:88]

                Apr 11 16:01:43 zen-lb001 ucarp[5879]: [WARNING] Switching
to state: BACKUP

                Apr 11 16:01:43 zen-lb001 ucarp[5879]: [WARNING] Spawning
[/usr/local/zenloadbalancer/app/zenlatency/zenlatency-stop.pl eth0
xxx.xxx.xx.xxx]

 

                zenloadbalancer.log:

                Wed Apr 11 16:01:43 2012 - * -  - admin - Returning the node
from maintenance, please wait and not stop the process

                Wed Apr 11 16:01:43 2012 - * -  - admin -
/usr/local/zenloadbalancer/app/ucarp/sbin/ucarp  --interface=eth0
--srcip=xxx.xxx.xx.xxx -P --vhid=1 --pass=secret --addr= xxx.xxx.xx.xxx
--upscript=/usr/local/zenloadbalancer/app/zenlatency/zenlatency-start.pl --
downscript=/usr/local/zenloadbalancer/app/zenlatency/zenlatency-stop.pl -B
-f local6

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:3 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:18 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:10 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:4 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:5 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:7 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:12 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:2 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:15 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:6 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:14 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:cluster down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:8 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:9 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:13 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:20 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:11 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:19 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:1 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:16 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running
'/sbin/ifconfig eth0:17 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
route flush table table_eth1.2150'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
rule del from xxx.xxx.xx.xxx table table_eth1.2150'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
link set eth1.2150 down'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
route flush table table_eth1.2151'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
rule del from xxx.xxx.xx.xxx table table_eth1.2151'

                Wed Apr 11 16:01:48 2012 - * -  - admin - running '/sbin/ip
link set eth1.2151 down'

 

The cluster status says "Cluster is active on zen-lb002".

The configured cluster type is "zen-lb001 master and zen-lb002 backup
automatic failback"

The GUI button "Return node from maintenance" has been changed to "Force
node as backup for maintenance" again. 

Only way to make zen-lb001 MASTER again is to click on "Test failover" on
zen-lb002 (current master at the time), or to unplug zen-lb002 so that
zen-lb001 becomes master again.

 

Anybody else experiencing this issue?

 

 

Regards,

 

Greg

 

 

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support

Reply via email to