I need a little bit of help here.

I have the following setup, Fedora 11, Bacula 3.0.3, set up and working 
with a local client (i.e.
the client runs on the same machine as bacula-dir and bacula-sd). I 
checked that bacula-dir and
bacula-sd are actually listening on port 9102/9103 on the real 
interface, not the localhost.

I have also a small NAS, bubba, with a debian sarge for arm installed, 
this has bacula version
1.36.2. Here is the status of the bubba client (called beige):

status client=beige

Connecting to Client beige at 192.168.1.3:9102

beige Version: 1.36.2 (28 February 2005) arm-unknown-linux-gnu debian 3.1

Daemon started 12-Feb-10 17:34, 0 Jobs run since started.

No Terminated Jobs.

Running Jobs:

Director connected at: 12-Feb-10 17:47

No Jobs running.

====


Which proves that bacula-dir can connect to it. Now when I start a job 
nothing happens at the
client side. If I cancel the job I get:

Automatically selected Job: JobId=33 Job=mail-backup.2010-02-12_17.34.19.04

2001 Job mail-backup.2010-02-12_17.34.19.04 marked to be canceled.

3000 Job mail-backup.2010-02-12_17.34.19.04 marked to be canceled.

12-Feb 17:34 beige: mail-backup.2010-02-12_17.34.19.04 Warning: 
bnet.c:769 Could not connect to Storage daemon on 192.168.1.40:9103. 
ERR=No route to host

Retrying ...

12-Feb 17:39 beige: mail-backup.2010-02-12_17.34.19.04 Warning: 
bnet.c:769 Could not connect to Storage daemon on 192.168.1.40:9103. 
ERR=No route to host

Retrying ...

12-Feb 17:44 beige: mail-backup.2010-02-12_17.34.19.04 Warning: 
bnet.c:769 Could not connect to Storage daemon on 192.168.1.40:9103. 
ERR=No route to host

Retrying ...

12-Feb 17:47 bacula-sd JobId 33: Job mail-backup.2010-02-12_17.34.19.04 
marked to be canceled.

12-Feb 17:47 beige: mail-backup.2010-02-12_17.34.19.04 Fatal error: 
Failed to connect to Storage daemon: 192.168.1.40:9103

12-Feb 17:47 bacula-dir JobId 33: Fatal error: Socket error on Storage 
command: ERR=No data available


Note: bacula-dir and bacula-sd are running on the machine with IP nr 
192.168.1.40,
the client has IP nr 192.168.1.3.

What is strange that the connection bacula-fd <-> bacula-dir works fine,
the connect bacula-fd <-> bacula-sd does not.

Is the because of the version difference between the client and the 
server (1.36.2 vs 3.0.3)?
Problem here is that I cannot simply update the client.

Any idea what to check here,

thanks,

Albert

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users