Red Hat Bugzilla – Bug 838828
bacula services start too soon
Last modified: 2012-07-19 21:55:23 EDT
When started with systemd, the bacula services are started once network.target is reached. However, DNS name resolution may not be available at that time as local nameservers are also started once network.target is reached. The last time I rebooted my server, bacula-fd came up before DNS was available and then failed to start because it couldn't resolve the hostname it was supposed to listen on (a local intranet address - I don't want it listening on all local interfaces).
A fix for this should be to change the start-up to wait for nss-lookup.target too:
@@ -1,7 +1,7 @@
Description=Bacula-FileDaemon, a Backup-client
+Requires=syslog.target network.target nss-lookup.target
See "man systemd.special" for a description of this and other special targets.
I think it would be good to add this target for all bacula daemons.
My systems are configured for listening on all addresses or in the case of servers so slow that I never stepped into the problem. Apache does the same as well, so I think is a good idea to add it.
I think it can be added also to the next Fedora 17 update, which is currently at the same level of Rawhide.
bacula-5.2.10-2.fc17 has been submitted as an update for Fedora 17.
Please leave karma at the above link if the update is ok for you.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bacula-5.2.10-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
bacula-5.0.3-30.fc16 has been submitted as an update for Fedora 16.
bacula-5.2.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
bacula-5.0.3-30.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.