mha0.56版本安装使用排错

1.master_check_ssh --conf=/etc/app1.conf

这个检查就报错的我觉得百分之九十都是ssh之间连接问题。务必要保证各节点之间都可以免秘钥访问！

2.master_check_repl --conf=/etc/app1.conf

(1)报错代码：

类似就是说什么copyuser复制用户在节点没有权限的代码，解决方法是每个节点创建这个用户即可。要是主从复制已经开启，记得节点先stop slave；再分别创建用户。

MHA版本，应该需要在所有的数据库中都开启二进制日志，中继日志，授权也应该都相同，配置文件也基本相同。我想在这个前提下在安装执行MHA应该不会遇上太多问题了。只是目前还不能确定这种做法是不是正解。

(2)报错代码：

Tue Apr 30 09:26:44 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

Tue Apr 30 09:26:44 2019 - [info] Reading application default configuration from /etc/mha/app1.cnf..

Tue Apr 30 09:26:44 2019 - [info] Reading server configuration from /etc/mha/app1.cnf..

Tue Apr 30 09:26:44 2019 - [info] MHA::MasterMonitor version 0.56.

Tue Apr 30 09:26:45 2019 - [info] GTID failover mode = 0

Tue Apr 30 09:26:45 2019 - [info] Dead Servers:

Tue Apr 30 09:26:45 2019 - [info] Alive Servers:

Tue Apr 30 09:26:45 2019 - [info]   103.75.1.22(103.75.1.22:3306)

Tue Apr 30 09:26:45 2019 - [info]   103.75.1.23(103.75.1.23:3306)

Tue Apr 30 09:26:45 2019 - [info]   103.75.1.24(103.75.1.24:3306)

Tue Apr 30 09:26:45 2019 - [info] Alive Slaves:

Tue Apr 30 09:26:45 2019 - [info]   103.75.1.23(103.75.1.23:3306)  Version=5.7.25-log (oldest major version between slaves) log-bin:enabled

Tue Apr 30 09:26:45 2019 - [info]     Replicating from 103.75.1.22(103.75.1.22:3306)

Tue Apr 30 09:26:45 2019 - [info]     Primary candidate for the new Master (candidate_master is set)

Tue Apr 30 09:26:45 2019 - [info]   103.75.1.24(103.75.1.24:3306)  Version=5.7.25-log (oldest major version between slaves) log-bin:enabled

Tue Apr 30 09:26:45 2019 - [info]     Replicating from 103.75.1.22(103.75.1.22:3306)

Tue Apr 30 09:26:45 2019 - [info] Current Alive Master: 103.75.1.22(103.75.1.22:3306)

Tue Apr 30 09:26:45 2019 - [info] Checking slave configurations..

Tue Apr 30 09:26:45 2019 - [info]  read_only=1 is not set on slave 103.75.1.24(103.75.1.24:3306).

Tue Apr 30 09:26:45 2019 - [info] Checking replication filtering settings..

Tue Apr 30 09:26:45 2019 - [info]  binlog_do_db= , binlog_ignore_db=

Tue Apr 30 09:26:45 2019 - [info]  Replication filtering check ok.

Tue Apr 30 09:26:45 2019 - [info] GTID (with auto-pos) is not supported

Tue Apr 30 09:26:45 2019 - [info] Starting SSH connection tests..

Tue Apr 30 09:26:53 2019 - [info] All SSH connection tests passed successfully.

Tue Apr 30 09:26:53 2019 - [info] Checking MHA Node version..

Tue Apr 30 09:26:57 2019 - [info]  Version check ok.

Tue Apr 30 09:26:57 2019 - [info] Checking SSH publickey authentication settings on the current master..

Tue Apr 30 09:26:58 2019 - [info] HealthCheck: SSH to 103.75.1.22 is reachable.

Tue Apr 30 09:26:59 2019 - [info] Master MHA Node version is 0.56.

Tue Apr 30 09:26:59 2019 - [info] Checking recovery script configurations on 103.75.1.22(103.75.1.22:3306)..

Tue Apr 30 09:26:59 2019 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data --output_file=/data/mastermha/app1//save_binary_logs_test --manager_version=0.56 --start_file=master-bin.000008

Tue Apr 30 09:26:59 2019 - [info]   Connecting to root@103.75.1.22(103.75.1.22:22)..

Failed to save binary log: Binlog not found from /data! If you got this error at MHA Manager, please set "master_binlog_dir=/path/to/binlog_directory_of_the_master" correctly in the MHA Manager's configuration file and try again.

 at /usr/bin/save_binary_logs line 123

    eval {...} called at /usr/bin/save_binary_logs line 70

    main::main() called at /usr/bin/save_binary_logs line 66

Tue Apr 30 09:27:00 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln158] Binlog setting check failed!

Tue Apr 30 09:27:00 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln405] Master configuration failed.

Tue Apr 30 09:27:00 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations.  at /usr/bin/masterha_check_repl line 48

Tue Apr 30 09:27:00 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

Tue Apr 30 09:27:00 2019 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

解决方法：

如果手动定义了二进制日志文件的路径，就必须在mha的配置文件中制定master_binlog_dir=‘二进制日志文件所在目录' 我是直接在app1.conf配置文件#注释掉这个master_binlog_dir=/data

(3)报错代码：

Tue Apr  ::  - [info] Checking replication health on 103.75.1.23..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [info] Checking replication health on 103.75.1.24..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [warning] master_ip_failover_script is not defined.

Tue Apr  ::  - [warning] shutdown_script is not defined.

Tue Apr  ::  - [info] Got exit code  (Not master dead).

MySQL Replication Health is OK.

这个报错代码出现在检查的最后面，意思是未定义这两个文件。未定义这两个文件我直接启动manage是卡住的。解决方法，在app1.conf配置文件添加master_ip_failover_scipt='脚本文件目录'

附脚本地址:http://control.blog.sina.com.cn/admin/article/article_edit.php?blog_id=b4fca5310102yan0

(3)报错代码：

103.75.1.22(103.75.1.22:) (current master)

 +--103.75.1.23(103.75.1.23:)

 +--103.75.1.24(103.75.1.24:)

Tue Apr  ::  - [info] Checking replication health on 103.75.1.23..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [info] Checking replication health on 103.75.1.24..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [info] Checking master_ip_failover_script status:

Tue Apr  ::  - [info]   /data/mastermha/app1/master_ip_failover --command=status --ssh_user=root --orig_master_host=103.75.1.22 --orig_master_ip=103.75.1.22 --orig_master_port=

Tue Apr  ::  - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. Can't exec "/data/mastermha/app1/master_ip_failover": Permission denied at /usr/share/perl5/vendor_perl/MHA/ManagerUtil.pm line 68.

Tue Apr  ::  - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

Tue Apr  ::  - [info] Got exit code  (Not master dead).

MySQL Replication Health is NOT OK!

Tue Apr  ::  - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln226]  Failed to get master_ip_failover_script status with return code :.

Tue Apr  ::  - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations.  at /usr/bin/masterha_check_repl line

Tue Apr  ::  - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

Tue Apr  ::  - [info] Got exit code  (Not master dead).

MySQL Replication Health is NOT OK!

这个报错查了很多资料。我一直以为是我的master_ip_fialover脚本有问题。结果不是，是这个脚本没有执行权限，参考

解决办法：赋权！ chmod +x
/data/mastermha/app1/master_ip_failover

再次执行发现解决！！

附完工图！

[root@localhost ~]# chmod +x /data/mastermha/app1/master_ip_failover

[root@localhost ~]# masterha_check_repl --conf=/etc/mha/app1.cnf

Tue Apr  ::  - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

Tue Apr  ::  - [info] Reading application default configuration from /etc/mha/app1.cnf..

Tue Apr  ::  - [info] Reading server configuration from /etc/mha/app1.cnf..

Tue Apr  ::  - [info] MHA::MasterMonitor version 0.56.

Tue Apr  ::  - [info] GTID failover mode =

Tue Apr  ::  - [info] Dead Servers:

Tue Apr  ::  - [info] Alive Servers:

Tue Apr  ::  - [info]   103.75.1.22(103.75.1.22:)

Tue Apr  ::  - [info]   103.75.1.23(103.75.1.23:)

Tue Apr  ::  - [info]   103.75.1.24(103.75.1.24:)

Tue Apr  ::  - [info] Alive Slaves:

Tue Apr  ::  - [info]   103.75.1.23(103.75.1.23:)  Version=5.7.-log (oldest major version between slaves) log-bin:enabled

Tue Apr  ::  - [info]     Replicating from 103.75.1.22(103.75.1.22:)

Tue Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)

Tue Apr  ::  - [info]   103.75.1.24(103.75.1.24:)  Version=5.7.-log (oldest major version between slaves) log-bin:enabled

Tue Apr  ::  - [info]     Replicating from 103.75.1.22(103.75.1.22:)

Tue Apr  ::  - [info] Current Alive Master: 103.75.1.22(103.75.1.22:)

Tue Apr  ::  - [info] Checking slave configurations..

Tue Apr  ::  - [info]  read_only= is not set on slave 103.75.1.24(103.75.1.24:).

Tue Apr  ::  - [info] Checking replication filtering settings..

Tue Apr  ::  - [info]  binlog_do_db= , binlog_ignore_db=

Tue Apr  ::  - [info]  Replication filtering check ok.

Tue Apr  ::  - [info] GTID (with auto-pos) is not supported

Tue Apr  ::  - [info] Starting SSH connection tests..

Tue Apr  ::  - [info] All SSH connection tests passed successfully.

Tue Apr  ::  - [info] Checking MHA Node version..

Tue Apr  ::  - [info]  Version check ok.

Tue Apr  ::  - [info] Checking SSH publickey authentication settings on the current master..

Tue Apr  ::  - [info] HealthCheck: SSH to 103.75.1.22 is reachable.

Tue Apr  ::  - [info] Master MHA Node version is 0.56.

Tue Apr  ::  - [info] Checking recovery script configurations on 103.75.1.22(103.75.1.22:)..

Tue Apr  ::  - [info]   Executing command: save_binary_logs --command=test --start_pos= --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/data/mastermha/app1//save_binary_logs_test --manager_version=0.56 --start_file=master-bin.000008

Tue Apr  ::  - [info]   Connecting to root@103.75.1.22(103.75.1.22:)..

  Creating /data/mastermha/app1 if not exists..    ok.

  Checking output directory is accessible or not..

   ok.

  Binlog found at /var/lib/mysql, up to master-bin.

Tue Apr  ::  - [info] Binlog setting check done.

Tue Apr  ::  - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..

Tue Apr  ::  - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mhauser' --slave_host=103.75.1.23 --slave_ip=103.75.1.23 --slave_port= --workdir=/data/mastermha/app1/ --target_version=5.7.-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx

Tue Apr  ::  - [info]   Connecting to root@103.75.1.23(103.75.1.23:)..

  Checking slave recovery environment settings..

    Opening /var/lib/mysql/relay-log.info ... ok.

    Relay log found at /var/lib/mysql, up to relay-log.

    Temporary relay log file is /var/lib/mysql/relay-log.

    Testing mysql connection and privileges..mysql: [Warning] Using a password on the command line interface can be insecure.

 done.

    Testing mysqlbinlog output.. done.

    Cleaning up test file(s).. done.

Tue Apr  ::  - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mhauser' --slave_host=103.75.1.24 --slave_ip=103.75.1.24 --slave_port= --workdir=/data/mastermha/app1/ --target_version=5.7.-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx

Tue Apr  ::  - [info]   Connecting to root@103.75.1.24(103.75.1.24:)..

  Checking slave recovery environment settings..

    Opening /var/lib/mysql/relay-log.info ... ok.

    Relay log found at /var/lib/mysql, up to relay-log.

    Temporary relay log file is /var/lib/mysql/relay-log.

    Testing mysql connection and privileges..mysql: [Warning] Using a password on the command line interface can be insecure.

 done.

    Testing mysqlbinlog output.. done.

    Cleaning up test file(s).. done.

Tue Apr  ::  - [info] Slaves settings check done.

Tue Apr  ::  - [info]

103.75.1.22(103.75.1.22:) (current master)

 +--103.75.1.23(103.75.1.23:)

 +--103.75.1.24(103.75.1.24:)

Tue Apr  ::  - [info] Checking replication health on 103.75.1.23..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [info] Checking replication health on 103.75.1.24..

Tue Apr  ::  - [info]  ok.

Tue Apr  ::  - [info] Checking master_ip_failover_script status:

Tue Apr  ::  - [info]   /data/mastermha/app1/master_ip_failover --command=status --ssh_user=root --orig_master_host=103.75.1.22 --orig_master_ip=103.75.1.22 --orig_master_port=

IN SCRIPT TEST====/sbin/ifconfig bond1: down==/sbin/ifconfig bond1: 103.75.1.30/===

Checking the Status of the script.. OK

SIOCSIFADDR: No such device

SIOCSIFNETMASK: No such device

SIOCGIFADDR: No such device

SIOCSIFBROADCAST: No such device

bond1:: unknown interface: No such device

Tue Apr  ::  - [info]  OK.

Tue Apr  ::  - [warning] shutdown_script is not defined.

Tue Apr  ::  - [info] Got exit code  (Not master dead).

MySQL Replication Health is OK.

3.master_manage
--conf=/etc/app1.conf

这里我卡住。后来查找资料发现启动方式不一样

[root@localhost ~]# nohup
masterha_manager --conf=/etc/mha/app1.cnf >
/data/mastermha/app1/manager.log &1 &
[1] 2190
上面的就是启动命令，需要启动文件和日志

[root@localhost ~]# masterha_check_status
--conf=/etc/mha/app1.cnf
app1 monitoring program is now on initialization
phase(10:INITIALIZING_MONITOR). Wait for a while and try checking
again.

查看状态就会提示在初始化，稍后一段时间，

再次执行就会发现启动成功

app1 monitoring program is now on initialization
phase(10:INITIALIZING_MONITOR). Wait for a while and try checking
again.
[root@localhost ~]# masterha_check_status
--conf=/etc/mha/app1.cnf
app1 (pid:2190) is running(0:PING_OK), master:103.75.1.22

mha0.56版本安装使用排错的更多相关文章

mysql 5.7以上版本安装配置方法图文教程（mysql 5.7.12\mysql 5.7.13\mysql 5.7.14）(转)
http://www.jb51.net/article/90302.htm ******************************* 这篇文章主要为大家分享了MySQL 5.7以上缩版本安装配置 ...
Atitti.dw cc 2015 绿色版本安装总结
Atitti.dw cc 2015 绿色版本安装总结 1.1. 安装程序无法初始化.请下载adobe Support Advisor检测该问题.1 1.1.1. Adobe Application M ...
centos7最小版本安装nginx+tomcat+java+mysql运行环境
最近项目从windows搬到linux,由于项目组成员有限并且有其它紧急的任务需要处理,因而这个任务就落到我的头上了.下面记录下centos最小版本安装nginx+tomcat+mysql+java的 ...
Robot Framework-Windows版本安装
Robot Framework-Mac版本安装 Robot Framework-Windows版本安装 Robot Framework-工具简介及入门使用 Robot Framework-Databa ...
Robot Framework-Mac版本安装
Robot Framework-Mac版本安装 Robot Framework-Windows版本安装 Robot Framework-工具简介及入门使用 Robot Framework-Databa ...
centOS 6.x 版本安装 node.js 4.x 以上版本的方法
由于 node 4.x 以上版本,通过编译源代码来安装,对 GCC 的版本有要求,而 centos 的 GCC 版本不够,更新 GCC 也很麻烦,所以只能通过别的方式解决. 这里主要介绍直接下载编译后 ...
如何为ubuntu server 版本安装图形界面
强烈建议使用命令行的交互方式,就算你在server上装了图形界面,但是在Linux上,大部分重要的操作还是要通过命令行的方式进行操作. 如何为ubuntu server 版本安装图形界面 Ubunt ...
（新）elasticsearch6.0版本安装head插件
ES6.0版本安装head插件 1.1 前言不知道是我电脑问题还是最近的开源软件都比较**,mysql和elasticsearch新版本变动都比较大. elasticsearch6.0貌似已经不支持 ...
Node.js 多版本安装
Node.js 多版本安装 Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine(Node.js 是一个基于 ...

随机推荐

Git实战（三）环境搭建
上次的博文中.我们介绍了一下关于Git作为版本号控制工具的基本原理,接下来我们来搭建一个主要的Git环境(因为我使用的是Windows系统.所以重点側重在这方面). Git安装 Git的安装很easy ...
Android实现一个自己定义相机的界面
我们先实现拍照button的圆形效果哈.Android开发中,当然能够找美工人员设计图片,然后直接拿进来.只是我们能够自己写代码实现这个效果哈.最经常使用的的是用layout-list实现图片的叠加, ...
纯CSS实现移动端常见布局——高度和宽度挂钩的秘密
纯CSS实现移动端常见布局--高度和宽度挂钩的秘密不踩坑不回头.之前我在一个项目中大量使用css3的calc计算属性.写代码的时候真心不要太爽啊-可是在项目上线之后,才让我崩溃了,原因非常easy, ...
Cisco VPP(1) 简单介绍
一.简单介绍 VPP全称Vector Packet Processing.是Cisco2002年开发的商用代码. 2016年2月11号,Linux基金会创建FD.io项目.Cisco将VPP代码的开源 ...
ZOJ 3888 Twelves Monkeys (预处理+优先队列)
题目链接:ZOJ 3888 Twelves Monkeys 题意:题目描写叙述起来比較绕,直接讲案例 9 3 3 9 1 6 1 4 1 6 7 2 输入n,m,q.n限制了你询问的年份,m台时光机, ...
java-javabean Introspector的应用
Introspector 类为通过工具学习有关受目标 Java Bean 支持的属性.事件和方法的知识提供了一个标准方法. 对于这三种信息,Introspector 将分别分析 bean 的类和超类, ...
Dynamics CRM Microsoft SQL Server 指定的数据库具有更高的版本号
在做NLB部署时遇到这么个问题,CRMAPP1安装的CRM版本号是6.1已经打了SP1补丁,而在CRMAPP2上的CRM安装包是6.0版本号.在选择连接现有部署后,最后一步检測就出了问题,例如以下图所 ...
uefi bios安装ubuntu16.04 （win10和ubuntu双系统）
哎呀,没事闲的装双系统,按照晚上的教程装半天也没成功,后来才知道是自己电脑的问题,当然也有那些过时的博客的问题! ultraiso制作ubuntu u盘启动盘 http://www.cr173.co ...
利用mass storage class 做免驱动usb设备.
当需要使用usb bulk传输,想让设备像串口通讯那样和PC主机通信, 通常需要自己做一个PC端的驱动,比较麻烦. 为避免在pc上编写usb设备驱动的麻烦,可以将设备做成mass storage 类的 ...
JavaScript Patterns 2.3 For loops
HTMLCollections are objects returned by DOM methods such as: • document.getElementsByName() • docume ...

mha0.56版本安装使用排错

mha0.56版本安装使用排错的更多相关文章

随机推荐

热门专题