Bacula-users

Re: [Bacula-users] Director can't talk to storage daemon

2012-12-18 11:46:19
Subject: Re: [Bacula-users] Director can't talk to storage daemon
From: Jan Martin <fyzzics AT gmail DOT com>
To: bacula-users <Bacula-users AT lists.sourceforge DOT net>
Date: Tue, 18 Dec 2012 08:43:32 -0800
On 12/14/2012 10:16 AM, John Drescher wrote:
> On Fri, Dec 14, 2012 at 12:58 PM, Jan Martin <fyzzics AT gmail DOT com> wrote:
>> Hello all,
>>
>> I'm having trouble with my new bacula setup.  I had it running fine on
>> Linux Mint 13, went to Mint 14, set up the configuration files as I had
>> them set up before, and now cannot talk to the storage daemon.  Here's
>> the status from bconsole:
>>
>> *status
>> Status available for:
>>        1: Director
>>        2: Storage
>>        3: Client
>>        4: All
>> Select daemon type for status (1-4): 2
>> Automatically selected Storage: File-trinity
>> Connecting to Storage daemon File-trinity at 192.168.0.4:9103
>>
>> Failed to connect to Storage daemon File-trinity.
>>
>> When I try to run a backup, I get a bunch of messages:
>>
>> 12-Dec 03:30 trinity-dir JobId 11: shell command: run BeforeJob
>> "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog"
>> 12-Dec 03:30 trinity-dir JobId 11: Start Backup JobId 11,
>> Job=BackupCatalog.2012-12-12_03.30.00_03
>> 12-Dec 03:30 trinity-dir JobId 11: Warning: bsock.c:127 Could not
>> connect to Storage daemon on 192.168.0.4:9103. ERR=Connection refused
>> Retrying ...
>> 12-Dec 03:35 trinity-dir JobId 11: Warning: bsock.c:127 Could not
>> connect to Storage daemon on 192.168.0.4:9103. ERR=Connection refused
>> Retrying ...
>>
>>       A bunch of these, then it errors out:
>>
>> 12-Dec 04:00 trinity-dir JobId 11: Fatal error: bsock.c:133 Unable to
>> connect to Storage daemon on 192.168.0.4:9103. ERR=Connection refused
>> 12-Dec 04:00 trinity-dir JobId 11: Error: Bacula trinity-dir 5.2.6
>> (21Feb12):
>>
>>
>> bconsole connects to bacula-dir just fine, and it can talk to bacula-fd
>> just fine.  The passwords in the config files for dir and sd match, and
>> the names also match:
>> bacula-dir.conf:
>> Director {                            # define myself
>>     Name = trinity-dir
>>     DIRport = 9101                # where we listen for UA connections
>>     QueryFile = "/etc/bacula/scripts/query.sql"
>>     WorkingDirectory = "/var/lib/bacula"
>>     PidDirectory = "/run/bacula"
>>     Maximum Concurrent Jobs = 1
>>     Password = "YYYYY"         # Console password
>>     Messages = Daemon
>>     DirAddress = 127.0.0.1
>> }
>>
>>
>> # Definition of file storage device
>> Storage {
>>     Name = File-trinity
>> # Do not use "localhost" here
>>     Address = 192.168.0.4                # N.B. Use a fully qualified
>> name here
>>     SDPort = 9103
>>     Password = "XXXXX"
>>     Device = FileStorage-trinity
>>     Media Type = File1
>> }
>>
>> bacula-sd.conf:
>>
>> Storage {                             # definition of myself
>>     Name = trinity-sd
>>     SDPort = 9103                  # Director's port
>>     WorkingDirectory = "/var/lib/bacula"
>>     Pid Directory = "/run/bacula"
>>     Maximum Concurrent Jobs = 20
>>     SDAddress = 127.0.0.1
>> }
>>
>> # List Directors who are permitted to contact Storage daemon
>> #
>> Director {
>>     Name = trinity-dir
>>     Password = "XXXXX"
>> }
>>
>> Device {
>>     Name = FileStorage-trinity
>>     Media Type = File1
>>     Archive Device = /media/jmm/Backup/bacula
>>     Device Type = File
>>     LabelMedia = yes;                   # lets Bacula label unlabeled media
>>     Random Access = Yes;
>>     RemovableMedia = no;
>>     Requires Mount = no
>> }
>>
>> I am somewhat of a noob, but XXXXX is of course not actually the
>> password - but they do match!
>>
>> Does anyone here have any ideas why the director can't talk to the sd?
>> There's no firewall on this machine, ufw is inactive (this is a pretty
>> plain vanilla Mint 14 install).
>>
>> Many thanks for any and all help on this, since bacula has been my
>> primary backup method for the past several years, and has really saved
>> my butt a couple of times.
>>
> Get rid of 127.0.0.John Drescher <drescherjm AT gmail DOT com>1 and replace 
> it with an external ipaddress.
>
> John
>


Bingo!  That was the location of the problem.  I just commented out the 
SDAddress line in the storage definition, and it ran and started 
communicating with the director.  Thanks very much!

-Jan

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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>