Actually, things worked once I downgraded to 1.38.6.
ZK
--- Dan Langille <[EMAIL PROTECTED]> wrote:
> On 1 May 2006 at 8:43, Zakai Kinan wrote:
>
> > I attempted to start bacula using ./bacula start
> and
> > this command gave me the error below. I installed
> the
> > client only on a redhat 9
On 1 May 2006 at 8:43, Zakai Kinan wrote:
> I attempted to start bacula using ./bacula start and
> this command gave me the error below. I installed the
> client only on a redhat 9 box and it works just fine.
> The config.log has a couple of errors as well. I
> removed the comments; thus, the t
I attempted to start bacula using ./bacula start and
this command gave me the error below. I installed the
client only on a redhat 9 box and it works just fine.
The config.log has a couple of errors as well. I
removed the comments; thus, the total size of the file
is less than 42 lines.
ZK
On 30 Apr 2006 at 15:02, Zakai Kinan wrote:
> I just installed bacula 1.38.8 on a debian sarge 3.1
> and now it will not start.
What command did you use to start it?
> I get the following error:
>
>
> zak:/etc/bacula# ./bacula start
> Starting the Bacula File daemon
> 30-Apr 17:49 bacula-fd
I just installed bacula 1.38.8 on a debian sarge 3.1
and now it will not start. I get the following error:
zak:/etc/bacula# ./bacula start
Starting the Bacula File daemon
30-Apr 17:49 bacula-fd: ERROR TERMINATION at
parse_conf.c:854
Config error: unexpected token 105 T_UNQUOTED_STRING
in resour
