Describe the bug
Running beegfs-fsck without a /etc/beegfs/beegfs-client.conf gives an error message:
"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."
Describe the system
BeeGFS 8.3.1
Rocky Linux 10.2
To Reproduce
Steps to reproduce the behavior:
Install BeeGFS
Rename /etc/beegfs/beegfs-client.conf to something else
Run beegfs-fsck
Expected behavior
A running beegfs-fsck instance
Log messages, error outputs
Additional context
BeeGFS supports custom beegfs-client.conf files, which can be used to mount multiple BeeGFS instances.
The individual mount configurations are managed through /etc/beegfs/beegfs-mounts.conf.
When this approach is used, a generic /etc/beegfs/beegfs-client.conf file is no longer meaningful and should ideally be removed. However, removing it prevents the use of beegfs-fsck, which still expects a standard client configuration file.
Describe the bug
Running beegfs-fsck without a /etc/beegfs/beegfs-client.conf gives an error message:
"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."
Describe the system
BeeGFS 8.3.1
Rocky Linux 10.2
To Reproduce
Steps to reproduce the behavior:
Install BeeGFS
Rename /etc/beegfs/beegfs-client.conf to something else
Run beegfs-fsck
Expected behavior
A running beegfs-fsck instance
Log messages, error outputs
Additional context
BeeGFS supports custom beegfs-client.conf files, which can be used to mount multiple BeeGFS instances.
The individual mount configurations are managed through /etc/beegfs/beegfs-mounts.conf.
When this approach is used, a generic /etc/beegfs/beegfs-client.conf file is no longer meaningful and should ideally be removed. However, removing it prevents the use of beegfs-fsck, which still expects a standard client configuration file.