bacula 2.2.0 fails to start, pidfile

Per olof Ljungmark peo at intersonic.se
Thu Aug 16 09:27:49 PDT 2007


[crossposting out of impatience, sorry for that]

Hi,

I just upgraded our bacula-server from 1.3.8 to version 2.2.0 using 
portupgrade.

Now bacula-dir fails to start:
Could not open pid file. /var/run/bacula-dir.9101.pid ERR=Permission denied

I assume it tries to start as the "bacula" user, but /var/run is not 
writable. Common practice seems to be to create a writable subdirectory 
instead, as in /var/run/bacula.

Anyone has a fix for this? Maybe a configuration directive would do it?

Per olof

FreeBSD 6.2-STABLE #0: Tue Jun  5
bacula-server-2.2.0


More information about the freebsd-ports mailing list