Dear Sean,
Yes, I just figured out it is being caused by the iptable of the
bacula server running the storage daemon. Actually the problem have
been fixed by including a rule for 9103 access. Anyway, thx very much
for your help indeed.
Rgds,
Frank
On Wed, May 12, 2010 at 10:45 PM, Sean M Clark
On 2010May12 2:42 AM, frank cheong wrote:
> Dear All,
>
> I have just finished setting up bacula 5.0.2 and have no problem in
> backing up local host, while it complained the following error when I
> add a second client :-
>
> Fatal error: Failed to connect to Storage daemon: server:9103 12-May
>
On 5/12/2010 3:42 AM, frank cheong wrote:
> Dear All,
>
> I have just finished setting up bacula 5.0.2 and have no problem in
> backing up local host, while it complained the following error when I
> add a second client :-
>
> Fatal error: Failed to connect to Storage daemon: server:9103 12-May
>
Dear All,
I have just finished setting up bacula 5.0.2 and have no problem in
backing up local host, while it complained the following error when I
add a second client :-
Fatal error: Failed to connect to Storage daemon: server:9103 12-May
12:41 server-dir JobId 17: Fatal error: Bad response to S
