Wed Apr 22 11:48:59 2015 - [info] Getting new master's binlog name and position..
Wed Apr 22 11:48:59 2015 - [info]? mysql-bin.000017:259187555
Wed Apr 22 11:48:59 2015 - [info]? All other slaves should start replication from here. Statement should be:
? CHANGE MASTER TO MASTER_HOST='vdbsrv3 or 192.168.1.8', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000017',
? MASTER_LOG_POS=259187555, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Wed Apr 22 11:48:59 2015 - [info] Executing master IP activate script:
Wed Apr 22 11:48:59 2015 - [info]? /tmp/master_ip_failover --command=start --ssh_user=root --orig_master_host=vdbsrv1
? --orig_master_ip=192.168.1.6 --orig_master_port=3306 --new_master_host=vdbsrv3 --new_master_ip=192.168.1.8 --new_master_port=3306
? --new_master_user='mha' --new_master_password='xxx'?
Unknown option: new_master_user
Unknown option: new_master_password
IN SCRIPT TEST====/sbin/ifconfig eth0:0 down==/sbin/ifconfig eth0:0 192.168.1.13/24===
----- Failover Report -----
app1: MySQL Master failover vdbsrv1(192.168.1.6:3306) to vdbsrv3(192.168.1.8:3306) succeeded
Master vdbsrv1(192.168.1.6:3306) is down!
Check MHA Manager logs at vdbsrv4 for details.
Started manual(interactive) failover.
Invalidated master IP address on vdbsrv1(192.168.1.6:3306)
The latest slave vdbsrv3(192.168.1.8:3306) has all relay logs for recovery.
Selected vdbsrv3(192.168.1.8:3306) as a new master.
vdbsrv3(192.168.1.8:3306): OK: Applying all logs succeeded.
vdbsrv3(192.168.1.8:3306): OK: Activated master IP address.
vdbsrv2(192.168.1.7:3306): Generating differential relay logs up to vdbsrv3(192.168.1.8:3306)succeeded.
Generating relay diff files from the latest slave succeeded.
vdbsrv2(192.168.1.7:3306): OK: Applying all logs succeeded. Slave started, replicating from vdbsrv3(192.168.1.8:3306)
vdbsrv3(192.168.1.8:3306): Resetting slave info succeeded.
Master failover to vdbsrv3(192.168.1.8:3306) completed successfully.