MHA启动过程

环境:
Master:192.168.100.50
Slave1:192.168.100.48
Slave2:192.168.100.141 (MHA管理节点)

[root@test11g log]# tail -f mha.log 
Thu Nov 20 17:51:50 2014 - [info] MHA::MasterMonitor version 0.56.
Thu Nov 20 17:51:50 2014 - [info] GTID failover mode = 0
Thu Nov 20 17:51:50 2014 - [info] Dead Servers:
Thu Nov 20 17:51:50 2014 - [info] Alive Servers:
Thu Nov 20 17:51:50 2014 - [info]   192.168.100.50(192.168.100.50:3306)
Thu Nov 20 17:51:50 2014 - [info]   192.168.100.48(192.168.100.48:3306)
Thu Nov 20 17:51:50 2014 - [info]   192.168.100.141(192.168.100.141:3306)
Thu Nov 20 17:51:50 2014 - [info] Alive Slaves:
Thu Nov 20 17:51:50 2014 - [info]   192.168.100.48(192.168.100.48:3306)  Version=5.5.18-log (oldest major version between slaves) log-bin:enabled
Thu Nov 20 17:51:50 2014 - [info]     Replicating from 192.168.100.50(192.168.100.50:3306)
Thu Nov 20 17:51:50 2014 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Nov 20 17:51:50 2014 - [info]   192.168.100.141(192.168.100.141:3306)  Version=5.5.18-log (oldest major version between slaves) log-bin:enabled
Thu Nov 20 17:51:50 2014 - [info]     Replicating from 192.168.100.50(192.168.100.50:3306)
Thu Nov 20 17:51:50 2014 - [info] Current Alive Master: 192.168.100.50(192.168.100.50:3306)
Thu Nov 20 17:51:50 2014 - [info] Checking slave configurations..
Thu Nov 20 17:51:50 2014 - [info] Checking replication filtering settings..
Thu Nov 20 17:51:50 2014 - [info]  binlog_do_db= , binlog_ignore_db= 
Thu Nov 20 17:51:50 2014 - [info]  Replication filtering check ok.
Thu Nov 20 17:51:50 2014 - [info] GTID (with auto-pos) is not supported
Thu Nov 20 17:51:50 2014 - [info] Starting SSH connection tests..
Thu Nov 20 17:51:52 2014 - [info] All SSH connection tests passed successfully.
Thu Nov 20 17:51:52 2014 - [info] Checking MHA Node version..
Thu Nov 20 17:51:52 2014 - [info]  Version check ok.
Thu Nov 20 17:51:52 2014 - [info] Checking SSH publickey authentication settings on the current master..
Thu Nov 20 17:51:53 2014 - [info] HealthCheck: SSH to 192.168.100.50 is reachable.
Thu Nov 20 17:51:53 2014 - [info] Master MHA Node version is 0.56.
Thu Nov 20 17:51:53 2014 - [info] Checking recovery script configurations on 192.168.100.50(192.168.100.50:3306)..
Thu Nov 20 17:51:53 2014 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/tol/mysql/binlog --output_file=/tmp/save_binary_logs_test --manager_version=0.56 --start_file=mysql-bin.000004 
Thu Nov 20 17:51:53 2014 - [info]   Connecting to root@192.168.100.50(192.168.100.50:22).. 
  Creating /tmp if not exists..    ok.
  Checking output directory is accessible or not..
   ok.
  Binlog found at /tol/mysql/binlog, up to mysql-bin.000004
Thu Nov 20 17:51:53 2014 - [info] Binlog setting check done.
Thu Nov 20 17:51:53 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Thu Nov 20 17:51:53 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='root' --slave_host=192.168.100.48 --slave_ip=192.168.100.48 --slave_port=3306 --workdir=/tmp --target_version=5.5.18-log --manager_version=0.56 --relay_log_info=/tol/mysql/data/relay-log.info  --relay_dir=/tol/mysql/data/  --slave_pass=xxx
Thu Nov 20 17:51:53 2014 - [info]   Connecting to root@192.168.100.48(192.168.100.48:22).. 
  Checking slave recovery environment settings..
    Opening /tol/mysql/data/relay-log.info ... ok.
    Relay log found at /tol/mysql/data, up to coredb-relay-bin.000002
    Temporary relay log file is /tol/mysql/data/coredb-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Thu Nov 20 17:51:54 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='root' --slave_host=192.168.100.141 --slave_ip=192.168.100.141 --slave_port=3306 --workdir=/tmp --target_version=5.5.18-log --manager_version=0.56 --relay_log_info=/tol/mysql/data/relay-log.info  --relay_dir=/tol/mysql/data/  --slave_pass=xxx
Thu Nov 20 17:51:54 2014 - [info]   Connecting to root@192.168.100.141(192.168.100.141:22).. 
  Checking slave recovery environment settings..
    Opening /tol/mysql/data/relay-log.info ... ok.
    Relay log found at /tol/mysql/data, up to test11g-relay-bin.000002
    Temporary relay log file is /tol/mysql/data/test11g-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Thu Nov 20 17:51:54 2014 - [info] Slaves settings check done.
Thu Nov 20 17:51:54 2014 - [info] 
192.168.100.50(192.168.100.50:3306) (current master)
 +--192.168.100.48(192.168.100.48:3306)
 +--192.168.100.141(192.168.100.141:3306)


Thu Nov 20 17:51:54 2014 - [info] Checking master_ip_failover_script status:
Thu Nov 20 17:51:54 2014 - [info]   /usr/bin/masterha_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.100.50 --orig_master_ip=192.168.100.50 --orig_master_port=3306 
Checking the Status of the script.. OK 
Thu Nov 20 17:51:54 2014 - [info]  OK.
Thu Nov 20 17:51:54 2014 - [warning] shutdown_script is not defined.
Thu Nov 20 17:51:54 2014 - [info] Set master ping interval 1 seconds.
Thu Nov 20 17:51:54 2014 - [info] Set secondary check script: /usr/bin/masterha_secondary_check -s coredb -s goolen --user=root --master_host=goolen --master_ip=192.168.100.50 --master_port=3306
Thu Nov 20 17:51:54 2014 - [info] Starting ping health check on 192.168.100.50(192.168.100.50:3306)..
Thu Nov 20 17:51:54 2014 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

+++其中“ Ping(SELECT) succeeded” 输出说明整个系统监控已经开始了。


来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/23249684/viewspace-1340736/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/23249684/viewspace-1340736/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值