| Description | The filedaemon does not complete its upgrade if there is already a client config file present in /etc/bareos/bareos-fd.d/client/, which has a different name than myself.conf
During the upgrade the filedaemon creates the file /etc/bareos/bareos-fd.d/client/myself.conf, regardless if there is a config there already (in our case we use ${HOSTNAME}.conf)
During the upgrade the upgrade script is trying to start bareos-fd and fails, since now there are now two config files for one and the same host, this is what the test returns:
root@server:/etc/bareos/bareos-fd.d/client # bareos-fd -t
15-May 09:11 bareos-fd: Fatal Error at filed.c:371 because:
Only one Client resource permitted in /etc/bareos/bareos-fd.d/*/.conf
15-May 09:11 hostname: ERROR in filed.c:251 Please correct configuration file: /etc/bareos/bareos-fd.d/*/.conf
Usually if you are performing an upgrade the configs should already be in place and you should not try to overwrite them or create new ones with the same purpose. There should be a prompt eventually, which config to keep, the new/default one or the old/custom one.
A similar issue was reported in https://bugs.bareos.org/view.php?id=738 |
|---|
