Bacula-users

[Bacula-users] Client failing to connect to Storage

2011-03-18 18:11:42
Subject: [Bacula-users] Client failing to connect to Storage
From: ryeguy146 <bacula-forum AT backupcentral DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Fri, 18 Mar 2011 14:17:34 -0700
I have a remote client (pluto.roler) that is unable to connect to the storage 
daemon (saturn.roler), complaining with the following error:

18-Mar 14:05 pluto-fd JobId 10: Warning: bsock.c:128 Could not connect to 
Storage daemon on saturn.roler:9103. ERR=Connection refused
Retrying ...
18-Mar 14:08 pluto-fd JobId 10: Fatal error: bsock.c:134 Unable to connect to 
Storage daemon on saturn.roler:9103. ERR=Connection refused
18-Mar 14:08 pluto-fd JobId 10: Fatal error: Failed to connect to Storage 
daemon: saturn.roler:9103
18-Mar 14:08 saturn-dir JobId 10: Fatal error: Bad response to Storage command: 
wanted 2000 OK storage
, got 2902 Bad storage

I have read that others had issues with DNS resolution problems, but I run a 
local BIND server, and the client (pluto-fd) running the file daemon is able to 
ping the storage daemon (saturn-sd) and director machine (saturn-dir) using the 
address specified in bacula-dir.conf for the storage daemon (saturn.roler). The 
file daemon running locally (saturn-fd) is able to complete backups perfectly. 
It may be worthwhile to note that the file daemon (pluto-fd) is of version 
5.0.3-3 while the storage daemon and director are 5.0.2. Perhaps it is possible 
that the version mismatch is causing problems, but I'd rather not rebuild 
either unless someone is quite sure that that is the source of the issue. The 
error message appears to me as if the traffic is getting through, but being 
denied for some reason. I checked passwords, and the only ones in the client's 
bacula-fd.conf match with those in the director config files. Running netstat 
on box hosting the director does indeed show the proper ports for the storage 
daemon and director to be open.

Further, tcpdump shows the traffic between the two machines, as the file daemon 
tries to connect, as follows:

13:58:59.020093 ARP, Request who-has pluto.roler tell saturn.roler, length 46
13:58:59.020113 ARP, Reply pluto.roler is-at 00:16:44:9f:c6:11 (oui Unknown), 
length 28
13:59:08.972832 IP pluto.roler.56994 > saturn.roler.domain: 46439+ AAAA? 
saturn.roler. (30)
13:59:08.974262 IP saturn.roler.domain > pluto.roler.56994: 46439* 0/1/0 (86)
13:59:08.974388 IP pluto.roler.38104 > saturn.roler.domain: 38223+ AAAA? 
saturn.roler.roler. (36)
13:59:08.975741 IP saturn.roler.domain > pluto.roler.38104: 38223 NXDomain* 
0/1/0 (99)
13:59:08.983591 IP pluto.roler.44481 > saturn.roler.domain: 54583+ A? 
saturn.roler. (30)
13:59:08.984752 IP saturn.roler.domain > pluto.roler.44481: 54583* 1/2/1 A 
192.168.0.23 (94)
13:59:08.984932 IP pluto.roler.48660 > saturn.roler.bacula-sd: Flags [S], seq 
1549214796, win 4380, options [mss 1460,sackOK,TS val 13513700 ecr 0,nop,wscale 
6], length 0
13:59:08.985867 IP saturn.roler.bacula-sd > pluto.roler.48660: Flags [R.], seq 
0, ack 1549214797, win 0, length 0

This pattern repeats for perhaps half an hour before it spits out the error 
mentioned earlier and fails. Any help resolving this would be greatly 
appreciated.

+----------------------------------------------------------------------
|This was sent by ryan.roler AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------



------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>