mmm连接失败

Question

监测服务器

日志

Network is unreachable
FATAL Network is reachable
FATAL Can't reach agent on host 'db2'
2020/01/09 14:55:11 FATAL Agent on host 'db2' is reachable again
FATAL Can't reach agent on host 'db3'
FATAL Can't reach agent on host 'db2'
FATAL Can't reach agent on host 'db1'
FATAL Agent on host 'db2' is reachable again
FATAL Agent on host 'db3' is reachable again
FATAL Agent on host 'db1' is reachable again

mmm_control show
  db1(192.168.128.131) master/HARD_OFFLINE. Roles:
  db2(192.168.128.134) master/HARD_OFFLINE. Roles:
  db3(192.168.128.132) slave/HARD_OFFLINE. Roles:

db1

1. 开启了3306,9988端口
2. 分配的三个账号在别的虚拟机都可以通过 mysql -h -u -p登录
3. ps -aux | grep 9988 没有运行的进程.

service mysql-mmm-agent status
Redirecting to /bin/systemctl status mysql-mmm-agent.service
● mysql-mmm-agent.service - MySQL MMM agent
 Loaded: loaded (/usr/lib/systemd/system/mysql-mmm-agent.service; enabled; vendor preset: disabled)
 Active: active (running) since 三 2020-01-08 01:30:12 CST; 1 day 13h ago
Process: 110158 ExecStart=/usr/sbin/mmm_agentd (code=exited, status=0/SUCCESS)
Main PID: 110161 (mmm_agentd)
 CGroup: /system.slice/mysql-mmm-agent.service
         ├─110161 mmm_agentd
         └─112822 mmm_agentd

Answer 1

sqlercn 2020-01-10 14:45:56

看报错是网络不可达，先确一下几个节点的seliunx和防火墙是不是已经都关闭了。ps -ef | grep mmm_agent进程是否存在。

• 提问者 已经快秃顶了呢 #1

  防火墙都是关闭的,进程也存在. 监测服务器需要启动mmm agent吗.

• sqlercn 回复 提问者 已经快秃顶了呢 #2

  临测服务器不用启动mmm_agent进程，在其中一个mmm_agent节点的配置文件中加入debug 1 然后再重启这个mmm_agent节点，看看是不是有错误产生。

• 提问者 已经快秃顶了呢 回复 sqlercn #3

  在db1的mmm_agent.conf添加debug 1后启动不了服务,报错

点开查看后面31条评论