No connAuthFile configured, but it is configured

[kyleb-fm]

Describe the bug
On Ubuntu 22.04, after a fresh installation of 20:7.4.6 installed from:
deb [signed-by=/etc/apt/trusted.gpg.d/beegfs.asc] https://www.beegfs.io/release/beegfs_7.4.6 jammy non-free
I get:

beeond start -n nodefile -d /bgfs-data/bgfs -c /mnt/beegfs 

INFO: Using status information file: /var/tmp/beeond.tmp
INFO: Checking reachability of host rschhpc210
INFO: Checking reachability of host rschhpc211
INFO: Number of storage servers automatically set to 2
INFO: Starting beegfs-mgmtd processes
INFO: Management daemon log: /var/log/beegfs-mgmtd_20250320-163757.log
INFO: Starting beegfs-mgmtd on host: rschhpc210

Unrecoverable error: No connAuthFile configured. Using BeeGFS without connection authentication is considered insecure and is not recommended. If you really want or need to run BeeGFS without connection authentication, please set connDisableAuthentication to true.

ERROR: Unable to start beegfs-mgmtd on host: rschhpc210

I have created /etc/beegfs/connAuth with the correct permissions:

root@rschhpc210:/etc/beegfs# ls -l connauthfile
-r-------- 1 root root 128 Oct 17 13:39 connauthfile
root@rschhpc210:/etc/beegfs# grep connauth beegfs-mgmtd.conf
connAuthFile                           = /etc/beegfs/connauthfile

When I strace beeond, it does not appear to be reading any of the conf files in /etc/beegfs where the connauthfile is defined, nor is it reading the connauthfile itself.

Is there a way to force beeond to read the connauthfile?

Thanks,

[philippfalk]

Hello @kyleb-fm,

services started with BeeOND don't read the default configuration files in /etc/beegfs to avoid conflicts with other BeeGFS services that might run on the same machine and to ensure that the configuration is available on all nodes that are part of the BeeOND file system.

To configure BeeOND, please use the -f flag. From beeond --help:

         -f PATH     => Directory containing additional beegfs config files.
                        There can be one file for each service as well as the client.
                        They must be  named in the form beegfs-<service>.conf, where 
                        <service> can be meta, storage, mgmtd or client.
                        Only the options specified within the files are
                        set/overwritten, the rest of the defaults will not be
                        touched and still be applied. The directory and the 
                        files need to be present on every node.

In your case, I would advise to place the connAuthFile in the specified configuration directory as well and to create service configuration files for mgmtd, meta, storage and client in that directory that set connAuthFile to that file path. Then make that directory available on all nodes in your node file and the services will start with the correct configuration applied.