MySQL MHA /usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted

MySQL MHA /usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted在公司随便找3台测试机搭个MHA,下面这个问题折腾了三天,之前没遇到过,查了OS版本发现一致,可能是不同人弄的OS吧,知道是cpan的问题就是搞不定,郁闷。。。[root@test247 ~]# ma

在公司随便找3台测试机搭个MHA,下面这个问题折腾了三天,之前没遇到过,查了OS版本发现一致,可能是不同人弄的OS吧,知道是cpan的问题就是搞不定,郁闷。。。
[root@test247 ~]# masterha_check_repl –conf=/etc/masterha/app1.cnf
Wed Dec 4 11:53:59 2019 – [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed Dec 4 11:53:59 2019 – [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed Dec 4 11:53:59 2019 – [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed Dec 4 11:53:59 2019 – [info] MHA::MasterMonitor version 0.56.
Wed Dec 4 11:54:00 2019 – [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.
Compilation failed in require at (eval 26) line 3.

at /usr/share/perl5/vendor_perl/MHA/DBHelper.pm line 205
at /usr/share/perl5/vendor_perl/MHA/Server.pm line 166
Wed Dec 4 11:54:00 2019 – [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.
Compilation failed in require at (eval 26) line 3.

at /usr/share/perl5/vendor_perl/MHA/DBHelper.pm line 205
at /usr/share/perl5/vendor_perl/MHA/Server.pm line 166
Wed Dec 4 11:54:00 2019 – [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.
Compilation failed in require at (eval 26) line 3.

at /usr/share/perl5/vendor_perl/MHA/DBHelper.pm line 205
at /usr/share/perl5/vendor_perl/MHA/Server.pm line 166
Wed Dec 4 11:54:01 2019 – [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln309] Got fatal error, stopping operations
Wed Dec 4 11:54:01 2019 – [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm line 326
Wed Dec 4 11:54:01 2019 – [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.
Wed Dec 4 11:54:01 2019 – [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

参考下面帖子发现结果还有异常
https://www.cnblogs.com/fangyuan303687320/p/9475279.html

yum install -y cpan
cpan -D DBI
# [yes—sudo]
–上面这不执行了好几分钟,输入了很多次yes
cpan DBD::mysql
还是出现下面的异常

–异常
DVEEDEN/DBD-mysql-4.050.tar.gz
/usr/bin/make — OK
Running make test
PERL_DL_NONLAZY=1 /usr/bin/perl “-MExtUtils::Command::MM” “-e” “test_harness(0, “blib/lib”, “blib/arch”)” t/*.t
t/00base.t ………………………… 1/6
# Failed test “use DBD::mysql;”
# at t/00base.t line 15.
# Tried to use “DBD::mysql”.
# Error: Can”t load “/root/.cpan/build/DBD-mysql-4.050-d0WgOf/blib/arch/auto/DBD/mysql/mysql.so” for module DBD::mysql: libmysqlclient.so.20: cannot open shared object file: No such file or directory at /usr/lib64/perl5/DynaLoader.pm line 200.
# at t/00base.t line 15
# Compilation failed in require at t/00base.t line 15.
# BEGIN failed–compilation aborted at t/00base.t line 15.
Bailout called. Further testing stopped: Unable to load DBD::mysql
FAILED–Further testing stopped: Unable to load DBD::mysql
make: *** [test_dynamic] Error 255
DVEEDEN/DBD-mysql-4.050.tar.gz
/usr/bin/make test — NOT OK
//hint// to see the cpan-testers results for installing this module, try:
reports DVEEDEN/DBD-mysql-4.050.tar.gz
Running make install
make test had returned bad status, won”t install without force

最后发现需要先执行下这个才可以,需要回答几次yes
[root@test247 ~]# cpan
cpan[1]> force install GD

Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /usr/local/lib64/perl5/auto/GD/GD.so
Installing /usr/local/lib64/perl5/auto/GD/GD.bs
Installing /usr/local/lib64/perl5/GD.pm
Installing /usr/local/lib64/perl5/auto/GD/autosplit.ix
Installing /usr/local/lib64/perl5/GD/Polygon.pm
Installing /usr/local/lib64/perl5/GD/Simple.pm
Installing /usr/local/lib64/perl5/GD/Group.pm
Installing /usr/local/lib64/perl5/GD/Image.pm
Installing /usr/local/lib64/perl5/GD/Polyline.pm
Installing /usr/local/share/man/man1/bdf2gdfont.pl.1
Installing /usr/local/share/man/man3/GD.3pm
Installing /usr/local/share/man/man3/GD::Polygon.3pm
Installing /usr/local/share/man/man3/GD::Group.3pm
Installing /usr/local/share/man/man3/GD::Simple.3pm
Installing /usr/local/share/man/man3/GD::Polyline.3pm
Installing /usr/local/share/man/man3/GD::Image.3pm
Installing /usr/local/bin/bdf2gdfont.pl
Appending installation info to /usr/lib64/perl5/perllocal.pod
RURBAN/GD-2.71.tar.gz
/usr/bin/make install — OK

cpan[2]> exit

[root@test247 ~]# cpan DBD::mysql
CPAN: Storable loaded ok (v2.20)
Going to read “/root/.cpan/Metadata”
Database was generated on Wed, 04 Dec 2019 02:29:02 GMT
Running install for module “DBD::mysql”
CPAN: YAML loaded ok (v0.70)
Running make for D/DV/DVEEDEN/DBD-mysql-4.050.tar.gz
CPAN: Digest::SHA loaded ok (v5.47)
Checksum for /root/.cpan/sources/authors/id/D/DV/DVEEDEN/DBD-mysql-4.050.tar.gz ok

For “make test” to run properly, you must ensure that the
database user “root” can connect to your MySQL server
and has the proper privileges that these tests require such
as “drop table”, “create table”, “drop procedure”, “create procedure”
as well as others.

mysql> grant all privileges on test.* to “root”@”localhost” identified by “s3kr1t”;

You can also optionally set the user to run “make test” with:

perl Makefile.PL –testuser=username

Prepending /root/.cpan/build/DBD-mysql-4.050-LtZCXU/blib/arch /root/.cpan/build/DBD-mysql-4.050-LtZCXU/blib/lib to PERL5LIB for “install”
Files found in blib/arch: installing files in blib/lib into architecture dependent library tree
Installing /usr/local/lib64/perl5/auto/DBD/mysql/mysql.so
Installing /usr/local/lib64/perl5/auto/DBD/mysql/mysql.bs
Installing /usr/local/lib64/perl5/Bundle/DBD/mysql.pm
Installing /usr/local/lib64/perl5/DBD/mysql.pm
Installing /usr/local/lib64/perl5/DBD/mysql/GetInfo.pm
Installing /usr/local/lib64/perl5/DBD/mysql/INSTALL.pod
Installing /usr/local/share/man/man3/DBD::mysql.3pm
Installing /usr/local/share/man/man3/Bundle::DBD::mysql.3pm
Installing /usr/local/share/man/man3/DBD::mysql::INSTALL.3pm
Appending installation info to /usr/lib64/perl5/perllocal.pod
DVEEDEN/DBD-mysql-4.050.tar.gz
/usr/bin/make install — OK
[root@test247 ~]#

再运行OK了
[root@test247 ~]# masterha_check_repl –conf=/etc/masterha/app1.cnf
Wed Dec 4 12:20:09 2019 – [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed Dec 4 12:20:09 2019 – [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed Dec 4 12:20:09 2019 – [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed Dec 4 12:20:09 2019 – [info] MHA::MasterMonitor version 0.56.
Wed Dec 4 12:20:10 2019 – [info] GTID failover mode = 0
Wed Dec 4 12:20:10 2019 – [info] Dead Servers:
Wed Dec 4 12:20:10 2019 – [info] Alive Servers:
Wed Dec 4 12:20:10 2019 – [info] 192.168.5.247(192.168.5.247:3306)
Wed Dec 4 12:20:10 2019 – [info] 192.168.5.93(192.168.5.93:3306)
Wed Dec 4 12:20:10 2019 – [info] 192.168.5.94(192.168.5.94:3306)
Wed Dec 4 12:20:10 2019 – [info] Alive Slaves:
Wed Dec 4 12:20:10 2019 – [info] 192.168.5.93(192.168.5.93:3306) Version=5.7.21-log (oldest major version between slaves) log-bin:enabled
Wed Dec 4 12:20:10 2019 – [info] Replicating from 192.168.5.247(192.168.5.247:3306)
Wed Dec 4 12:20:10 2019 – [info] Primary candidate for the new Master (candidate_master is set)
Wed Dec 4 12:20:10 2019 – [info] 192.168.5.94(192.168.5.94:3306) Version=5.7.21-log (oldest major version between slaves) log-bin:enabled
Wed Dec 4 12:20:10 2019 – [info] Replicating from 192.168.5.247(192.168.5.247:3306)
Wed Dec 4 12:20:10 2019 – [info] Current Alive Master: 192.168.5.247(192.168.5.247:3306)
Wed Dec 4 12:20:10 2019 – [info] Checking slave configurations..
Wed Dec 4 12:20:10 2019 – [info] Checking replication filtering settings..
Wed Dec 4 12:20:10 2019 – [info] binlog_do_db= , binlog_ignore_db=
Wed Dec 4 12:20:10 2019 – [info] Replication filtering check ok.
Wed Dec 4 12:20:10 2019 – [info] GTID (with auto-pos) is not supported
Wed Dec 4 12:20:10 2019 – [info] Starting SSH connection tests..
Wed Dec 4 12:20:12 2019 – [info] All SSH connection tests passed successfully.
Wed Dec 4 12:20:12 2019 – [info] Checking MHA Node version..
Wed Dec 4 12:20:13 2019 – [info] Version check ok.
Wed Dec 4 12:20:13 2019 – [info] Checking SSH publickey authentication settings on the current master..
Wed Dec 4 12:20:13 2019 – [info] HealthCheck: SSH to 192.168.5.247 is reachable.
Wed Dec 4 12:20:13 2019 – [info] Master MHA Node version is 0.56.
Wed Dec 4 12:20:13 2019 – [info] Checking recovery script configurations on 192.168.5.247(192.168.5.247:3306)..
Wed Dec 4 12:20:13 2019 – [info] Executing command: save_binary_logs –command=test –start_pos=4 –binlog_dir=/data/mysql/logs/bin-log –output_file=/tmp/save_binary_logs_test –manager_version=0.56 –start_file=mysql-bin.000008
Wed Dec 4 12:20:13 2019 – [info] Connecting to root@192.168.5.247(192.168.5.247:22)..
Creating /tmp if not exists.. ok.
Checking output directory is accessible or not..
ok.
Binlog found at /data/mysql/logs/bin-log, up to mysql-bin.000008
Wed Dec 4 12:20:13 2019 – [info] Binlog setting check done.
Wed Dec 4 12:20:13 2019 – [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Wed Dec 4 12:20:13 2019 – [info] Executing command : apply_diff_relay_logs –command=test –slave_user=”monitor” –slave_host=192.168.5.93 –slave_ip=192.168.5.93 –slave_port=3306 –workdir=/tmp –target_version=5.7.21-log –manager_version=0.56 –relay_log_info=/data/mysql/relay-log.info –relay_dir=/data/mysql/data/ –slave_pass=xxx
Wed Dec 4 12:20:13 2019 – [info] Connecting to root@192.168.5.93(192.168.5.93:22)..
Checking slave recovery environment settings..
Opening /data/mysql/relay-log.info … ok.
Relay log found at /data/mysql/logs/relay-log, up to relay-bin.000015
Temporary relay log file is /data/mysql/logs/relay-log/relay-bin.000015
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.
Wed Dec 4 12:20:13 2019 – [info] Executing command : apply_diff_relay_logs –command=test –slave_user=”monitor” –slave_host=192.168.5.94 –slave_ip=192.168.5.94 –slave_port=3306 –workdir=/tmp –target_version=5.7.21-log –manager_version=0.56 –relay_log_info=/data/mysql/relay-log.info –relay_dir=/data/mysql/data/ –slave_pass=xxx
Wed Dec 4 12:20:13 2019 – [info] Connecting to root@192.168.5.94(192.168.5.94:22)..
Checking slave recovery environment settings..
Opening /data/mysql/relay-log.info … ok.
Relay log found at /data/mysql/logs/relay-log, up to relay-bin.000015
Temporary relay log file is /data/mysql/logs/relay-log/relay-bin.000015
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.
Wed Dec 4 12:20:14 2019 – [info] Slaves settings check done.
Wed Dec 4 12:20:14 2019 – [info]
192.168.5.247(192.168.5.247:3306) (current master)
+–192.168.5.93(192.168.5.93:3306)
+–192.168.5.94(192.168.5.94:3306)

Wed Dec 4 12:20:14 2019 – [info] Checking replication health on 192.168.5.93..
Wed Dec 4 12:20:14 2019 – [info] ok.
Wed Dec 4 12:20:14 2019 – [info] Checking replication health on 192.168.5.94..
Wed Dec 4 12:20:14 2019 – [info] ok.
Wed Dec 4 12:20:14 2019 – [info] Checking master_ip_failover_script status:
Wed Dec 4 12:20:14 2019 – [info] /usr/local/bin/master_ip_failover –command=status –ssh_user=root –orig_master_host=192.168.5.247 –orig_master_ip=192.168.5.247 –orig_master_port=3306
Wed Dec 4 12:20:14 2019 – [info] OK.
Wed Dec 4 12:20:14 2019 – [warning] shutdown_script is not defined.
Wed Dec 4 12:20:14 2019 – [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.
[root@test247 ~]#

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 举报,一经查实,本站将立刻删除。
转载请注明出处: https://daima100.com/10600.html

(0)
上一篇 2022-12-24 22:00
下一篇 2022-12-25

相关推荐

  • DBA入职指南学习笔记3[通俗易懂]

    DBA入职指南学习笔记3[通俗易懂]1、数据库启动 加载参数文件(spfile、pfile)—->nomount状态 加载控制文件(*.ctl) —->mount状态 加载数据文件、Redo log日志文件 ——>op…

    2023-03-29
    145
  • MySQL教程90-MySQL视图是什么?[亲测有效]

    MySQL教程90-MySQL视图是什么?[亲测有效]
    MySQL 视图(View)是一种虚拟存在的表,同真实表一样,视图也由列和行构成,但视图并不实际存在于数据库中。行和列的数据来自于定义视图的查询中所使用的表…

    2023-04-05
    133
  • mysql binlog和redolog_binlog日志记录格式

    mysql binlog和redolog_binlog日志记录格式一.redo log 使用原因 原理 二.binlog(归档日志) 与redo log的区别 三.两段提交 更新过程 update T set c=c+1 where ID=2; 1. 执行器先找引擎

    2023-02-03
    124
  • mssql的text字段中文乱码

    mssql的text字段中文乱码问题: 1.在页面存入中文后乱码,从前端从后台发现数据未发生异常,发现是存入数据库后乱码; 经查询该字段为text字段,存入中文会乱码 如图 解决办法: 1.将text转为varchar或nvarch

    2022-12-18
    116
  • 腾讯金融云产品_简述金融大数据的关键技术

    腾讯金融云产品_简述金融大数据的关键技术近期,由中科软科技股份有限公司主办,以“数字保险 科技引擎”为主题的“中国财险科技应用高峰论坛”在北京古北水镇成功举办。论坛聚集400多位来自国内财险公司、国内外保险科技公司的技术专家,腾讯云数据库总

    2023-06-03
    132
  • 云三级架构_云数据中心架构

    云三级架构_云数据中心架构随着企业规模的扩大,对数据库可用性要求越来越高,更多企业采用两地三中心、异地多活的架构,以提高数据库的异常事件应对能力。 在数据库领域,我们常听的“两地三中心”、“异地多活”到底是什么呢? “两地三中

    2023-05-28
    116
  • MySQL安装——Linux「建议收藏」

    MySQL安装——Linux「建议收藏」MySQL安装——Linux MySQL下载链接:http://downloads.mysql.com/archives/community/ mysql安装(5.5) (1)查询是否安装过 #查看…

    2023-01-28
    129
  • redis的哨兵_地面哨兵

    redis的哨兵_地面哨兵[TOC] RedisSentinel哨兵 注意 若master实例故障,sentinel会重新选主并启动自动故障切换:选择slave-priority最小的那个slave实例并将其提升为maste…

    2023-02-02
    126

发表回复

您的电子邮箱地址不会被公开。 必填项已用*标注