为提高效率,提问时请提供以下信息,问题描述清晰可优先响应。
【DM版本】:
DM Database Server x64 V8 DB Version: 0x7000c
1-3-140-2024.03.21-222308-20093-ENT
【操作系统】:
【CPU】:
【问题描述】*:
14:54 systemctl stop DmMonitor-xxx,然后 stop 掉主从节点以及 watcher
14:56 start 主从节点,然后 systemctl start DmMonitor-xxx 报错
15:19 再次systemctl start DmMonitor-xxx 成功
是不是应该在start 主从节点后,应该等主从状态正常后再 start DmMonitor?
报错日志:
[monitor] 2025-02-25 14:56:02: mfil_read_hdr_from_buf, mfil_chksum_calc failed!
[monitor] 2025-02-25 14:56:02: mfil_read_hdr_from_handle, mfil_read_hdr_from_buf failed!
[monitor] 2025-02-25 14:56:02: dmmonitor read online log file failed, please check MON_LOG_PATH in dmmonitor.ini or online log file!
√onitor] 2025-02-25 14:54:02: Resuming flush thread success!
[monitor] 2025-02-25 14:54:02: Async recover for dest 3 success
[monitor] 2025-02-25 14:54:10: dwmon tcp port vio(10) close, inst_name:GRP1_RT_01, ip:172.16.0.84, port:5436, n_fixed:0.
[monitor] 2025-02-25 14:54:10: dwmon tcp port vio(9) close, inst_name:GRP1_RT_02, ip:172.16.0.81, port:5436, n_fixed:0.
[monitor] 2025-02-25 14:54:11: dwmon tcp port vio(0) close, inst_name:, ip:172.16.0.84, port:5436, n_fixed:0.
[monitor] 2025-02-25 14:54:11: dwmon tcp port vio(0) close, inst_name:, ip:172.16.0.81, port:5436, n_fixed:0.
[monitor] 2025-02-25 14:54:11: Exit DMMONITOR!
[monitor] 2025-02-25 14:54:11: Closed by user: dmdba, IP:localhost
[monitor] 2025-02-25 14:54:12: DMMONITOR[4.0] DEINIT SUCCESS.
[monitor] 2025-02-25 14:54:12: [for dem]SYSTEM SHUTDOWN SUCCESS.
[monitor] 2025-02-25 14:56:02: mfil_read_hdr_from_buf, mfil_chksum_calc failed!
[monitor] 2025-02-25 14:56:02: mfil_read_hdr_from_handle, mfil_read_hdr_from_buf failed!
[monitor] 2025-02-25 14:56:02: dmmonitor read online log file failed, please check MON_LOG_PATH in dmmonitor.ini or online log file!
[monitor] 2025-02-25 15:19:07: DMMONITOR[4.0] IS READY.
[monitor] 2025-02-25 15:19:07: [for dem]SYSTEM IS READY.
[monitor] 2025-02-25 15:19:08: [mraft] vote start : l_term_id = 17, f_seqno = 2528, protect = 0
[monitor] 2025-02-25 15:19:08: wait mpkg flush redo over success, self_id: 1, vote_stat: CANDIDATE, l_term_id: 17
[monitor] 2025-02-25 15:19:09: [mraft] vote start : l_term_id = 18, f_seqno = 2528, protect = 0
[monitor] 2025-02-25 15:19:09: wait mpkg flush redo over success, self_id: 1, vote_stat: CANDIDATE, l_term_id: 18
[monitor] 2025-02-25 15:19:10: [mraft] vote start : l_term_id = 19, f_seqno = 2528, protect = 0
[monitor] 2025-02-25 15:19:10: wait mpkg flush redo over success, self_id: 1, vote_stat: CANDIDATE, l_term_id: 19
[monitor] 2025-02-25 15:19:11: [mraft] vote start : l_term_id = 20, f_seqno = 2528, protect = 0
[monitor] 2025-02-25 15:19:11: wait mpkg flush redo over success, self_id: 1, vote_stat: CANDIDATE, l_term_id: 20
可以按照正确的启停顺序进行测试:
启动顺序:主库实例、备库实例、主库守护进程、备库守护进程、监视器
停止顺序:监视器、备库守护进程、主库守护进程、主库实例、备库实例
检查下配置的监视器Log文件路径在dmmonitor.ini文件中是否配置正确且Log路径存在