Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL Enterprise use MHA report errors #93

Open
GoogleCodeExporter opened this issue Jul 30, 2015 · 1 comment
Open

MySQL Enterprise use MHA report errors #93

GoogleCodeExporter opened this issue Jul 30, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Contributor

What steps will reproduce the problem?
1.MySQL Enterprise use MHA report errors (None of slaves can be master.)


What is the expected output? What do you see instead?
Wed Nov 26 14:02:58 2014 - [warning] Global configuration file 
/etc/masterha_default.cnf not found. Skipping.
Wed Nov 26 14:02:58 2014 - [info] Reading application default configuration 
from /etc/app1.cnf..
Wed Nov 26 14:02:58 2014 - [info] Reading server configuration from 
/etc/app1.cnf..
Wed Nov 26 14:02:58 2014 - [info] MHA::MasterMonitor version 0.56.
Wed Nov 26 14:02:58 2014 - [info] GTID failover mode = 0
Wed Nov 26 14:02:58 2014 - [info] Dead Servers:
Wed Nov 26 14:02:58 2014 - [info]   192.168.100.33(192.168.100.33:3306)
Wed Nov 26 14:02:58 2014 - [info] Alive Servers:
Wed Nov 26 14:02:58 2014 - [info]   192.168.100.32(192.168.100.32:3306)
Wed Nov 26 14:02:58 2014 - [info]   192.168.100.34(192.168.100.34:3306)
Wed Nov 26 14:02:58 2014 - [info] Alive Slaves:
Wed Nov 26 14:02:58 2014 - [info]   192.168.100.34(192.168.100.34:3306)  
Version=5.6.19-enterprise-commercial-advanced-log (oldest major version between 
slaves) log-bin:enabled
Wed Nov 26 14:02:58 2014 - [info]     Replicating from 
192.168.100.32(192.168.100.32:3306)
Wed Nov 26 14:02:58 2014 - [info]     Not candidate for the new Master 
(no_master is set)
Wed Nov 26 14:02:58 2014 - [info] Current Alive Master: 
192.168.100.32(192.168.100.32:3306)
Wed Nov 26 14:02:58 2014 - [info] Checking slave configurations..
Wed Nov 26 14:02:58 2014 - [info] Checking replication filtering settings..
Wed Nov 26 14:02:58 2014 - [info]  binlog_do_db= , binlog_ignore_db= 
Wed Nov 26 14:02:58 2014 - [info]  Replication filtering check ok.
Wed Nov 26 14:02:58 2014 - 
[error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln361] None of 
slaves can be master. Check failover configuration file or log-bin settings in 
my.cnf
Wed Nov 26 14:02:58 2014 - 
[error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error 
happened on checking configurations.  at /usr/bin/masterha_check_repl line 48
Wed Nov 26 14:02:58 2014 - 
[error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error 
happened on monitoring servers.
Wed Nov 26 14:02:58 2014 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

What version of the product are you using? On what operating system?
mysql-advanced-5.6.19-linux-glibc2.5-x86_64.rpm.zip
centos6.3

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 11 Aug 2014 at 6:07

@GoogleCodeExporter
Copy link
Contributor Author

The error log says a slave 192.168.100.34 is replicating from 192.168.100.32, 
not from a dead server (192.168.100.33). To make MHA work, all slaves have to 
replicate from a dead server.

- Yoshinori

Original comment by [email protected] on 12 Aug 2014 at 2:47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant