-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin
...
Here is what i get from debug on the client:
$ bacula-fd -c /etc/bacula/bacula-fd.conf -v -s -d350 -f
bacula-fd: filed_conf.c:438-0 Inserting director res: godzilla-mon
gnadmin-fd: message.c:259-0 Copy message resource 809be78 to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moray
Am 13.01.2010 um 17:56 schrieb Moray Henderson:
...
Does the password contain any characters outside the ASCII range
32-127?
If so, it might be a codepage conversion problem.
I'm afraid, no, all standard chars from a-z and 0-9. Even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
__Martin
Many thanks for your reply, i have two things here (which are quite
long):
First, another debug of baculca-fd where something diffrent in the
debug of:
(Note: Nothing changed in configuration etc... )
- ---
$ bacula-fd -f -u root -g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I do have a quite misterious and headacking problem with one of my
fresh hosts, which
i'd like to integrate with bacula.
Whatever i try or do, i cannot connect to the bacula-fd on my client,
i allways get the message below:
*
13-Jan
Simon Spring wrote:
Hi all
I do have a quite misterious and headacking problem with one of my
fresh hosts, which
i'd like to integrate with bacula.
Whatever i try or do, i cannot connect to the bacula-fd on my client,
i allways get the message below:
*
13-Jan 16:57 godzilla-dir JobId 0:
On Wed, 13 Jan 2010 17:16:21 +0100, Simon Spring said:
Hi all
I do have a quite misterious and headacking problem with one of my
fresh hosts, which
i'd like to integrate with bacula.
Whatever i try or do, i cannot connect to the bacula-fd on my client,
i allways get the message