You may want to try bareos -t -d 200 #where 200 is the debug level; the
higher the number the more output.
Do not be confused by the segmentation fault, this is the current
fatal-exit of the director. This can also happen on a misconfigured
config or database connection. The debug messages
P.S.
I installed bareos now on 3 different servers (new installation). 3x
the same error:
# bareos-dir -t
BAREOS interrupted by signal 11: Segmentation violation
Segmentation fault (core dumped)
Seems to be in relation with the DB, not with the files in bareos-dir.d
Can someone reproduce
Hello,
I'm trying to enable the statistics collection on 18.2.6, FreeBSD - without
success.
in dir-Director {
Statistics Collect Interval = 60
Statistics Retention = 7776000
in dir-Storage {
Collect Statistics = yes
in sd-Storage {
Collect Device Statistics = yes
Collect Job
Hello,
Can someone help me with this please?
root@diufnas26:/etc/bareos/bareos-dir.d/fileset# systemctl restart
bareos-dir
Job for bareos-director.service failed because a fatal signal was
delivered causing the control process to dump core. See "systemctl
status bareos-director.service"
