View Issue Details

IDProjectCategoryView StatusLast Update
0000948bareos-corefile daemonpublic2023-03-23 16:45
Reporteramorphis Assigned Tobruno-at-bareos  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
PlatformLinuxOSUbuntuOS Version16.04
Product Version17.2.4 
Summary0000948: Filedaemon does not upgrade if there is a config in /etc/bareos/bareos-fd.d/client/
DescriptionThe 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
Steps To Reproduce1. Setup a Linux box with Ubuntu 16.04 (most likely reproducable on other versions as well)
2. Install Bareos filedaemon 16.2.4
3. Make a custom config in /etc/bareos/bareos-fd.d/client/ with filename different than myself.conf
4. Attempt to upgrade the filedaemon to 17.2.4
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

rhillmann

rhillmann

2018-05-16 13:17

reporter   ~0003002

Last edited: 2018-05-16 13:18

see also https://github.com/Project0/puppet-bareos/issues/25
this affects bareos-dir->director and bareos-sd -> storage resource as well.

bruno-at-bareos

bruno-at-bareos

2023-03-23 16:45

developer   ~0004951

Documented, you have to keep the installed by package .conf file.
If you want to change the content, comment or empty the file, this will then no more changed by the package installation.

Issue History

Date Modified Username Field Change
2018-05-16 09:54 amorphis New Issue
2018-05-16 13:17 rhillmann Note Added: 0003002
2018-05-16 13:18 rhillmann Note Edited: 0003002
2023-03-23 16:45 bruno-at-bareos Assigned To => bruno-at-bareos
2023-03-23 16:45 bruno-at-bareos Status new => closed
2023-03-23 16:45 bruno-at-bareos Resolution open => won't fix
2023-03-23 16:45 bruno-at-bareos Note Added: 0004951