Backup Central

I'm testing a new bacula server, running 2.0.3 installed from the el4
rpm from sourceforge.

My client is running WinXP, with the 2.0.3 winbacula from sourceforge.

The client and the server both have each other's addresses in their
hosts files, to rule out dns issues while I'm testing. I'm using the
configs from my old server, stripped down to support just one client.

I get this error after starting a backup job:

You have messages.
*m
16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning:
../../lib/bnet.c:864 Could not connect to Storage daemon on
packrat:9103. ERR=No error
Retrying ...
*

The server just sits there like this:

Running Jobs:
JobId Level Name Status
======================================================================
5831 Differe jeff-t40.2007-03-16_21.24.41 is waiting for Client
jeff-t40-fd to connect to Storage jeff-t40-filestore
====

and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007) VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.
====

Any idea what might be going on ?

Jeff Dickens schrieb:
[snip]
*m
16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning:
../../lib/bnet.c:864 Could not connect to Storage daemon on
packrat:9103. ERR=No error
Retrying ...
*

The server just sits there like this:

Running Jobs:
JobId Level Name Status
======================================================================
5831 Differe jeff-t40.2007-03-16_21.24.41 is waiting for Client
jeff-t40-fd to connect to Storage jeff-t40-filestore
====

and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007) VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.
====

Any idea what might be going on ?

Can you reach the bacula-sd on port 9102 from your client?

Ralf

Attachments: Message as HTML

Ralf Gross wrote:
Jeff Dickens schrieb:
[snip]

*m
16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning:
../../lib/bnet.c:864 Could not connect to Storage daemon on
packrat:9103. ERR=No error
Retrying ...
*

The server just sits there like this:

Running Jobs:
JobId Level Name Status
======================================================================
5831 Differe jeff-t40.2007-03-16_21.24.41 is waiting for Client
jeff-t40-fd to connect to Storage jeff-t40-filestore
====

and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007) VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.
====

Any idea what might be going on ?


Can you reach the bacula-sd on port 9102 from your client?


I figured it out. It was a firewall issue on the server. Thanks for
pointing me in the right direction.

It would be nice if I had had something other than "ERR: No error" to
go on.

On Saturday 17 March 2007 02:29, Jeff Dickens wrote:
I'm testing a new bacula server, running 2.0.3 installed from the el4
rpm from sourceforge.

My client is running WinXP, with the 2.0.3 winbacula from sourceforge.

The client and the server both have each other's addresses in their
hosts files, to rule out dns issues while I'm testing. I'm using the
configs from my old server, stripped down to support just one client.

I get this error after starting a backup job:

You have messages.
*m
16-Mar 21:25 jeff-t40-fd: jeff-t40.2007-03-16_21.24.41 Warning:
../../lib/bnet.c:864 Could not connect to Storage daemon on
packrat:9103. ERR=No error
Retrying ...

Unfortunately, the error message here is probably incorrect because at that
low level, it doesn't know about Win32. As a consequence, it is most likely
that packrat is not properly defined on jeff-t40-fd.

It would be a big help to Win32 users if you would file a bug report with the
above message and something like "Incorrect Win32 network error message" as
the title.

*

The server just sits there like this:

Running Jobs:
JobId Level Name Status
======================================================================
5831 Differe jeff-t40.2007-03-16_21.24.41 is waiting for Client
jeff-t40-fd to connect to Storage jeff-t40-filestore
====

and the client like this:

jeff-t40-fd Version: 2.0.3 (06 March 2007) VSS Linux Cross-compile Win32
Daemon started 16-Mar-07 20:32, 0 Jobs run since started.
Heap: bytes=19,076 max_bytes=20,872 bufs=83 max_bufs=94
Sizeof: boffset_t=8 size_t=4 debug=0 trace=1

Running Jobs:
JobId 5831 Job jeff-t40.2007-03-16_21.24.41 is running.
System or Console Job started: 16-Mar-07 21:24
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDSocket closed.
====

Any idea what might be going on ?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

Unfortunately, the error message here is probably incorrect because at that
low level, it doesn't know about Win32. As a consequence, it is most likely
that packrat is not properly defined on jeff-t40-fd.


Ahhh so different socket API errors for TCP sockets? Different
firewalls return (or don't return) different TCP and ICMP packets in
response to SYN packets that violate policies.

Cisco doesn't give you a lot of control; pf(4) / ipf(4) does etc.

~BAS

It would be a big help to Win32 users if you would file a bug report with the
above message and something like "Incorrect Win32 network error message" as
the title.

IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.