On Wed, 13 Apr 2011 18:45:51 -0400, "Kenney, William P. (Information
Technology Services)" <kenn...@easternct.edu> wrote:
>> -----Original Message-----
>> From: Jérôme Blion [mailto:jerome.bl...@free.fr]
>> Sent: Friday, April 08, 2011 9:55 AM
>> To: Kenney, William P. (Information Technology Services)
>> Cc: bacula-users@lists.sourceforge.net
>> Subject: RE: [Bacula-users] Connection error from remote client
> clip ................
>
>> > I have tried this address, ecsu-bk3.easternct.edu and the IP address
>> in
>> > the address field and get the same error.
>> >
>> > I have removed the internal FW's during testing and it made no
>> difference.
>> >
>> > The database contains a bacula user for all hostname addresses that I
>> have
>> > used, so that should not be a problem.
>> >
>> > Bill
>>
>> Hello,
>>
>> From the client, are the following commands working?
>> nslookup ecsu-bk3
>> telnet ecsu-bk3 9103
>>
>> Can you confirm me the Storage Daemon and the Director are on the same
>> machine?
>>
>> (I read ecsu-bk3-dir in your message)
>>
>> HTH.
>> Jerome Blion.
>
> Hi Jerome,
>
> I cleaned up the DNS server annow get only one "correct" response from
> nslookup.
>
> The Storage daemon and Director are on the same machine.
>
> I opened up "my.cnf" to allow remote access to the database.
>
> I added the FQDN and alias to the IP address in the /etc/hosts file.
>
> The local client runs just fine but I still get the error message from
the
> second "remote" client.
>
> Below is a listing of the error message and the configuration files I'm
> using:
>
>
*********************************************************************************
> This is the error message I received from the Director:
>
> You have messages.
> *messages
> 13-Apr 18:11 ecsu-bk3-dir JobId 55: Fatal error: No Job status returned
> from FD.
> 13-Apr 18:08 ecsu-bk3-dir JobId 55: Warning: bsock.c:129 Could not
connect
> to Client: beast-fd on beast.easternct.edu:9102. ERR=Connection refused
> Retrying ...
> 13-Apr 18:11 ecsu-bk3-dir JobId 55: Fatal error: bsock.c:135 Unable to
> connect to Client: beast-fd on beast.easternct.edu:9102. ERR=Connection
> refused
> 13-Apr 18:11 ecsu-bk3-dir JobId 55: Error: Bacula ecsu-bk3-dir 5.0.2
> (28Apr10): 13-Apr-2011 18:11:00
> Build OS: x86_64-pc-linux-gnu ubuntu 10.10
> JobId: 55
> Job: BackupClient2.2011-04-13_18.07.58_12
> Backup Level: Full (upgraded from Incremental)
> Client: "beast-fd" 5.0.0 (26Jan10)
> x86_64-redhat-linux-gnu,redhat,Enterprise release
> FileSet: "Full Set" 2011-04-01 11:44:48
> Pool: "File" (From Job resource)
> Catalog: "MyCatalog" (From Client resource)
> Storage: "File" (From Job resource)
> Scheduled time: 13-Apr-2011 18:07:51
> Start time: 13-Apr-2011 18:08:00
> End time: 13-Apr-2011 18:11:00
> Elapsed time: 3 mins
> Priority: 10
> FD Files Written: 0
> SD Files Written: 0
> FD Bytes Written: 0 (0 B)
> SD Bytes Written: 0 (0 B)
> Rate: 0.0 KB/s
> Software Compression: None
> VSS: no
> Encryption: no
> Accurate: no
> Volume name(s):
> Volume Session Id: 3
> Volume Session Time: 1302731375
> Last Volume Bytes: 1,774 (1.774 KB)
> Non-fatal FD errors: 0
> SD Errors: 0
> FD termination status: Error
> SD termination status: Waiting on FD
> Termination: *** Backup Error ***
>
> [...]
>
> This is the bacula-sd.conf on the backup server
>
> #
> # Default Bacula Storage Daemon Configuration file
> #
> # For Bacula release 5.0.2 (28 April 2010) -- ubuntu 10.10
> #
> # You may need to change the name of your tape drive
> # on the "Archive Device" directive in the Device
> # resource. If you change the Name and/or the
> # "Media Type" in the Device resource, please ensure
> # that dird.conf has corresponding changes.
> #
>
> Storage { # definition of myself
> Name = ecsu-bk3-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/lib/bacula"
> Pid Directory = "/var/run/bacula"
> Maximum Concurrent Jobs = 20
> #SDAddress = 127.0.0.1
> SDAddress = ecsu-bk3.easternct.edu
> }
It seems to be OK. ecsu-bk3.easternct.edu will have to be resolved on the
client.
>
> This is the bacula-dir.conf:
>
> #
> # Default Bacula Director Configuration file
> #
> # The only thing that MUST be changed is to add one or more
> # file or directory names in the Include directive of the
> # FileSet resource.
> #
> # For Bacula release 5.0.2 (28 April 2010) -- ubuntu 10.10
> #
> # You might also want to change the default email address
> # from root to your address. See the "mail" and "operator"
> # directives in the Messages resource.
> #
>
> Director { # define myself
> Name = ecsu-bk3-dir
> DIRport = 9101 # where we listen for UA connections
> QueryFile = "/etc/bacula/scripts/query.sql"
> WorkingDirectory = "/var/lib/bacula"
> PidDirectory = "/var/run/bacula"
> Maximum Concurrent Jobs = 1
> Password = "*498F6E0FC18D37B6288117511CF2B12BCC8E1A3F" #
Console
> password
> Messages = Daemon
> #DirAddress = 127.0.0.1
> DirAddress = ecsu-bk3.easternct.edu
> }
For me, that's OK too... Same notice for the DirAddress.
> Job {
> Name = "BackupClient2"
> Client = beast-fd
> JobDefs = "DefaultJob"
> }
>
> [...]
>
> #
> # Second Client (File Services) to backup
> # You should change Name, Address, and Password before using
> #
> Client {
> Name = beast-fd
> Address = beast.easternct.edu
> FDPort = 9102
> Catalog = MyCatalog
> Password = "*498F6E0FC18D37B6288117511CF2B12BCC8E1A3F" #
> password for FileDaemon 2
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
13-Apr 18:08 ecsu-bk3-dir JobId 55: Warning: bsock.c:129 Could not connect
to Client: beast-fd on beast.easternct.edu:9102. ERR=Connection refused
Connection refused means that the director was able to resolve the
hostname, and got a reply from the server (or a firewall which rejects
packets instead of dropping them)
Could you provide us the beast-fd configuration file ?
Could you check that the client is listenning on the right IP Address?
Sometimes, it can be useful to just comment (FD|SD|DIR)Address to have the
daemon to listen on any interface available.
On beast-fd client: netstat -natp | grep 9102
HTH.
Jérôme Blion.
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
