MySQL 高可用 MHA check scripts
发表于:2025-11-06 作者:千家信息网编辑
千家信息网最后更新 2025年11月06日,介绍几个MHA check 命令,输出如下[root@MHA bin]# pwd/usr/local/bin[root@MHA bin]# ls -ltotal 104-r-xr-xr-x. 1 ro
千家信息网最后更新 2025年11月06日MySQL 高可用 MHA check scripts
介绍几个MHA check 命令,输出如下
[root@MHA bin]# pwd/usr/local/bin[root@MHA bin]# ls -ltotal 104-r-xr-xr-x. 1 root root 16367 Sep 7 09:43 apply_diff_relay_logs-r-xr-xr-x. 1 root root 4807 Sep 7 09:43 filter_mysqlbinlog-r-xr-xr-x. 1 root root 1995 Sep 7 09:22 masterha_check_repl-r-xr-xr-x. 1 root root 1779 Sep 7 09:22 masterha_check_ssh-r-xr-xr-x. 1 root root 1865 Sep 7 09:22 masterha_check_status-r-xr-xr-x. 1 root root 3201 Sep 7 09:22 masterha_conf_host-r-xr-xr-x. 1 root root 2517 Sep 7 09:22 masterha_manager-r-xr-xr-x. 1 root root 2165 Sep 7 09:22 masterha_master_monitor-r-xr-xr-x. 1 root root 2373 Sep 7 09:22 masterha_master_switch-r-xr-xr-x. 1 root root 5171 Sep 7 09:22 masterha_secondary_check-r-xr-xr-x. 1 root root 1739 Sep 7 09:22 masterha_stop-rwxr-xr-x. 1 root root 4598 Sep 7 14:20 master_ip_failover-rwxr-xr-x. 1 root root 10101 Sep 7 14:32 master_ip_online_change-r-xr-xr-x. 1 root root 8261 Sep 7 09:43 purge_relay_logs-r-xr-xr-x. 1 root root 7525 Sep 7 09:43 save_binary_logs[root@MHA bin]# masterha_check_ssh --conf=/etc/app1.cnf Sun Sep 9 08:27:02 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Sun Sep 9 08:27:02 2018 - [info] Reading application default configuration from /etc/app1.cnf..Sun Sep 9 08:27:02 2018 - [info] Reading server configuration from /etc/app1.cnf..Sun Sep 9 08:27:02 2018 - [info] Starting SSH connection tests..Sun Sep 9 08:27:02 2018 - [debug] Sun Sep 9 08:27:02 2018 - [debug] Connecting via SSH from root@master(192.168.56.101:22) to root@slave1(192.168.56.102:22)..Sun Sep 9 08:27:02 2018 - [debug] ok.Sun Sep 9 08:27:02 2018 - [debug] Connecting via SSH from root@master(192.168.56.101:22) to root@slave2(192.168.56.103:22)..Sun Sep 9 08:27:02 2018 - [debug] ok.Sun Sep 9 08:27:03 2018 - [debug] Sun Sep 9 08:27:02 2018 - [debug] Connecting via SSH from root@slave1(192.168.56.102:22) to root@master(192.168.56.101:22)..Sun Sep 9 08:27:03 2018 - [debug] ok.Sun Sep 9 08:27:03 2018 - [debug] Connecting via SSH from root@slave1(192.168.56.102:22) to root@slave2(192.168.56.103:22)..Sun Sep 9 08:27:03 2018 - [debug] ok.Sun Sep 9 08:27:03 2018 - [debug] Sun Sep 9 08:27:03 2018 - [debug] Connecting via SSH from root@slave2(192.168.56.103:22) to root@master(192.168.56.101:22)..Sun Sep 9 08:27:03 2018 - [debug] ok.Sun Sep 9 08:27:03 2018 - [debug] Connecting via SSH from root@slave2(192.168.56.103:22) to root@slave1(192.168.56.102:22)..Sun Sep 9 08:27:03 2018 - [debug] ok.Sun Sep 9 08:27:03 2018 - [info] All SSH connection tests passed successfully.[root@MHA bin]# masterha_check_repl --conf=/etc/app1.cnf Sun Sep 9 08:27:15 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Sun Sep 9 08:27:15 2018 - [info] Reading application default configuration from /etc/app1.cnf..Sun Sep 9 08:27:15 2018 - [info] Reading server configuration from /etc/app1.cnf..Sun Sep 9 08:27:15 2018 - [info] MHA::MasterMonitor version 0.56.Sun Sep 9 08:27:16 2018 - [info] GTID failover mode = 0Sun Sep 9 08:27:16 2018 - [info] Dead Servers:Sun Sep 9 08:27:16 2018 - [info] Alive Servers:Sun Sep 9 08:27:16 2018 - [info] master(192.168.56.101:3306)Sun Sep 9 08:27:16 2018 - [info] slave1(192.168.56.102:3306)Sun Sep 9 08:27:16 2018 - [info] slave2(192.168.56.103:3306)Sun Sep 9 08:27:16 2018 - [info] Alive Slaves:Sun Sep 9 08:27:16 2018 - [info] slave1(192.168.56.102:3306) Version=10.1.35-MariaDB (oldest major version between slaves) log-bin:enabledSun Sep 9 08:27:16 2018 - [info] Replicating from 192.168.56.101(192.168.56.101:3306)Sun Sep 9 08:27:16 2018 - [info] slave2(192.168.56.103:3306) Version=10.1.35-MariaDB (oldest major version between slaves) log-bin:enabledSun Sep 9 08:27:16 2018 - [info] Replicating from 192.168.56.101(192.168.56.101:3306)Sun Sep 9 08:27:16 2018 - [info] Current Alive Master: master(192.168.56.101:3306)Sun Sep 9 08:27:16 2018 - [info] Checking slave configurations..Sun Sep 9 08:27:16 2018 - [info] Checking replication filtering settings..Sun Sep 9 08:27:16 2018 - [info] binlog_do_db= , binlog_ignore_db= Sun Sep 9 08:27:16 2018 - [info] Replication filtering check ok.Sun Sep 9 08:27:16 2018 - [info] GTID (with auto-pos) is not supportedSun Sep 9 08:27:16 2018 - [info] Starting SSH connection tests..Sun Sep 9 08:27:17 2018 - [info] All SSH connection tests passed successfully.Sun Sep 9 08:27:17 2018 - [info] Checking MHA Node version..Sun Sep 9 08:27:18 2018 - [info] Version check ok.Sun Sep 9 08:27:18 2018 - [info] Checking SSH publickey authentication settings on the current master..Sun Sep 9 08:27:18 2018 - [info] HealthCheck: SSH to master is reachable.Sun Sep 9 08:27:18 2018 - [info] Master MHA Node version is 0.56.Sun Sep 9 08:27:18 2018 - [info] Checking recovery script configurations on master(192.168.56.101:3306)..Sun Sep 9 08:27:18 2018 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data/binlogs --output_file=/var/log/masterha//save_binary_logs_test --manager_version=0.56 --start_file=mysql-bin.000005 Sun Sep 9 08:27:18 2018 - [info] Connecting to root@192.168.56.101(master:22).. Creating /var/log/masterha if not exists.. ok. Checking output directory is accessible or not.. ok. Binlog found at /data/binlogs, up to mysql-bin.000005Sun Sep 9 08:27:19 2018 - [info] Binlog setting check done.Sun Sep 9 08:27:19 2018 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..Sun Sep 9 08:27:19 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=slave1 --slave_ip=192.168.56.102 --slave_port=3306 --workdir=/var/log/masterha/ --target_version=10.1.35-MariaDB --manager_version=0.56 --relay_log_info=/data/mysql/relay-log.info --relay_dir=/data/mysql/ --slave_pass=xxxSun Sep 9 08:27:19 2018 - [info] Connecting to root@192.168.56.102(slave1:22).. Checking slave recovery environment settings.. Opening /data/mysql/relay-log.info ... ok. Relay log found at /data/relaylogs, up to relay-bin.000015 Temporary relay log file is /data/relaylogs/relay-bin.000015 Testing mysql connection and privileges.. done. Testing mysqlbinlog output.. done. Cleaning up test file(s).. done.Sun Sep 9 08:27:19 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=slave2 --slave_ip=192.168.56.103 --slave_port=3306 --workdir=/var/log/masterha/ --target_version=10.1.35-MariaDB --manager_version=0.56 --relay_log_info=/data/mysql/relay-log.info --relay_dir=/data/mysql/ --slave_pass=xxxSun Sep 9 08:27:19 2018 - [info] Connecting to root@192.168.56.103(slave2:22).. Checking slave recovery environment settings.. Opening /data/mysql/relay-log.info ... ok. Relay log found at /data/relaylogs, up to relay-bin.000015 Temporary relay log file is /data/relaylogs/relay-bin.000015 Testing mysql connection and privileges.. done. Testing mysqlbinlog output.. done. Cleaning up test file(s).. done.Sun Sep 9 08:27:19 2018 - [info] Slaves settings check done.Sun Sep 9 08:27:19 2018 - [info] master(192.168.56.101:3306) (current master) +--slave1(192.168.56.102:3306) +--slave2(192.168.56.103:3306)Sun Sep 9 08:27:19 2018 - [info] Checking replication health on slave1..Sun Sep 9 08:27:19 2018 - [info] ok.Sun Sep 9 08:27:19 2018 - [info] Checking replication health on slave2..Sun Sep 9 08:27:19 2018 - [info] ok.Sun Sep 9 08:27:19 2018 - [info] Checking master_ip_failover_script status:Sun Sep 9 08:27:19 2018 - [info] /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=master --orig_master_ip=192.168.56.101 --orig_master_port=3306 inet 192.168.56.105/32 scope global eth2INFO: VIP 192.168.1.100 found on MasterSun Sep 9 08:27:19 2018 - [info] OK.Sun Sep 9 08:27:19 2018 - [warning] shutdown_script is not defined.Sun Sep 9 08:27:19 2018 - [info] Got exit code 0 (Not master dead).MySQL Replication Health is OK.[root@MHA bin]# [root@MHA bin]# masterha_check_smasterha_check_ssh masterha_check_status [root@MHA bin]# masterha_check_status --conf=/etc/app1.cnf app1 is stopped(2:NOT_RUNNING).[root@MHA bin]# masterha_check_status Either --conf or --status_dir must be set. at /usr/local/share/perl5/MHA/ManagerAdminWrapper.pm line 121[root@MHA bin]#
命令
输出
数据库的安全要保护哪些东西
数据库安全各自的含义是什么
生产安全数据库录入
数据库的安全性及管理
数据库安全策略包含哪些
海淀数据库安全审计系统
建立农村房屋安全信息数据库
易用的数据库客户端支持安全管理
连接数据库失败ssl安全错误
数据库的锁怎样保障安全
服务器出租传奇需要远程管理吗
网络安全关系着税收
易飞服务器打不开
河南通用软件开发售价
模拟钢琴软件开发
说明网络安全的重要性的例子
思科网络技术学院教程第三章
答辩运用了哪些网络安全防护技术
深圳软件开发公司前程无忧招聘
软件开发的顶层设计
中国网络安全大赛的主要人物
萨迩数据库访问
双路服务器可以只用一个CPU吗
数据库被锁死其他进程还能访问吗
万方数据库收录检索
数据库中如何实现用户点击统计
海南综合软件开发预算
服务器网络受限
学习数据库怎么赚钱
数据库交易平台
如何兼职做服务器管理工作
杭州线上内训软件开发
属于数据库应用系统
手机软件开发软件工具
宝山区互联网软件开发内容
不是数据库字段
深圳孙悟空互联网科技有限公司
银上网络技术有限公司怎么样
世界互联网科技成果发布
数据库VBA选择题及答案