接上篇文章，介绍了如何安装mysql mha，地址如下：http://blog.csdn.net/yiyuf/article/details/40340895

下面接着进行mha的相关测试：

SSH 信任关系检测：

[root@mha scripts]# masterha_check_ssh --conf=/etc/app1.cnf

Fri Oct 17 09:45:45 2014 - [info] Reading default configuration from /etc/masterha_default.cnf..

Fri Oct 17 09:45:45 2014 - [info] Reading application default configuration from /etc/app1.cnf..

Fri Oct 17 09:45:45 2014 - [info] Reading server configuration from /etc/app1.cnf..

Fri Oct 17 09:45:45 2014 - [info] Starting SSH connection tests..

Fri Oct 17 09:45:46 2014 - [debug]

Fri Oct 17 09:45:45 2014 - [debug]  Connecting via SSH from root@192.168.56.110(192.168.56.110:22) to root@192.168.56.113(192.168.56.113:22)..

Fri Oct 17 09:45:46 2014 - [debug]   ok.

Fri Oct 17 09:45:47 2014 - [debug]

Fri Oct 17 09:45:46 2014 - [debug]  Connecting via SSH from root@192.168.56.113(192.168.56.113:22) to root@192.168.56.110(192.168.56.110:22)..

Fri Oct 17 09:45:47 2014 - [debug]   ok.

Fri Oct 17 09:45:47 2014 - [info] All SSH connection tests passed successfully

[root@mha ~]# masterha_check_repl --conf=/etc/app1.cnf 
Tue Oct 21 11:06:59 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Oct 21 11:06:59 2014 - [info] Reading application default configuration from /etc/app1.cnf..
Tue Oct 21 11:06:59 2014 - [info] Reading server configuration from /etc/app1.cnf..
Tue Oct 21 11:06:59 2014 - [info] MHA::MasterMonitor version 0.56.
Tue Oct 21 11:07:00 2014 - [info] GTID failover mode = 0
Tue Oct 21 11:07:00 2014 - [info] Dead Servers:
Tue Oct 21 11:07:00 2014 - [info] Alive Servers:
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.112(192.168.56.112:3306)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.113(192.168.56.113:3306)
Tue Oct 21 11:07:00 2014 - [info] Alive Slaves:
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.112(192.168.56.112:3306)  Version=5.5.40-36.1-log (oldest major version between slaves) log-bin:enabled
Tue Oct 21 11:07:00 2014 - [info]     Replicating from 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.113(192.168.56.113:3306)  Version=5.6.21-69.0-log log-bin:enabled
Tue Oct 21 11:07:00 2014 - [info]     Replicating from 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]     Not candidate for the new Master (no_master is set)
Tue Oct 21 11:07:00 2014 - [info] Current Alive Master: 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info] Checking slave configurations..
Tue Oct 21 11:07:00 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.56.112(192.168.56.112:3306).
Tue Oct 21 11:07:00 2014 - [info] Checking replication filtering settings..
Tue Oct 21 11:07:00 2014 - [info]  binlog_do_db= , binlog_ignore_db= 
Tue Oct 21 11:07:00 2014 - [info]  Replication filtering check ok.
Tue Oct 21 11:07:00 2014 - [info] GTID (with auto-pos) is not supported
Tue Oct 21 11:07:00 2014 - [info] Starting SSH connection tests..
Tue Oct 21 11:07:06 2014 - [info] All SSH connection tests passed successfully.
Tue Oct 21 11:07:06 2014 - [info] Checking MHA Node version..
Tue Oct 21 11:07:07 2014 - [info]  Version check ok.
Tue Oct 21 11:07:07 2014 - [info] Checking SSH publickey authentication settings on the current master..
Tue Oct 21 11:07:07 2014 - [info] HealthCheck: SSH to 192.168.56.110 is reachable.
Tue Oct 21 11:07:07 2014 - [info] Master MHA Node version is 0.56.
Tue Oct 21 11:07:07 2014 - [info] Checking recovery script configurations on 192.168.56.110(192.168.56.110:3306)..
Tue Oct 21 11:07:07 2014 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/log/masterha/app1/save_binary_logs_test --manager_version=0.56 --start_file=561103306-bin.000010 
Tue Oct 21 11:07:07 2014 - [info]   Connecting to root@192.168.56.110(192.168.56.110:22).. 
  Creating /var/log/masterha/app1 if not exists..    ok.
  Checking output directory is accessible or not..
   ok.
  Binlog found at /var/lib/mysql, up to 561103306-bin.000010
Tue Oct 21 11:07:08 2014 - [info] Binlog setting check done.
Tue Oct 21 11:07:08 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Tue Oct 21 11:07:08 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='yyf' --slave_host=192.168.56.112 --slave_ip=192.168.56.112 --slave_port=3306 --workdir=/var/log/masterha/app1 --target_version=5.5.40-36.1-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx
Tue Oct 21 11:07:08 2014 - [info]   Connecting to root@192.168.56.112(192.168.56.112:22).. 
  Checking slave recovery environment settings..
    Opening /var/lib/mysql/relay-log.info ... ok.
    Relay log found at /var/lib/mysql, up to mysqld-relay-bin.000002
    Temporary relay log file is /var/lib/mysql/mysqld-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Tue Oct 21 11:07:08 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='yyf' --slave_host=192.168.56.113 --slave_ip=192.168.56.113 --slave_port=3306 --workdir=/var/log/masterha/app1 --target_version=5.6.21-69.0-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx
Tue Oct 21 11:07:08 2014 - [info]   Connecting to root@192.168.56.113(192.168.56.113:22).. 
  Checking slave recovery environment settings..
    Opening /var/lib/mysql/relay-log.info ... ok.
    Relay log found at /var/lib/mysql, up to mysqld-relay-bin.000002
    Temporary relay log file is /var/lib/mysql/mysqld-relay-bin.000002
    Testing mysql connection and privileges..Warning: Using a password on the command line interface can be insecure.
 done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Tue Oct 21 11:07:17 2014 - [info] Slaves settings check done.
Tue Oct 21 11:07:17 2014 - [info] 
192.168.56.110(192.168.56.110:3306) (current master)
 +--192.168.56.112(192.168.56.112:3306)
 +--192.168.56.113(192.168.56.113:3306)
Tue Oct 21 11:07:17 2014 - [info] Checking replication health on 192.168.56.112..
Tue Oct 21 11:07:17 2014 - [info]  ok.
Tue Oct 21 11:07:17 2014 - [info] Checking replication health on 192.168.56.113..
Tue Oct 21 11:07:17 2014 - [info]  ok.
Tue Oct 21 11:07:17 2014 - [info] Checking master_ip_failover_script status:
Tue Oct 21 11:07:17 2014 - [info]   /root/scripts/master_ip_failover.sh --command=status --ssh_user=root --orig_master_host=192.168.56.110 --orig_master_ip=192.168.56.110 --orig_master_port=3306 
IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===
Checking the Status of the script.. OK 
Tue Oct 21 11:07:17 2014 - [info]  OK.
Tue Oct 21 11:07:17 2014 - [warning] shutdown_script is not defined.
Tue Oct 21 11:07:17 2014 - [info] Got exit code 0 (Not master dead).
MySQL Replication Health is OK.

MySQL MHA相关测试的更多相关文章

  1. MySQL MHA+Keepalived

    一.MHA的简单介绍MHA是由perl语言编写的,用外挂脚本的方式实现mysql主从复制的高可用性.MHA可以自动检测mysql是否宕机,如果宕机,在10-30s内完成new master的选举,应用 ...

  2. MYSQL MHA

    MYSQL MHA 简介: MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司youshimaton(现就职于 Face ...

  3. 搭建MySQL MHA高可用

    本文内容参考:http://www.ttlsa.com/mysql/step-one-by-one-deploy-mysql-mha-cluster/ MySQL MHA 高可用集群 环境: Linu ...

  4. CENTOS6.6 下mysql MHA架构搭建

    本文来自我的github pages博客http://galengao.github.io/ 即www.gaohuirong.cn 摘要: 本篇是自己搭建的一篇mysql MHA文章 前面的安装步骤基 ...

  5. mysql MHA架构搭建过程

    [环境介绍] 系统环境:Red Hat Enterprise Linux 7 + 5.7.18 + MHA version 0.57 系统 IP 主机名 备注 版本 xx系统 192.168.142. ...

  6. CentOS6.8下MySQL MHA架构搭建笔记

    转载请注明出处,本文地址:http://www.cnblogs.com/ajiangg/p/6552855.html 以下是CentOS6.8下MySQL MHA架构搭建笔记 IP资源规划: 192. ...

  7. MySQL MHA 搭建&测试（环境：CentOS7 + MySQL5.7.23）

    MySQL MHA架构介绍: MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司youshimaton(现就职于Face ...

  8. 基于Docker Compose构建的MySQL MHA集群

    Docker MySQL MHA 基于Docker 1.13.1之上构建的MySQL MHA Docker Compose Project 可快速启动GTID模式下的MasterHA集群, 主用于My ...

  9. 基于MySQL+MHA+Haproxy部署高可用负载均衡集群

    一.MHA 概述 MHA(Master High Availability)是可以在MySQL上使用的一套高可用方案.所编写的语言为Perl 从名字上我们可以看到.MHA的目的就是为了维护Master ...

随机推荐

  1. python学习笔记（十九）面向对象编程，类

    一.面向对象编程 面向对象,是一种程序设计思想. 编程范式:编程范式就是你按照什么方式去编程,去实现一个功能.不同的编程范式本质上代表对各种类型的任务采取的不同的解决问题的思路,两种最重要的编程范式分 ...

  2. OC + RAC(七) RACSubject和RACSignal的区别

    -(void)_test8{ /// RACSubject继承自RACSignal 但是RACSubject和RACSignal的区别? //1能接收1,2 //但是2只能接收2 RACSubject ...

  3. PHPcms编辑器如何粘贴带格式的word文档

    在之前在工作中遇到在富文本编辑器中粘贴图片不能展示的问题,于是各种网上扒拉,终于找到解决方案,在这里感谢一下知乎中众大神以及TheViper. 通过知乎提供的思路找到粘贴的原理,通过TheViper找 ...

  4. 如何从word中复制内容到网站后台编辑器中

    word图片转存,是指UEditor为了解决用户从word中复制了一篇图文混排的文章粘贴到编辑器之后,word文章中的图片数据无法显示在编辑器中,也无法提交到服务器上的问题而开发的一个操作简便的图片转 ...

  5. Android签名机制之---签名验证过程详解

    一.前言 今天是元旦,也是Single Dog的嚎叫之日,只能写博客来祛除寂寞了,今天我们继续来看一下Android中的签名机制的姊妹篇:Android中是如何验证一个Apk的签名.在前一篇文章中我们 ...

  6. C# 图片剪切与缩小的实例

    public void CutToF(Stream stream) { Image initImage = Image.FromStream(stream, true); && ini ...

  7. 问候 UEditor 的大爷

    记录该日志的时间是2015年2月1日. 先给出 UEditor 项目的首页,它是一款由百度开发的开源富文本编辑器,关于它的介绍,大家可以查看百度百科. UEditor - 首页http://uedit ...

  8. Linux下安装mysql教程

    Linux下安装mysql  MySQL官网:https://dev.mysql.com/downloads/mysql/ 到mysql官网下载mysql编译好的二进制安装包,在下载页面Select ...

  9. hbase报Dead Region Servers

    问题描述: 16010端口启动成功,16020未启动. hbase-root-regionserver-hbase2.log日志: 2019-08-14 16:45:10,552 WARN [Thre ...

  10. postman测试wsdl类型接口

    1 IP地址来源搜索 WEB 服务 接口信息 http://www.webxml.com.cn/WebServices/WeatherWebService.asmx?wsdl 2  设置接口调用地址 ...