I have 3 vm hosts installed beegfs-7.4.0 :
rockynode1: beegfs-storage &
beegfs-meta & beegfs-mgmtd
rockynode2: beegfs-storage & beegfs-meta & beegfs-mgmtd
rockynode3: beegfs-storage
I have installed beegfs-mgmtd service HA by keepalived+DRBD, and meta mirror and storage mirror. All things goes well serveral days. But beegfs-meta occurs error on the host-rockynode2 today, as fllows:
[root@rockynode3 ~]# beegfs-ctl --listtargets --nodetype=meta --state
TargetID Reachability Consistency NodeID
======== ============ =========== ======
1 Online Good 1
2 Offline Good 2
[root@rockynode3 ~]#
[root@rockynode2 meta]# journalctl -u beegfs-meta -f
Apr 29 19:19:28 rockynode2 systemd[1]: Stopping BeeGFS Metadata Server...
Apr 29 19:19:30 rockynode2 systemd[1]: beegfs-meta.service: Deactivated successfully.
Apr 29 19:19:30 rockynode2 systemd[1]: Stopped BeeGFS Metadata Server.
Apr 29 19:19:30 rockynode2 systemd[1]: beegfs-meta.service: Consumed 5.261s CPU time.
Apr 29 19:19:30 rockynode2 systemd[1]: Started BeeGFS Metadata Server.
Apr 29 19:30:03 rockynode2 systemd[1]: Stopping BeeGFS Metadata Server...
Apr 29 19:30:04 rockynode2 systemd[1]: beegfs-meta.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Apr 29 19:30:04 rockynode2 systemd[1]: beegfs-meta.service: Failed with result 'exit-code'.
Apr 29 19:30:04 rockynode2 systemd[1]: Stopped BeeGFS Metadata Server.
[root@rockynode2 ~]# tail -f /var/log/beegfs-meta.log
(5) Apr29 20:11:19 RegDGramLis [RegDGramLis] >> Received a message that is invalid within the current context from: 10.254.254.143; type: RefreshTargetStates (1051)
(5) Apr29 20:11:20 RegDGramLis [RegDGramLis] >> Received a message that is invalid within the current context from: 10.254.254.145; type: RefreshTargetStates (1051)
(5) Apr29 20:11:20 RegDGramLis [RegDGramLis] >> Received a message that is invalid within the current context from: 10.254.254.143; type: RefreshTargetStates (1051)
^C
[root@rockynode2 ~]#
May I ask if all the teachers have encountered this problem before? Thank you very much