Title: myEMAILsignature
|
Yes, I find systemd rather non-satisfactory. One thing is if
there is no error printed, it usually means everything went well.
A "service bacula-dir status" should tell you if it is running or
not. Otherwise service bacula-dir start output gives you two
commands to use to get more detailed information. The one I use
most often is
journalctl -xe
Best regards,
Kern
On 05/14/2018 11:18 PM, Tom Plancon
wrote:
Hello,
I'm changing some configurations in my bacula-dir.conf on a
CentOS 7 server. Unfortunately it uses the new-fangled systemd
to stop and start the director. I don't get any reports as to
whether it starts or not after "systemctl start bacula-dir". In
the old days, if the director failed to start because of a
configuration error, I would get a fairly comprehensible
explanation why, down to the line number! I don see anything in
/var/log/messages. Any idea where to look for those good old
explanatory errors to see why my director refuses to start?
Thanks much!
------------------------------------------------------------------------------
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
|
------------------------------------------------------------------------------
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
