View Issue Details

IDProjectCategoryView StatusLast Update
0000952bareos-corefile daemonpublic2019-07-02 17:14
Reportertuxmaster Assigned Tojoergs  
Status confirmedResolutionopen 
PlatformX86_64OSFedoraOS Version28
Product Version17.2.5 
Summary0000952: The file daemon crash with an empty config file
DescriptionWhen the myself.conf file contains only comments, then the daemon crash on start.
Steps To Reproduce1. create an myself.conf which only contains commends.
Additional Informationbareos-fd -f -c /etc/bareos/
27-Mai 17:58 bareos-fd: Fatal Error at filed.c:359 because:
No File daemon resource defined in /etc/bareos/bareos-fd.d/*/*.conf
Without that I don't know who I am :-(
27-Mai 17:58 bareos-fd: ERROR in filed.c:251 Please correct configuration file: /etc/bareos/bareos-fd.d/*/*.conf
BAREOS interrupted by signal 11: Segmentation violation
Kaboom! bareos-fd, bareos-fd got signal 11 - Segmentation violation. Attempting traceback.
Kaboom! exepath=/root
Calling: /root/btraceback /root/bareos-fd 26155 /tmp/
execv: /root/btraceback failed: ERR=No such file or directory
The btraceback call returned 255
Dumping: /tmp//bareos-fd.26155.bactrace

Attempt to dump locks
Attempt to dump current JCRs. njcrs=0
TagsNo tags attached.




2019-07-02 17:12

developer   ~0003406

Last edited: 2019-07-02 17:14

Yes, I can reproduce that problem. It also crashes, when the myself.conf file does not exists (when no client resource is defined).

Issue History

Date Modified Username Field Change
2018-05-27 18:14 tuxmaster New Issue
2019-07-02 17:12 joergs Assigned To => joergs
2019-07-02 17:12 joergs Status new => confirmed
2019-07-02 17:12 joergs Note Added: 0003406
2019-07-02 17:13 joergs Priority normal => low
2019-07-02 17:14 joergs Note Edited: 0003406