Not the answer you need?
Register and ask your own question!

Problem with Percona 5.7 and MHA 0.57

lcalerolcalero EntrantCurrent User Role Participant
Hello, I've been having problems with Percona 5.7 (Server version: 5.7.18-15-log Percona Server (GPL), Release '15', Revision 'bff2cd9') and MHA 0.57. I setup MHA and everything looks right, but when I start the MHA Manager, I get connection errors:

[email protected]:~# masterha_check_repl --conf=/etc/mha/app1.cnf
[...]
MySQL Replication Health is OK.

[email protected]:~# masterha_manager --conf=/etc/mha/app1.cnf
[...]
Tue Jun 27 16:15:17 2017 - [info] Starting ping health check on db-perc-01.antevenio.local(172.16.11.225:3306)..
Tue Jun 27 16:15:17 2017 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
Tue Jun 27 16:15:22 2017 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Tue Jun 27 16:15:22 2017 - [info] Executing SSH check script: exit 0
Tue Jun 27 16:15:22 2017 - [info] HealthCheck: SSH to db-perc-01.antevenio.local is reachable.
Tue Jun 27 16:15:27 2017 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
Tue Jun 27 16:15:32 2017 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Tue Jun 27 16:15:32 2017 - [info] Executing SSH check script: exit 0
Tue Jun 27 16:15:32 2017 - [info] HealthCheck: SSH to db-perc-01.antevenio.local is reachable.
Tue Jun 27 16:15:37 2017 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
Tue Jun 27 16:15:42 2017 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Tue Jun 27 16:15:42 2017 - [info] Executing SSH check script: exit 0

So it loses the connection to the other server, but the ping is ok. On the other server there are some errors:
2017-06-27T14:16:22.598621Z 16 [Note] Aborted connection 16 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
2017-06-27T14:16:32.599012Z 17 [Note] Aborted connection 17 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
2017-06-27T14:16:42.599332Z 18 [Note] Aborted connection 18 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
2017-06-27T14:16:52.599987Z 19 [Note] Aborted connection 19 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
2017-06-27T14:17:02.601149Z 20 [Note] Aborted connection 20 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
2017-06-27T14:17:12.601341Z 21 [Note] Aborted connection 21 to db: 'unconnected' user: 'mhauser' host: '172.16.11.226' (Got an error reading communication packets)
[...]

But the strange thing is that if I just change Percona server, for MySQL Server 5.7 and run the exact same configuration, MHA works perfectly. Any ideas?

Regards
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.