You probably have two bacula-dir.conf files on your system. The
best thing is to *always* use the -c option and specify the full
path to the conf file. That way, you can be sure which one you
are getting.
Hi folks,
Just spent several frustrating hours trying to get some special
backup configs into my bacula-dir.conf file. I'd shut down the
Director, "sytemctl stop bacula-dir", edit the file, then start
the Director, "systemctl start bacula-dir" and nothing. Did a
"bacula-dir -t" and found some syntax errors, fixed those and
then "systemctl start bacula-dir" and again - nothing. Tried
"bacula-dir -t", no errors reported! Edited the conf file and
commented out all my changes, then "systemctl start bacula-dir"
and it worked. But I did not have the config I wanted.
So piece by piece I un-commented the lines I wanted, did a
"bacula-dir -t", no errors reported. Tried to start, "systemctl
start bacula-dir", nothing. Went back and forth this way for a
long time finally commenting out again back to original file,
then "bacula-dir -t", no errors reported. Tried to start,
"systemctl start bacula-dir", nothing!
Then I rebooted the whole server - when it came up the Director
was running!!! Stopped the Director, tried adding back in some
of the config lines I wanted, did a "bacula-dir -t", no errors
reported. Tried to start, "systemctl start bacula-dir", nothing!
Again I rebooted - Director was running with my special
config!!!
Not sure what was going on, but bottom line - don't trust
systemd!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
