Hello,
I posted this a while back, but i have additional information on it.
I've been having an issue about bacula since upgrading from 2.03 to
2.2.x. I'm running bacula with tls communications for all daemons. THis is
on a FreeBSD 6.x machine, all three daemons. I'm able to start the file and
storage daemons, they read the configuration files and keys fine, the
director did not. I found out via a bug report i atempted to file that the
most likely cause was the director was not being started as root. I went to
the box and manually started the director with:
bacula-dir -c /usr/local/etc/bacula-dir.conf
and it fired right up. This told me the most likely cause of the issue was
in the bacula-dir startup rc.d file and that the suggestion as starting as
root was correct. I checked /usr/local/etc/rc.d/bacula-dir and noted the
bacula_flags
line:
-u bacula -g bacula -v -c /usr/local/etc/bacula-dir.conf
when i start the director using this line i'm getting an error the
private key file can not be read. This is definitely my problem, manually
starting with only the -c option works fine. Is there a
way to correct this in the port, perhaps with a flag at installtime if one
is using tls, or is there a better way?
Thanks.
Dave.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
