search

mctaek / mysql-master-ha

Automatically exported from code.google.com/p/mysql-master-ha
0 stars 0 forks source link

Applying diffs failed with return code 22:0 #65

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.The MHA Environment has been configured
2.The manager process has been start
3.when i do the insert sql perating,i stop the master node mysql ,Master 
failover to a slave node done, but recovery on slave partially failed.
some log info :
eeerrrrrrrrrrtttttttttt'),(0,' 
','qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt'),(0,' 
','qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrr
rrrtttttttttt')
--------------

Bye
Sun Sep  1 01:04:10 2013 - 
[error][/usr/local/share/perl/5.14.2/MHA/MasterFailover.pm, ln1182]  Applying 
diffs failed with return co
de 22:0.
Sun Sep  1 01:04:10 2013 - [info] End of log messages from 192.168.137.141.
Sun Sep  1 01:04:10 2013 - [info] -- Recovery on host 
192.168.137.141(192.168.137.141:3306) failed, exit code 1
Sun Sep  1 01:04:10 2013 - 
[error][/usr/local/share/perl/5.14.2/MHA/MasterFailover.pm, ln1561] Master 
failover to 192.168.137.53(192
.168.137.53:3306) done, but recovery on slave partially failed.
Sun Sep  1 01:04:10 2013 - [info] 

----- Failover Report -----

app1: MySQL Master failover 192.168.137.74 to 192.168.137.53

Master 192.168.137.74 is down!

Check MHA Manager logs at ubuntu:/masterha/app1/manager.log for details.

Started automated(non-interactive) failover.
The latest slave 192.168.137.53(192.168.137.53:3306) has all relay logs for 
recovery.
Selected 192.168.137.53 as a new master.
192.168.137.53: OK: Applying all logs succeeded.
192.168.137.141: Generating differential relay logs up to 192.168.137.53 
succeeded.
Generating relay diff files from the latest slave succeeded.
192.168.137.141: ERROR: Applying logs failed.
Master failover to 192.168.137.53(192.168.137.53:3306) done, but recovery on 
slave partially failed.
root@ubuntu:/masterha/app1#    

please help me how to do?? thanks very much!

Original issue reported on code.google.com by majiansa...@gmail.com on 1 Sep 2013 at 8:33

GoogleCodeExporter commented 8 years ago 
Please attach the whole error log, or (if you don't want to share the log to 
the public) send the log to me (Yoshinori.Matsunobu@gmail.com).

Did you manually or intentionally update the failed slave before running MHA 
failover?

Original comment by Yoshinor...@gmail.com on 1 Sep 2013 at 6:45