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 是一个基于 ...

随机推荐

[Javascript] JavaScript赋值时的传值与传址
JavaScript中有两种不同数据类型的值,分别是基本数据类型与引用数据类型基本数据类型包含5类,分别是:Number.String.Boolean.Null.Undefined 引用数据类型包含 ...
黑马程序猿——JAVA基础——IO流
----------android培训.java培训.java学习型技术博客.期待与您交流!------------ 一. 一.IO流的三种分类方式 1.按流的方向分为:输入流和输出流 2.按流的数 ...
struts2国际化---配置国际化全局资源文件并输出国际化资源信息
我们首先学习怎么配置国际化全局资源文件.并输出资源文件信息 1.首先struts2项目搭建完毕后,我们在src文件夹下.即struts2.xml同级文件夹下创建资源文件.资源文件的名称格式为: XXX ...
Java原型模式之浅拷贝-深拷贝
一.是什么? 浅拷贝:对值类型的成员变量进行值的复制,对引用类型的成员变量仅仅复制引用,不复制引用的对象深拷贝:对值类型的成员变量进行值的复制,对引用类型的成员变量也进行引用对象的复制内部机制: ...
oc80--copy
// // main.m // Copy基本使用,拷贝的本质:修改其中一个不能影响另外一个. // 每个oc对象都有copy和mutableCopy方法,前提是必须遵守NSCopying协议实现cop ...
MDK链接脚本错误
我想让我的程序运行在RAM中而不是在SPI FLASH上,写了一个scatterfile: ROM 0x00000000 0x00200000 ;spi flash{STARTUP +0 { star ...
ALSA声卡驱动中的DAPM详解之六：精髓所在，牵一发而动全身
设计dapm的主要目的之一,就是希望声卡上的各种部件的电源按需分配,需要的就上电,不需要的就下电,使得整个音频系统总是处于最小的耗电状态,最主要的就是,这一切对用户空间的应用程序是透明的,也就是说,用 ...
iOS开发基础：OC数组对象NSArray的常用方法
本文介绍了OC的数组对象的基本方法的使用: 因为OC的数组中存储的为对象类型,所以我们可以新建一个Person类,通过Person生成对象进行操作. 其中Person.h中的代码为: [objc] v ...
unique(V.begin(),V.end())
unique(V.begin(),V.end()) 重排容器算法:sort,unique unique 返回指向不重复区域之后一个位置的迭代器 ///删除vstr中重复的元素 void delete ...
树的遍历迭代算法——思路：初始化stack，pop stack利用pop的node，push new node to stack，可以考虑迭代一颗树因为后序遍历最后还要要访问根结点一次，所以要访问根结点两次是难点
144. Binary Tree Preorder Traversal Given a binary tree, return the preorder traversal of its nodes' ...

mha0.56版本安装使用排错

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

随机推荐

热门专题