Issue enabling meta data mirroring

62 views
Skip to first unread message

Usman Aslam

unread,
Dec 23, 2019, 2:09:43 AM12/23/19
to fhgfs...@googlegroups.com
We've configured a buddygroup for metadata mirroring but when trying to enable it we get the following "Invalid Argument" error message.

# beegfs-ctl --mirrormd
Operation failed on server: beegfs-mgmtd HOSTNAME [ID: 1]; Error: Invalid argument
See the server's log file for details.

I've looked through all docs but cannot find any required arguments or their syntax.
Any suggestions?

Thanks,

Usman Aslam
Senior Systems Administrator

Avigilon
A Motorola Solutions Company


Your privacy is important to us. That is why we have taken appropriate measures to ensure the data you provide to us is kept secure. To learn more about how we process your personal information, how we comply with applicable data protection laws, and care for the security and privacy of your personal data, please review our Privacy Policy. If you have any questions related to data protection and compliance with applicable laws, please contact us at our Security Operations Center at 1-302-444-9838 or mail us at: 

Attention: Privacy Compliance Program, P.O. Box 59263, Schaumburg, IL USA, 60159-0263

Ty Christensen

unread,
Feb 28, 2020, 5:03:16 PM2/28/20
to beegfs-user
I'm getting the same issue on a clean install of 7.1.4 on Cent7.  I have 2 metadata nodes online, they show Good consistency, and they are virgin.  The mgmtd log shows the metadata nodes coming online, so why does it think there aren't any metadata nodes???

(2) Feb28 13:40:43 XNodeSync [Assign node to capacity pool] >> Metadata node capacity pool assignment updated. NodeID: 1; Pool: Emergency; Reason: No capacity report received.
(2) Feb28 13:40:43 XNodeSync [Assign node to capacity pool] >> Metadata node capacity pool assignment updated. NodeID: 2; Pool: Emergency; Reason: No capacity report received.
(2) Feb28 13:40:43 Worker2 [Change consistency states] >> Metadata node is coming online. ID: 1
(2) Feb28 13:40:44 Worker2 [Change consistency states] >> Metadata node is coming online. ID: 2
(2) Feb28 13:43:43 XNodeSync [Assign node to capacity pool] >> Metadata node capacity pool assignment updated. NodeID: 1; Pool: Normal; Reason: Free capacity threshold
(2) Feb28 13:43:43 XNodeSync [Assign node to capacity pool] >> Metadata node capacity pool assignment updated. NodeID: 2; Pool: Normal; Reason: Free capacity threshold
(1) Feb28 13:47:35 Worker1 [SetMetadataMirroringMsgEx.cpp:46] >> Attempted to enable mirroring for system without metadata nodes.
(1) Feb28 13:48:50 Worker1 [SetMetadataMirroringMsgEx.cpp:46] >> Attempted to enable mirroring for system without metadata nodes.
(1) Feb28 13:48:53 Worker2 [SetMetadataMirroringMsgEx.cpp:46] >> Attempted to enable mirroring for system without metadata nodes.

Ty Christensen

unread,
Feb 28, 2020, 5:14:13 PM2/28/20
to beegfs-user
Almost forgot...yes, both metadata servers are in a buddy group.

[root@silomon ~]# beegfs-ctl --listtargets --nodetype=meta --mirrorgroups --state
MirrorGroupID MGMemberType TargetID     Reachability  Consistency   NodeID
============= ============ ========     ============  ===========   ======
            1      primary        1           Online         Good        1
            1    secondary        2           Online         Good        2
[root@silomon ~]# beegfs-ctl --listnodes --nodetype=metadata
silo6 [ID: 1]
silo5 [ID: 2]

ash...@gmail.com

unread,
May 16, 2022, 6:05:01 PMMay 16
to beegfs-user
Did you ever find the root cause of this?
Reply all
Reply to author
Forward
0 new messages