Fail to start bacula director with systemctl.

Erik P. Olsen epodata at gmail.com
Fri Jun 29 21:55:01 UTC 2012


When migrating to fedora 16 (from 14) I have to start bacula using systemctl. It 
works fine with the client and storage daemons but the director service fails. 
systemctl status bacula-<daemon> shows:

[root at epohost ~]# systemctl status bacula-dir.service
bacula-dir.service - Bacula-Director, the Backup-server
	  Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled)
	  Active: failed since Fri, 29 Jun 2012 23:09:35 +0200; 1min 9s ago
	 Process: 1781 ExecStart=/usr/sbin/bacula-dir -f $OPTS -c $CONFIG -u $DIR_USER 
-g $DIR_GROUP (code=exited, status=1/FAILURE)
	 Process: 1778 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, 
status=0/SUCCESS)
	  CGroup: name=systemd:/system/bacula-dir.service

[root at epohost ~]# systemctl status bacula-sd.service
bacula-sd.service - Bacula-StorageDaemon, the storage-server
	  Loaded: loaded (/lib/systemd/system/bacula-sd.service; enabled)
	  Active: active (running) since Fri, 29 Jun 2012 23:09:27 +0200; 1min 42s ago
	 Process: 1205 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, 
status=0/SUCCESS)
	Main PID: 1219 (bacula-sd)
	  CGroup: name=systemd:/system/bacula-sd.service
		  └ 1219 /usr/sbin/bacula-sd -f -c /etc/bacula/bacula-sd.co...

[root at epohost ~]# systemctl status bacula-fd.service
bacula-fd.service - Bacula-FileDaemon, a Backup-client
	  Loaded: loaded (/lib/systemd/system/bacula-fd.service; enabled)
	  Active: active (running) since Fri, 29 Jun 2012 23:09:27 +0200; 1min 55s ago
	 Process: 1196 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, 
status=0/SUCCESS)
	Main PID: 1214 (bacula-fd)
	  CGroup: name=systemd:/system/bacula-fd.service
		  └ 1214 /usr/sbin/bacula-fd -f -c /etc/bacula/bacula-fd.co...

Can somebody decipher what is wrong or perhaps suggest a way to diagnose the 
problem? Starting bacula-dir manually works fine. Maybe this is for the bacula 
community to answer but I've started here since it may a failure in the rpm package.

-- 
Erik


More information about the users mailing list