Mon Jan 18 18:05:49 2016 - [warning] Goterror on MySQL select ping: 2006 (MySQL server has gone away)
Mon Jan 18 18:05:49 2016 - [info] ExecutingSSH check script: save_binary_logs --command=test --start_pos=4--binlog_dir=/data/dbdata/mysqllog/binlog--output_file=/tmp/save_binary_logs_test --manager_version=0.56--binlog_prefix=binlog
Creating /tmp if not exists.. ok.
Checking output directory is accessible or not..
ok.
Binlog found at /data/dbdata/mysqllog/binlog, up to binlog.000003
Mon Jan 18 18:05:50 2016 - [info]HealthCheck: SSH to 192.168.6.85 is reachable.
Mon Jan 18 18:05:50 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
Mon Jan 18 18:05:50 2016 - [warning]Connection failed 2 time(s)..
Mon Jan 18 18:05:51 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
Mon Jan 18 18:05:51 2016 - [warning]Connection failed 3 time(s)..
Mon Jan 18 18:05:52 2016 - [warning] Goterror on MySQL connect: 2013 (Lost connection to MySQL server at 'readinginitial communication packet', system error: 111)
Mon Jan 18 18:05:52 2016 - [warning]Connection failed 4 time(s)..
Mon Jan 18 18:05:52 2016 - [warning] Masteris not reachable from health checker!
Mon Jan 18 18:05:52 2016 - [warning] Master192.168.6.85(192.168.6.85:3306) is not reachable!
Mon Jan 18 18:05:52 2016 - [warning] SSH isreachable.
Mon Jan 18 18:05:52 2016 - [info]Connecting to a master server failed. Reading configuration file/etc/masterha_default.cnf and /etc/mha/masterha_default.cnf again, and tryingto connect to all servers to check server status..
Mon Jan 18 18:05:52 2016 - [warning] Globalconfiguration file /etc/masterha_default.cnf not found. Skipping.
Mon Jan 18 18:05:52 2016 - [info] Readingapplication default configuration from /etc/mha/masterha_default.cnf..
Mon Jan 18 18:05:52 2016 - [info] Readingserver configuration from /etc/mha/masterha_default.cnf..
Mon Jan 18 18:05:53 2016 - [info] Executingcommand on the dead master 192.168.6.85(192.168.6.85:3306): save_binary_logs--command=save --start_file=binlog.000003 --start_pos=107 --binlog_dir=/data/dbdata/mysqllog/binlog--output_file=/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog--handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56
Creating /tmp if not exists.. ok.
Concat binary/relay logs from binlog.000003pos 107 to binlog.000003 EOF into/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog ..
Dumping binlog format description event, from position 0 to 107.. ok.
Dumping effective binlog data from /data/dbdata/mysqllog/binlog/binlog.000003position 107 to tail(126).. ok.
Concat succeeded.
Mon Jan 18 18:05:54 2016 - [info] scp fromroot@192.168.6.85:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogto local:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
Mon Jan 18 18:05:54 2016 - [info]HealthCheck: SSH to 192.168.6.91 is reachable.
Mon Jan 18 18:05:55 2016 - [info]HealthCheck: SSH to 192.168.6.149 is reachable.
Mon Jan 18 18:05:55 2016 - [info]
Mon Jan 18 18:05:55 2016 - [info] * Phase3.3: Determining New Master Phase..
Mon Jan 18 18:05:55 2016 - [info]
Mon Jan 18 18:05:55 2016 - [info] Findingthe latest slave that has all relay logs for recovering other slaves..
Mon Jan 18 18:05:55 2016 - [info] Allslaves received relay logs to the same position. No need to resync each other.
Mon Jan 18 18:05:55 2016 - [info] Searchingnew master from slaves..
Mon Jan 18 18:05:55 2016 - [info] Candidate masters from the configurationfile:
Mon Jan 18 18:05:55 2016 - [info] 192.168.6.91(192.168.6.91:3306) Version=5.5.33-log (oldest major versionbetween slaves) log-bin:enabled
Mon Jan 18 18:05:55 2016 - [info] Replicating from192.168.6.85(192.168.6.85:3306)
Mon Jan 18 18:05:55 2016 - [info] Primary candidate for the new Master(candidate_master is set)
Mon Jan 18 18:05:55 2016 - [info] Non-candidate masters:
Mon Jan 18 18:05:55 2016 - [info] Searching from candidate_master slaves whichhave received the latest relay log events..
Mon Jan 18 18:05:55 2016 - [info] New masteris 192.168.6.91(192.168.6.91:3306)
Mon Jan 18 18:05:55 2016 - [info] Startingmaster failover..
Mon Jan 18 18:05:55 2016 - [info]
From:
192.168.6.85(192.168.6.85:3306) (currentmaster)
+--192.168.6.91(192.168.6.91:3306)
+--192.168.6.149(192.168.6.149:3306)
To:
192.168.6.91(192.168.6.91:3306) (newmaster)
+--192.168.6.149(192.168.6.149:3306)
Mon Jan 18 18:05:55 2016 - [info]
Mon Jan 18 18:05:55 2016 - [info] * Phase3.3: New Master Diff Log Generation Phase..
Mon Jan 18 18:05:55 2016 - [info]
Mon Jan 18 18:05:55 2016 - [info] This server has all relay logs. No need togenerate diff files from the latest slave.
Mon Jan 18 18:05:55 2016 - [info] Sendingbinlog..
Mon Jan 18 18:05:55 2016 - [info] scp fromlocal:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogtoroot@192.168.6.91:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
Mon Jan 18 18:05:55 2016 - [info] *NOTICE:If any error happens from this phase, manual recovery is needed.
Mon Jan 18 18:05:55 2016 - [info] Startingrecovery on 192.168.6.91(192.168.6.91:3306)..
Mon Jan 18 18:05:55 2016 - [info] Generating diffs succeeded.
Mon Jan 18 18:05:55 2016 - [info] Waitinguntil all relay logs are applied.
Mon Jan 18 18:05:55 2016 - [info] done.
Mon Jan 18 18:05:55 2016 - [info] Gettingslave status..
Mon Jan 18 18:05:55 2016 - [info] Thisslave(192.168.6.91)'s Exec_Master_Log_Pos equals toRead_Master_Log_Pos(binlog.000003:107). No need to recover fromExec_Master_Log_Pos.
Mon Jan 18 18:05:55 2016 - [info]Connecting to the target slave host 192.168.6.91, running recover script..
Applying differential binary/relay logfiles /tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog on192.168.6.91:3306. This may take long time...
Applying log files succeeded.
Mon Jan 18 18:05:56 2016 - [info] All relay logs were successfully applied.
Mon Jan 18 18:05:56 2016 - [info] Gettingnew master's binlog name and position..
Mon Jan 18 18:05:56 2016 - [info] binlog.000003:107
Mon Jan 18 18:05:56 2016 - [info] All other slaves should start replicationfrom here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.6.91',MASTER_PORT=3306, MASTER_LOG_FILE='binlog.000003', MASTER_LOG_POS=107,MASTER_USER='repl', MASTER_PASSWORD='xxx';
Mon Jan 18 18:05:56 2016 - [warning]master_ip_failover_script is not set. Skipping taking over new master IPaddress.
Mon Jan 18 18:05:56 2016 - [info] scp fromlocal:/var/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogto root@192.168.6.149:/tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlogsucceeded.
Mon Jan 18 18:05:56 2016 - [info] Startingrecovery on 192.168.6.149(192.168.6.149:3306)..
Mon Jan 18 18:05:56 2016 - [info] Generating diffs succeeded.
Mon Jan 18 18:05:56 2016 - [info] Waitinguntil all relay logs are applied.
Mon Jan 18 18:05:56 2016 - [info] done.
Mon Jan 18 18:05:56 2016 - [info] Gettingslave status..
Mon Jan 18 18:05:56 2016 - [info] Thisslave(192.168.6.149)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(binlog.000003:107).No need to recover from Exec_Master_Log_Pos.
Mon Jan 18 18:05:56 2016 - [info]Connecting to the target slave host 192.168.6.149, running recover script..
Applying differential binary/relay logfiles /tmp/saved_master_binlog_from_192.168.6.85_3306_20160118180552.binlog on192.168.6.149:3306. This may take long time...
Applying log files succeeded.
Mon Jan 18 18:05:57 2016 - [info] All relay logs were successfully applied.
Mon Jan 18 18:05:57 2016 - [info] Resetting slave 192.168.6.149(192.168.6.149:3306)and starting replication from the new master 192.168.6.91(192.168.6.91:3306)..
Mon Jan 18 18:05:57 2016 - [info] Executed CHANGE MASTER.
Mon Jan 18 18:05:57 2016 - [info] Slave started.
Mon Jan 18 18:05:57 2016 - [info] End oflog messages from 192.168.6.149.
Mon Jan 18 18:05:57 2016 - [info] -- Slaverecovery on host 192.168.6.149(192.168.6.149:3306) succeeded.
Mon Jan 18 18:05:57 2016 - [info] All newslave servers recovered successfully.
Mon Jan 18 18:05:57 2016 - [info]
Mon Jan 18 18:05:57 2016 - [info] * Phase5: New master cleanup phase..
Mon Jan 18 18:05:57 2016 - [info]
Mon Jan 18 18:05:57 2016 - [info] Resettingslave info on the new master..
Mon Jan 18 18:05:57 2016 - [info] 192.168.6.91: Resetting slave info succeeded.
Mon Jan 18 18:05:57 2016 - [info] Masterfailover to 192.168.6.91(192.168.6.91:3306) completed successfully.
Mon Jan 18 18:05:57 2016 - [info] Deletedserver1 entry from /etc/mha/masterha_default.cnf .
Mon Jan 18 18:05:57 2016 - [info]
----- Failover Report -----
masterha_default: MySQL Master failover192.168.6.85(192.168.6.85:3306) to 192.168.6.91(192.168.6.91:3306) succeeded
Master 192.168.6.85(192.168.6.85:3306) isdown!
Check MHA Manager logs at slave2 fordetails.
Started automated(non-interactive)failover.
The latest slave192.168.6.91(192.168.6.91:3306) has all relay logs for recovery.
Selected 192.168.6.91(192.168.6.91:3306) asa new master.
192.168.6.91(192.168.6.91:3306): OK:Applying all logs succeeded.
192.168.6.149(192.168.6.149:3306): Thishost has the latest relay log events.
Generating relay diff files from the latestslave succeeded.
192.168.6.149(192.168.6.149:3306): OK:Applying all logs succeeded. Slave started, replicating from192.168.6.91(192.168.6.91:3306)
192.168.6.91(192.168.6.91:3306): Resettingslave info succeeded.