Replies: 1 comment 2 replies
-
That error happens if a storage node is unable to update the management with its available target capacity (which happens periodically). That specific error typically indicates some sort of communication/network issue as you suspected. This could be BeeGFS misconfiguration, notably if connection authentication is not setup properly (or disabled fully). But in your case since the mount succeeded on node 1 it seems more likely some network/other issue happened later on. Did your management node log anything interesting? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I'm just starting with beeond, which seems to start, mounts the file system on the starting node and then gets stuck waiting for the others.
I have 32 nodes running Rocky 9.5. They can communicate with each other - I did some MPI jobs on them previously.
For beeond, I followed the docu step by step. Command line reads
beeond start -n nodefile -d /srv/beeond -c /mnt/beeond
On node 1, where I issued the
beeond start
command, the mount succeeds, giving me a 1.3T /mnt/beeond, which seems reasonable if all 32 nodes contribute.But for > 12 hours now, the start command paints dots onto the screen,
Waiting until all nodes have registered with mgmtd
None of the other nodes has beeond mounted, and there, the
/var/log/beegfs-storage_2025...log
mostly repeatsXNodeSync [XNodeSync] >> Management did not accept target free space info message.
Seems to be a basic communication issue?
Regards,
Thomas
Beta Was this translation helpful? Give feedback.
All reactions