Bacula-users

Re: [Bacula-users] Director will not connect to a remote client

2016-03-10 03:04:05
Subject: Re: [Bacula-users] Director will not connect to a remote client
From: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
To: "Bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 10 Mar 2016 08:57:42 +0100
Hello,

On Thu, Mar 10, 2016 at 1:56 AM, maaf4d <bacula-forum AT backupcentral DOT com> wrote:
Wanderlei,

Here is the fd config file of the remote machine:
________________________________________________________________________________
Director {
Name = backup-master-001.novalocal-dir
Password = "7m1XU9Fp9uJcd76hCpoTIHLPoX3nK8veS"
}
Director {
Name = backup-master-001.novalocal-mon
Password = "YgYu3gMvctN1ZtwtTrHUZ84JB0-u0JUNf"
Monitor = yes
}
FileDaemon { # this is me
Name = test-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
FDAddress = 128.104.223.157
}
Messages {
Name = Standard
director = backup-master-001.novalocal-dir = all, !skipped, !restored
}
_________________________________________________________________


When I try to use netstat on the client machine, it gives no output for any of the ports.

​This means that your client daemon is not running/listening to connections on the client machine. Have you issued a "bacula status" on the client machine for checking whether client daemon is running or not? Could you try to start the file daemon with "-d 200" command line option and check for error messages?


On the server, it only give an output for 9102 and here it is:

tcp        0      0 127.0.0.1:9102          0.0.0.0:*               LISTEN




Ana,

I did change the IP address in bconsole and I still can't connect to it. I believe the previous reply to Wanderlei answers the other question. I also tried the command you suggested for testing the connection and it is not connection.

​Are the DirAddress the same for director in bacula-dir.conf and bconsole.conf? Have you checked with "bacula status" whether the director daemon is running (based on the fact that a netstat on the server only gives you a listening on 9102, I suppose the director daemon is not running because ​you should have an entry for 9101)?

​Best regards,
Ana​

 


Again, I really appreciate the help

+----------------------------------------------------------------------
|This was sent by maaf4d AT mst DOT edu via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------



------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
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>