首页 数据库 mysql教程 MHA+非root用户SSH等效性配置

MHA+非root用户SSH等效性配置

Jun 07, 2016 pm 04:02 PM
root ssh 环境 用户 配置

环境:CentOS5.8 MySQL5.5.17 实验:搭建MHA高可用架构(非root用户SSH等效性配置)SSH等效性用户配置的是:concert 端口:1314 MHA配置文件 [concert@mhamanager mha]$ more /etc/masterha_default.cnf [server default] user = root password = mysql_admi

环境:CentOS5.8

MySQL5.5.17

实验:搭建MHA高可用架构(非root用户SSH等效性配置)SSH等效性用户配置的是:concert 端口:1314

MHA配置文件

[concert@mhamanager mha]$ more /etc/masterha_default.cnf
[server default]
user = root
password = mysql_admin
ssh_user = concert
ssh_port = 1314
repl_user = repl
repl_password = repl_pwd
ping_interval = 3
ping_type = select

[concert@mhamanager mha]$ more /etc/appl.cnf
[server default]
manager_workdir = /mha/appl
manager_log = /mha/appl/manager.log
remote_workdir = /mha/appl

[server1]
hostname = 192.168.66.88
master_binlog_dir = /data/lib/mysql
candidate_master = 1

[server2]
hostname = 192.168.66.89
master_binlog_dir = /data/lib/mysql
candidate_master = 1

[server3]
hostname = 192.168.66.120
no_master = 1
port = 3307

问题:配置好非root用户SSH等效性后,通过masterha_check_ssh检查没有问题

[concert@mhamanager ~]$ /usr/bin/masterha_check_ssh --conf=/etc/appl.cnf
Tue Sep 2 15:06:01 2014 - [info] Reading default configuratoins from /etc/masterha_default.cnf..
Tue Sep 2 15:06:01 2014 - [info] Reading application default configurations from /etc/appl.cnf..
Tue Sep 2 15:06:01 2014 - [info] Reading server configurations from /etc/appl.cnf..
Tue Sep 2 15:06:01 2014 - [info] Starting SSH connection tests..
Tue Sep 2 15:06:01 2014 - [debug]
Tue Sep 2 15:06:01 2014 - [debug] Connecting via SSH from concert@192.168.66.88(192.168.66.88:1314) to concert@192.168.66.89(192.168.66.89:1314)..
Tue Sep 2 15:06:01 2014 - [debug] ok.
Tue Sep 2 15:06:01 2014 - [debug] Connecting via SSH from concert@192.168.66.88(192.168.66.88:1314) to concert@192.168.66.120(192.168.66.120:1314)..
Tue Sep 2 15:06:01 2014 - [debug] ok.
Tue Sep 2 15:06:02 2014 - [debug]
Tue Sep 2 15:06:01 2014 - [debug] Connecting via SSH from concert@192.168.66.89(192.168.66.89:1314) to concert@192.168.66.88(192.168.66.88:1314)..
Tue Sep 2 15:06:01 2014 - [debug] ok.
Tue Sep 2 15:06:01 2014 - [debug] Connecting via SSH from concert@192.168.66.89(192.168.66.89:1314) to concert@192.168.66.120(192.168.66.120:1314)..
Tue Sep 2 15:06:02 2014 - [debug] ok.
Tue Sep 2 15:06:02 2014 - [debug]
Tue Sep 2 15:06:02 2014 - [debug] Connecting via SSH from concert@192.168.66.120(192.168.66.120:1314) to concert@192.168.66.88(192.168.66.88:1314)..
Tue Sep 2 15:06:02 2014 - [debug] ok.
Tue Sep 2 15:06:02 2014 - [debug] Connecting via SSH from concert@192.168.66.120(192.168.66.120:1314) to concert@192.168.66.89(192.168.66.89:1314)..
Tue Sep 2 15:06:02 2014 - [debug] ok.
Tue Sep 2 15:06:02 2014 - [info] All SSH connection tests passed successfully.

但通过masterha_check_repl检查则不通过

[concert@mhamanager ~]$ /usr/bin/masterha_check_repl --conf=/etc/appl.cnf
Tue Sep 2 17:10:08 2014 - [info] Reading default configuratoins from /etc/masterha_default.cnf..
Tue Sep 2 17:10:08 2014 - [info] Reading application default configurations from /etc/appl.cnf..
Tue Sep 2 17:10:08 2014 - [info] Reading server configurations from /etc/appl.cnf..
Tue Sep 2 17:10:08 2014 - [info] MHA::MasterMonitor version 0.55.
Tue Sep 2 17:10:08 2014 - [info] Dead Servers:
Tue Sep 2 17:10:08 2014 - [info] Alive Servers:
Tue Sep 2 17:10:08 2014 - [info] 192.168.66.88(192.168.66.88:3306)
Tue Sep 2 17:10:08 2014 - [info] 192.168.66.89(192.168.66.89:3306)
Tue Sep 2 17:10:08 2014 - [info] 192.168.66.120(192.168.66.120:3307)
Tue Sep 2 17:10:08 2014 - [info] Alive Slaves:
Tue Sep 2 17:10:08 2014 - [info] 192.168.66.89(192.168.66.89:3306) Version=5.5.17-log (oldest major version between slaves) log-bin:enabled
Tue Sep 2 17:10:08 2014 - [info] Replicating from 192.168.66.88(192.168.66.88:3306)
Tue Sep 2 17:10:08 2014 - [info] Primary candidate for the new Master (candidate_master is set)
Tue Sep 2 17:10:08 2014 - [info] 192.168.66.120(192.168.66.120:3307) Version=5.5.17-log (oldest major version between slaves) log-bin:enabled
Tue Sep 2 17:10:08 2014 - [info] Replicating from 192.168.66.88(192.168.66.88:3306)
Tue Sep 2 17:10:08 2014 - [info] Not candidate for the new Master (no_master is set)
Tue Sep 2 17:10:08 2014 - [info] Current Alive Master: 192.168.66.88(192.168.66.88:3306)
Tue Sep 2 17:10:08 2014 - [info] Checking slave configurations..
Tue Sep 2 17:10:08 2014 - [info] Checking replication filtering settings..
Tue Sep 2 17:10:08 2014 - [info] binlog_do_db= , binlog_ignore_db=
Tue Sep 2 17:10:08 2014 - [info] Replication filtering check ok.
Tue Sep 2 17:10:08 2014 - [info] Starting SSH connection tests..
Tue Sep 2 17:10:10 2014 - [error][/usr/lib/perl5/vendor_perl/MHA/MasterMonitor.pm, ln386] Error happend on checking configurations. SSH Configuration Check Failed!
at /usr/lib/perl5/vendor_perl/MHA/MasterMonitor.pm line 341
Tue Sep 2 17:10:10 2014 - [error][/usr/lib/perl5/vendor_perl/MHA/MasterMonitor.pm, ln482] Error happened on monitoring servers.
Tue Sep 2 17:10:10 2014 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

解决方案

1、增加remote_workdir(运行MySQL实例的服务器)的工作目录权限,其中会生成日志文件,将该目录拥有者设为concert

[root@master88 ~]# chown -R concert:concert /mha/

2、添加concert为MySQL同组用户,使其有读取MySQL binary/relay log文件和relay_log.info文件的权限,以及日志目录的写权限

[root@bakmaster ~]# usermod -g mysql concert

再次检查

[concert@mhamanager mha]$ /usr/bin/masterha_check_repl --conf=/etc/appl.cnf
Wed Sep 3 22:27:41 2014 - [info] Reading default configuratoins from /etc/masterha_default.cnf..
Wed Sep 3 22:27:41 2014 - [info] Reading application default configurations from /etc/appl.cnf..
Wed Sep 3 22:27:41 2014 - [info] Reading server configurations from /etc/appl.cnf..
Wed Sep 3 22:27:41 2014 - [info] MHA::MasterMonitor version 0.55.
Wed Sep 3 22:27:41 2014 - [info] Dead Servers:
Wed Sep 3 22:27:41 2014 - [info] Alive Servers:
Wed Sep 3 22:27:41 2014 - [info] 192.168.66.88(192.168.66.88:3306)
Wed Sep 3 22:27:41 2014 - [info] 192.168.66.89(192.168.66.89:3306)
Wed Sep 3 22:27:41 2014 - [info] 192.168.66.120(192.168.66.120:3307)
Wed Sep 3 22:27:41 2014 - [info] Alive Slaves:
Wed Sep 3 22:27:41 2014 - [info] 192.168.66.89(192.168.66.89:3306) Version=5.5.17-log (oldest major version between slaves) log-bin:enabled
Wed Sep 3 22:27:41 2014 - [info] Replicating from 192.168.66.88(192.168.66.88:3306)
Wed Sep 3 22:27:41 2014 - [info] Primary candidate for the new Master (candidate_master is set)
Wed Sep 3 22:27:41 2014 - [info] 192.168.66.120(192.168.66.120:3307) Version=5.5.17-log (oldest major version between slaves) log-bin:enabled
Wed Sep 3 22:27:41 2014 - [info] Replicating from 192.168.66.88(192.168.66.88:3306)
Wed Sep 3 22:27:41 2014 - [info] Not candidate for the new Master (no_master is set)
Wed Sep 3 22:27:41 2014 - [info] Current Alive Master: 192.168.66.88(192.168.66.88:3306)
Wed Sep 3 22:27:41 2014 - [info] Checking slave configurations..
Wed Sep 3 22:27:41 2014 - [info] Checking replication filtering settings..
Wed Sep 3 22:27:41 2014 - [info] binlog_do_db= , binlog_ignore_db=
Wed Sep 3 22:27:41 2014 - [info] Replication filtering check ok.
Wed Sep 3 22:27:41 2014 - [info] Starting SSH connection tests..
Wed Sep 3 22:27:42 2014 - [info] All SSH connection tests passed successfully.
Wed Sep 3 22:27:42 2014 - [info] Checking MHA Node version..
Wed Sep 3 22:27:43 2014 - [info] Version check ok.
Wed Sep 3 22:27:43 2014 - [info] Checking SSH publickey authentication settings on the current master..
Wed Sep 3 22:27:43 2014 - [info] HealthCheck: SSH to 192.168.66.88 is reachable.
Wed Sep 3 22:27:43 2014 - [info] Master MHA Node version is 0.54.
Wed Sep 3 22:27:43 2014 - [info] Checking recovery script configurations on the current master..
Wed Sep 3 22:27:43 2014 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data/lib/mysql --output_file=/mha/appl/save_binary_logs_test --manager_version=0.55 --start_file=mysql-bin.000004
Wed Sep 3 22:27:43 2014 - [info] Connecting to concert@192.168.66.88(192.168.66.88)..
Creating /mha/appl if not exists.. ok.
Checking output directory is accessible or not..
ok.
Binlog found at /data/lib/mysql, up to mysql-bin.000004
Wed Sep 3 22:27:43 2014 - [info] Master setting check done.
Wed Sep 3 22:27:43 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Wed Sep 3 22:27:43 2014 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='root' --slave_host=192.168.66.89 --slave_ip=192.168.66.89 --slave_port=3306 --workdir=/mha/appl --target_version=5.5.17-log --manager_version=0.55 --relay_log_info=/data/lib/mysql/relay-log.info --relay_dir=/data/lib/mysql/ --slave_pass=xxx
Wed Sep 3 22:27:43 2014 - [info] Connecting to concert@192.168.66.89(192.168.66.89:1314)..
Checking slave recovery environment settings..
Opening /data/lib/mysql/relay-log.info ... ok.
Relay log found at /data/lib/mysql, up to mysql-relay-bin.000006
Temporary relay log file is /data/lib/mysql/mysql-relay-bin.000006
Testing mysql connection and privileges.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Wed Sep 3 22:27:43 2014 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='root' --slave_host=192.168.66.120 --slave_ip=192.168.66.120 --slave_port=3307 --workdir=/mha/appl --target_version=5.5.17-log --manager_version=0.55 --relay_log_info=/data/lib/mysqlb/relay-log.info --relay_dir=/data/lib/mysqlb/ --slave_pass=xxx
Wed Sep 3 22:27:43 2014 - [info] Connecting to concert@192.168.66.120(192.168.66.120:1314)..
Checking slave recovery environment settings..
Opening /data/lib/mysqlb/relay-log.info ... ok.
Relay log found at /data/lib/mysqlb, up to mysql-relay-bin.000005
Temporary relay log file is /data/lib/mysqlb/mysql-relay-bin.000005
Testing mysql connection and privileges.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Wed Sep 3 22:27:44 2014 - [info] Slaves settings check done.
Wed Sep 3 22:27:44 2014 - [info]
192.168.66.88 (current master)
+--192.168.66.89
+--192.168.66.120

Wed Sep 3 22:27:44 2014 - [info] Checking replication health on 192.168.66.89..
Wed Sep 3 22:27:44 2014 - [info] ok.
Wed Sep 3 22:27:44 2014 - [info] Checking replication health on 192.168.66.120..
Wed Sep 3 22:27:44 2014 - [info] ok.
Wed Sep 3 22:27:44 2014 - [warning] master_ip_failover_script is not defined.
Wed Sep 3 22:27:44 2014 - [warning] shutdown_script is not defined.
Wed Sep 3 22:27:44 2014 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

OK!问题解决。

本站声明
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系admin@php.cn

热AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover

AI Clothes Remover

用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool

Undress AI Tool

免费脱衣服图片

Clothoff.io

Clothoff.io

AI脱衣机

Video Face Swap

Video Face Swap

使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热工具

记事本++7.3.1

记事本++7.3.1

好用且免费的代码编辑器

SublimeText3汉化版

SublimeText3汉化版

中文版,非常好用

禅工作室 13.0.1

禅工作室 13.0.1

功能强大的PHP集成开发环境

Dreamweaver CS6

Dreamweaver CS6

视觉化网页开发工具

SublimeText3 Mac版

SublimeText3 Mac版

神级代码编辑软件(SublimeText3)

如何用小红书号查找用户?能查到手机号吗? 如何用小红书号查找用户?能查到手机号吗? Mar 22, 2024 am 08:40 AM

随着社交媒体的迅速发展,小红书已经成为了备受青睐的社交平台之一。用户可以通过创建小红书号来展示个人身份,并与其他用户交流互动。如果你需要查找某个用户的小红书号码,可以按照以下简单步骤进行操作。一、如何用小红书号查找用户?1.打开小红书APP,点击右下角的“发现”按钮,然后选择“笔记”选项。2.在笔记列表中,找到你想查找的用户发布的那篇笔记。点击进入笔记详情页。3.在笔记详情页中,点击用户头像下方的“关注”按钮,即可进入该用户的个人主页。4.在用户个人主页右上角,点击三个点按钮,然后选择“个人信息

以超级用户身份登录Ubuntu 以超级用户身份登录Ubuntu Mar 20, 2024 am 10:55 AM

在Ubuntu系统中,root用户通常是禁用状态的。要激活root用户,可以使用passwd命令设置密码,然后使用su-命令以root身份登录。根用户是具有系统管理权限且不受限制的用户。他拥有访问和修改文件、用户管理、软件安装和删除,以及系统配置更改等权限。根用户与普通用户有着明显的区别,根用户拥有系统中最高的权限和更广泛的控制权。根用户可以执行重要的系统命令和编辑系统文件,而普通用户则无法做到这一点。在本指南中,我将探讨Ubuntu根用户,如何以根用户身份登录,以及它与普通用户的不同之处。注意

Linux系统中GDM的工作原理及配置方法 Linux系统中GDM的工作原理及配置方法 Mar 01, 2024 pm 06:36 PM

标题:Linux系统中GDM的工作原理及配置方法在Linux操作系统中,GDM(GNOMEDisplayManager)是一种常见的显示管理器,用于控制图形用户界面(GUI)登录和用户会话管理。本文将介绍GDM的工作原理和配置方法,以及提供具体的代码示例。一、GDM的工作原理GDM是GNOME桌面环境下的显示管理器,负责启动X服务器并提供登录界面,用户输

了解Linux Bashrc:功能、配置与使用方法 了解Linux Bashrc:功能、配置与使用方法 Mar 20, 2024 pm 03:30 PM

了解LinuxBashrc:功能、配置与使用方法在Linux系统中,Bashrc(BourneAgainShellruncommands)是一个非常重要的配置文件,其中包含了系统启动时自动运行的各种命令和设置。Bashrc文件通常位于用户的家目录下,是一个隐藏文件,它的作用是为用户自定义设置Bashshell的环境。一、Bashrc的功能设置环境

Windows 上的 OpenSSH:安装、配置和使用指南 Windows 上的 OpenSSH:安装、配置和使用指南 Mar 08, 2024 am 09:31 AM

对于大多数Windows用户来说,远程桌面协议(RDP)一直是远程管理的首选,因为它提供了友好的图形界面。然而,对于那些需要更精细控制的系统管理员来说,SSH更适合他们的需求。通过SSH,管理员可以通过命令行与远程设备进行交互,这样可以让管理工作更加高效。SSH的优势在于其安全性和灵活性,使得管理员能够更方便地进行远程管理和维护工作,尤其是在处理大量设备或进行自动化任务时。因此,尽管RDP在用户友好性方面表现出色,但对于系统管理员来说,SSH的功能和控制力更胜一筹。以前,Windows用户需要借

Linux系统中如何配置和安装FTPS Linux系统中如何配置和安装FTPS Mar 20, 2024 pm 02:03 PM

标题:Linux系统中如何配置和安装FTPS,需要具体代码示例在Linux系统中,FTPS是一种安全的文件传输协议,与FTP相比,FTPS通过TLS/SSL协议对传输的数据进行加密,提高了数据传输的安全性。在本文中,将介绍如何在Linux系统中配置和安装FTPS,并提供具体的代码示例。步骤一:安装vsftpd打开终端,输入以下命令安装vsftpd:sudo

Linux系统中的用户密码存储机制解析 Linux系统中的用户密码存储机制解析 Mar 20, 2024 pm 04:27 PM

Linux系统中的用户密码存储机制解析在Linux系统中,用户密码的存储是非常重要的安全机制之一。本文将解析Linux系统中用户密码的存储机制,包括密码的加密存储、密码的验证过程以及如何安全地管理用户密码。同时,将通过具体的代码示例展示密码存储的实际操作过程。一、密码的加密存储在Linux系统中,用户密码并不是以明文的形式存储在系统中,而是经过加密后保存。L

Oracle数据库:一个用户是否可以拥有多个表空间? Oracle数据库:一个用户是否可以拥有多个表空间? Mar 03, 2024 am 09:24 AM

Oracle数据库是一种常用的关系型数据库管理系统,许多用户都会遇到关于表空间的使用问题。在Oracle数据库中,一个用户可以拥有多个表空间,这样可以更好地管理数据存储和组织。本文将探讨一个用户如何在Oracle数据库中拥有多个表空间,并提供具体的代码示例。在Oracle数据库中,表空间是用来存储表、索引、视图等对象的逻辑结构。每个数据库都至少有一个表空间,

See all articles