[Bacula-users] Director will not connect to a remote client
Oh, finally! We're getting somewhere. So, after I took out the addresses lines, everything is working fine. Next step for me is to get things working on CloudLab. Thank you all for your help. I think I can figure out the OpenStack issue on my own from here. Thank you guys so much! -Marty +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
> Date: Monday, March 14, 2016 15:27:47 -0700
> From: maaf4d
>
> I am using the public IP address of the machines like so:
>
> Storage { # definition of myself
> Name = storage-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/lib/bacula"
> Pid Directory = "/var/run/bacula"
> Maximum Concurrent Jobs = 20
> SDAddress = public.ip.address.xx
> }
>
You should double check that you don't have 127.0.0.1 or localhost
specified anywhere in your configurations. About the only way you are
going to get netstat output like:
tcp 0 0 127.0.1.1:9101 0.0.0.0:* LISTEN 6591/bacula-dir
tcp 0 0 127.0.1.1:9102 0.0.0.0:* LISTEN 1886/bacula-fd
tcp 0 0 127.0.1.1:9103 0.0.0.0:* LISTEN 1865/bacula-sd
is if you are specifying the localhost name or ipnumber.
Also, that "xxAddress" line is optional and, as the documentation
indicates, it should bind to all addresses if nothing is specified.
Try dropping that line.
[by the way, could you please reply with context. it is very hard to
reply to your messages from the mailing list side when they don't
carry any of the thread.]
--
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=278785231&iu=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello
You said that is running in a cloud lab.
I suggest you first learn how to configure in a local machine/local network
and after that try in a cloud lab.
There no secret how to configure bacula, but first you need to know how
bacula works.
Atenciosamente
*Wanderlei Hüttel*
http://www.huttel.com.br
2016-03-14 19:27 GMT-03:00 maaf4d :
> I am using the public IP address of the machines like so:
>
> Storage { # definition of myself
> Name = storage-sd
> SDPort = 9103 # Director's port
> WorkingDirectory = "/var/lib/bacula"
> Pid Directory = "/var/run/bacula"
> Maximum Concurrent Jobs = 20
> SDAddress = public.ip.address.xx
> }
>
> +--
> |This was sent by maa...@mst.edu via Backup Central.
> |Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.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=278785231&iu=/4140___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
On 03/14/2016 05:27 PM, maaf4d wrote: > I am using the public IP address of the machines like so: ... > SDAddress = public.ip.address.xx > } Mine works fine without that line. What does 'ip a' say on the sd machine, does it actually have 'inet public.ip.address.xx'? Also 'ip route': is there route to public.ip.net/mask? -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- 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=278785231&iu=/4140___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
I am using the public IP address of the machines like so:
Storage { # definition of myself
Name = storage-sd
SDPort = 9103 # Director's port
WorkingDirectory = "/var/lib/bacula"
Pid Directory = "/var/run/bacula"
Maximum Concurrent Jobs = 20
SDAddress = public.ip.address.xx
}
+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
This is actually not OpenStack anymore. I'm running a temporary experiment on a few Linux machines I got in the lab +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
> Date: Monday, March 14, 2016 17:00:51 -0500
> From: Dimitri Maziuk
>
> On 03/14/2016 04:45 PM, maaf4d wrote:
>> How would I change that? Maybe that is my issue
>
> Sorry. I played with OpenStack a year or so ago and decided it
> wasn't worth my time. So I've no idea, all I can tell you is 127/8
> is the loopback address as defined in RFC1122 and will not be
> routed outside localhost.
Are you specifying an IPnumber on the "address" directives? E.g.,
SDAddresses = { ip = {
addr = 127.0.0.1; port = 9103; }
}
If so, and you're using "127.0.0.1", then it will only listen in the
internal interface, not the external, which is what your netstat is
showing. I believe that there are options for this for all the
daemons.
from the current documentation:
SDAddress = This directive is optional, and if it is
specified, it will cause the Storage daemon server (for Director and
File daemon connections) to bind to the specified IP-Address, which
is either a domain name or an IP address specified as a dotted
quadruple. If this directive is not specified, the Storage daemon
will bind to any available address (the default).
--
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=278785231&iu=/4140
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
On 03/14/2016 04:45 PM, maaf4d wrote: > How would I change that? Maybe that is my issue Sorry. I played with OpenStack a year or so ago and decided it wasn't worth my time. So I've no idea, all I can tell you is 127/8 is the loopback address as defined in RFC1122 and will not be routed outside localhost. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- 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=278785231&iu=/4140___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
How would I change that? Maybe that is my issue +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
On 03/14/2016 04:30 PM, maaf4d wrote: > I get the following when I use netstat: > > tcp0 0 127.0.1.1:9101 0.0.0.0:* LISTEN > 6591/bacula-dir > tcp0 0 127.0.1.1:9102 0.0.0.0:* LISTEN > 1886/bacula-fd > tcp0 0 127.0.1.1:9103 0.0.0.0:* LISTEN > 1865/bacula-sd > > > It seems to me like it's listening to the correct ports yet it still refuses > the connection Are you connecting from(/to) localhost? 'cause that's what 127.0.1.1 is. If it's not just localhost then this is what you want to see: tcp 0 0 0.0.0.0:bacula-dir 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:bacula-fd 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:bacula-sd 0.0.0.0:* LISTEN -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- 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=278785231&iu=/4140___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
I get the following when I use netstat: tcp0 0 127.0.1.1:9101 0.0.0.0:* LISTEN 6591/bacula-dir tcp0 0 127.0.1.1:9102 0.0.0.0:* LISTEN 1886/bacula-fd tcp0 0 127.0.1.1:9103 0.0.0.0:* LISTEN 1865/bacula-sd It seems to me like it's listening to the correct ports yet it still refuses the connection +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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=278785231&iu=/4140 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
> Date: Sunday, March 13, 2016 11:41:40 -0700 > From: maaf4d > > Ok so there seems to be some kind of issue with the public IP > addresses of OpenStack to where I can't really use the IP addresses > to connect to the nodes even tough I can ssh to them. It's very > weird. > > Anyway, I tried to install Bacula on some of the machines on my > lab. I made one machine the server, and another one a client. I > opened the ports and made sure that they're listening on the right > ports. Although, I cannot get the machines to connect. When I use > telnet, I get a connection refused message. I can ping the machines > just fine. > A "connection refused" response to a telnet generally means that the target machine isn't listening on the port you tried. Use netstat to make certain that the daemon is listening on the external interface for the port(s) you are trying. If you reach a listening daemon, but there are access control issues, you'll likely get a different response. -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
Ok so there seems to be some kind of issue with the public IP addresses of OpenStack to where I can't really use the IP addresses to connect to the nodes even tough I can ssh to them. It's very weird. Anyway, I tried to install Bacula on some of the machines on my lab. I made one machine the server, and another one a client. I opened the ports and made sure that they're listening on the right ports. Although, I cannot get the machines to connect. When I use telnet, I get a connection refused message. I can ping the machines just fine. I really appreciate all the help. +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
I noticed than whenever I change any address in [bacula-dir.conf, bacula-sd.conf, bacula-fd.com] from localhost to a public IP address, the machine stops listening on the matching port. This is the weirdest thing. +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
Maybe it's worth mentioning that I am setting up a network on a CloudLab infrastructure which has OpenStack installed on it. I then create two machines on OpenStack and install Bacula on them. My ultimate goal is to create a cluster (or a cloud) which would serve as the Bacula server and use machines not on the same network as clients to run backup jobs to observe some metrics for my research. I don't know if that helps with this problem or not but I thought it was worth mentioning. +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
I removed the output rules from iptables and nothing changed. Telnet stills "hangs" and after a while it times out +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
> Date: Thursday, March 10, 2016 09:05:43 -0800 > From: maaf4d > > IPTables on Server: > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW tcp dpts:bacula-dir:bacula-sd > > Client's IPTables rules: > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:bacula-fd I think that your iptables output policies are a part of your problem. A machine's output policy constrains what ports the source side can go out from. With bacula you are going *to* ports 9101-03, but *from* an arbitrary (high numbered) port. So, while you may want to constrain that ports you accept inbound (input) connections on, you generally leave the outbound (output) totally open. In your case, you appear to be constraining your outbound ports to 9101 and 03 on your server and 9102 on the client. That, in fact, means that you very likely aren't getting out at all. Remove those outbound constraints from iptables and things should improve. I think you still have other issues, but you should be able to telnet to the 9101-03 ports (as appropriate) and get at least a "connection refused" response from the remote host. -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
Running bconsole on the local machine which has the director installed on it +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Are you trying to connect bconsole in local machine ( bacula-dir server ) or in a machine of local network or in a machine over the internet? Atenciosamente *Nome **|* *Wanderlei Hüttel* *Blog de Tecnologia* | http://www.huttel.com.br 2016-03-10 15:17 GMT-03:00 maaf4d : > After I removed DirAddress from Bacula-dir.conf: > > 1) bconsole still won't connect to the director (the public IP address is > being used in bconsole.conf.) It times out after while > 2) I get the following when i run netstat now > > tcp 0 0 0.0.0.0:9101 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:91020.0.0.0:* LISTEN > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
After I removed DirAddress from Bacula-dir.conf: 1) bconsole still won't connect to the director (the public IP address is being used in bconsole.conf.) It times out after while 2) I get the following when i run netstat now tcp 0 0 0.0.0.0:9101 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:91020.0.0.0:* LISTEN +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello - try to remove DirAddress from Director in bacula-dir.conf - in bconsole.conf, use the network address(not localhost) - check if there some error in bacula confs (bacula-dir -t), if not restart bacula. - netstat -na | grep 910[123] on bacula server. Atenciosamente *Nome **|* *Wanderlei Hüttel* http://www.huttel.com.br 2016-03-10 14:05 GMT-03:00 maaf4d : > IPTables on Server: > > _ > Chain INPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpts:bacula-dir:bacula-sd > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpts:bacula-dir:bacula-sd > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpts:bacula-dir:bacula-sd > > > > > > > > > Client's IPTables rules: > __ > Chain INPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:bacula-fd > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:bacula-fd > __ > > > > > > Client Machine's file daemon debug: > > __ > bacula-fd: filed_conf.c:452-0 Inserting director res: client-mon > 10-Mar 16:48 client-fd: ERROR TERMINATION at bsys.c:438 > bacula-fd is already running. pid=11903 > Check file /var/run/bacula/bacula-fd.9102.pid > __ > > > > > Server's director debug: > > ___ > bacula-dir: dird.c:185-0 Debug level = 200 > bacula-dir: runscript.c:296-0 runscript: debug > bacula-dir: runscript.c:297-0 --> RunScript > bacula-dir: runscript.c:298-0 --> Command=/etc/bacula/scripts/ > make_catalog_backup.pl MyCatalog > bacula-dir: runscript.c:299-0 --> Target= > bacula-dir: runscript.c:300-0 --> RunOnSuccess=1 > bacula-dir: runscript.c:301-0 --> RunOnFailure=0 > bacula-dir: runscript.c:302-0 --> FailJobOnError=1 > bacula-dir: runscript.c:303-0 --> RunWhen=2 > bacula-dir: runscript.c:296-0 runscript: debug > bacula-dir: runscript.c:297-0 --> RunScript > bacula-dir: runscript.c:298-0 --> > Command=/etc/bacula/scripts/delete_catalog_backup > bacula-dir: runscript.c:299-0 --> Target= > bacula-dir: runscript.c:300-0 --> RunOnSuccess=1 > bacula-dir: runscript.c:301-0 --> RunOnFailure=0 > bacula-dir: runscript.c:302-0 --> FailJobOnError=1 > bacula-dir: runscript.c:303-0 --> RunWhen=1 > 10-Mar 16:49 bacula-dir: ERROR TERMINATION at bsys.c:438 > bacula-dir is already running. pid=13270 > Check file /var/run/bacula/bacula-dir.9101.pid > > > > > > > > server's storage daemon debug: > > _ > bacula-sd: stored_conf.c:704-0 Inserting director res: server-mon > 10-Mar 16:50 server-sd: ERROR TERMINATION at bsys.c:438 > bacula-sd is already running. pid=13189 > Check file /var/run/bacula/bacula-sd.9103.pid > __ > > > > > Server's Netstat: > __ > root@server:~# netstat -na | grep 910[123] > tcp0 0 127.0.0.1:9102 0.0.0.0:* LISTEN > __ > > > > Client's netstat: > > root@client:~# netstat -na | grep 910[123] > > > > > Server's telnet: > ___ > root@server:~# telnet 128.104.223.157 9102 > Trying 128.104.223.157... > ___ > > > > So the issue for now is that bconsole is not connecting to the director > after I change the local address to the public IP address. The IP addresses > in bconsole and bacula-dir config files do match. The other issue is the > clients are not connecting to the director. It looks to me like the ports > are open but the machines are not listening to the correct ports. > > +-- > |This was sent by maa...@mst.edu via
[Bacula-users] Director will not connect to a remote client
IPTables on Server: _ Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere state NEW tcp dpts:bacula-dir:bacula-sd ACCEPT tcp -- anywhere anywhere state NEW tcp dpts:bacula-dir:bacula-sd Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere state NEW tcp dpts:bacula-dir:bacula-sd Client's IPTables rules: __ Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:bacula-fd Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:bacula-fd __ Client Machine's file daemon debug: __ bacula-fd: filed_conf.c:452-0 Inserting director res: client-mon 10-Mar 16:48 client-fd: ERROR TERMINATION at bsys.c:438 bacula-fd is already running. pid=11903 Check file /var/run/bacula/bacula-fd.9102.pid __ Server's director debug: ___ bacula-dir: dird.c:185-0 Debug level = 200 bacula-dir: runscript.c:296-0 runscript: debug bacula-dir: runscript.c:297-0 --> RunScript bacula-dir: runscript.c:298-0 --> Command=/etc/bacula/scripts/make_catalog_backup.pl MyCatalog bacula-dir: runscript.c:299-0 --> Target= bacula-dir: runscript.c:300-0 --> RunOnSuccess=1 bacula-dir: runscript.c:301-0 --> RunOnFailure=0 bacula-dir: runscript.c:302-0 --> FailJobOnError=1 bacula-dir: runscript.c:303-0 --> RunWhen=2 bacula-dir: runscript.c:296-0 runscript: debug bacula-dir: runscript.c:297-0 --> RunScript bacula-dir: runscript.c:298-0 --> Command=/etc/bacula/scripts/delete_catalog_backup bacula-dir: runscript.c:299-0 --> Target= bacula-dir: runscript.c:300-0 --> RunOnSuccess=1 bacula-dir: runscript.c:301-0 --> RunOnFailure=0 bacula-dir: runscript.c:302-0 --> FailJobOnError=1 bacula-dir: runscript.c:303-0 --> RunWhen=1 10-Mar 16:49 bacula-dir: ERROR TERMINATION at bsys.c:438 bacula-dir is already running. pid=13270 Check file /var/run/bacula/bacula-dir.9101.pid server's storage daemon debug: _ bacula-sd: stored_conf.c:704-0 Inserting director res: server-mon 10-Mar 16:50 server-sd: ERROR TERMINATION at bsys.c:438 bacula-sd is already running. pid=13189 Check file /var/run/bacula/bacula-sd.9103.pid __ Server's Netstat: __ root@server:~# netstat -na | grep 910[123] tcp0 0 127.0.0.1:9102 0.0.0.0:* LISTEN __ Client's netstat: root@client:~# netstat -na | grep 910[123] Server's telnet: ___ root@server:~# telnet 128.104.223.157 9102 Trying 128.104.223.157... ___ So the issue for now is that bconsole is not connecting to the director after I change the local address to the public IP address. The IP addresses in bconsole and bacula-dir config files do match. The other issue is the clients are not connecting to the director. It looks to me like the ports are open but the machines are not listening to the correct ports. +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ba
Re: [Bacula-users] Director will not connect to a remote client
Hello,
On Thu, Mar 10, 2016 at 1:56 AM, maaf4d
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:
>
> tcp0 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 maa...@mst.edu via Backup Central.
> |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hi, you keep saying you "forwarded" the ports. I don't think that that is the correct way to use the firewall rules, unless you are trying to create a new terminology or are confused. The ports, per the firewall doc, need to be open. In my setup I use iptables rules to open the specific ports for the specific directors and their ports and/or clients for their ports. Looks something like this on the client side: ACCEPT tcp -- anywhere directorname.mydomain.ext tcp dpt:bacula-sd ACCEPT tcp -- directorname.mydomain.extanywheretcp dpt:bacula-fd And like this on the director side: ACCEPT tcp -- clientname.mydomain.ext anywheretcp dpt:bacula-sd So there are no FORWARDING statements in that configuration, I would consider this, test the telnet statements that folk have posted, that should point in the right direction. On 3/9/2016 6:17 PM, maaf4d wrote: > I do get a network "hang." Although, this does not make any sense to me > because I forwarded the ports needed for Bacula. Am i doing something wrong > here? Is there anyway I can check if my firewall is blocking the connection? > > Thanks for pointing out that the passwords are included in here. I didn't > even think about that. I will make sure not include them from now on. > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
I do get a network "hang." Although, this does not make any sense to me because I forwarded the ports needed for Bacula. Am i doing something wrong here? Is there anyway I can check if my firewall is blocking the connection? Thanks for pointing out that the passwords are included in here. I didn't even think about that. I will make sure not include them from now on. +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
> Date: Wednesday, March 09, 2016 16:56:14 -0800 > From: maaf4d > > 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. When you try to telnet from the backup server to port 9102 on the client machine what type of response do you get? If you get a network "hang", then the issue is most likely a firewall. If the machine is on the same network segment the firewall is probably on the target machine. If the machine is on a different network segment the firewall could be at any router between the two machines (but I'd start with the target machine). If you reach the machine but it's not listening on 9102 you'll probably get a "connection refused" response. You might also get a connection that opens and then immediately closes, or some other permutation, which generally indicates some type of configuration or access issue on the target machine. By the way, if the passwords you have been including in your configuration outputs are the real ones, you should change them on the machines in question, and be certain to not include them in your posts ongoing. -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
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.
On the server, it only give an output for 9102 and here it is:
tcp0 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.
Again, I really appreciate the help
+--
|This was sent by maa...@mst.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello, Forgot to mention that you can always test connections to IP/ports between all your hosts/daemons using telnet. For example, from your director: telnet 128.104.223.157 9102. I´m not sure if you have already tried this. Make sure this is working between all your director, clients, storages hosts. This is really important to be sure that you do not have a firewall issue. Best regards, Ana On Wed, Mar 9, 2016 at 11:01 AM, Ana Emília M. Arruda < emiliaarr...@gmail.com> wrote: > Hello, > > If you change the DirAddress for the director in bacula-dir.conf to the > public IP address, then you need to change it also in bconsole.conf. > Because this is the address that your bconsole will use to connect to your > director daemon. > > Have you checked if your clients are listening for connections on the IP > address (port 9102) configured? > > Best regards, > Ana > > > > On Wed, Mar 9, 2016 at 6:24 AM, maaf4d > wrote: > >> Florian, >> >> All my machines can ping each other now but the issue is still not >> resolved. I also went through all your suggestions and made sure everything >> is okay. Still nothing. >> >> Randy, >> >> my ports are forwarded through the firewall but I still can't connect to >> the clients. >> >> Jari, >> >> When I change the director address to the public IP address, I can't >> connect to the director at all >> >> This is driving me insane lol >> >> +-- >> |This was sent by maa...@mst.edu via Backup Central. >> |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello, If you change the DirAddress for the director in bacula-dir.conf to the public IP address, then you need to change it also in bconsole.conf. Because this is the address that your bconsole will use to connect to your director daemon. Have you checked if your clients are listening for connections on the IP address (port 9102) configured? Best regards, Ana On Wed, Mar 9, 2016 at 6:24 AM, maaf4d wrote: > Florian, > > All my machines can ping each other now but the issue is still not > resolved. I also went through all your suggestions and made sure everything > is okay. Still nothing. > > Randy, > > my ports are forwarded through the firewall but I still can't connect to > the clients. > > Jari, > > When I change the director address to the public IP address, I can't > connect to the director at all > > This is driving me insane lol > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello -Please, post the config of bacula-fd.conf (client config in remote machine, not in bacula-dir) and -Change your dir address to the real IP not localhost (need restart bacula). -Send output of command: netstat -na | grep 910[123] Best Regards Wanderlei Hüttel Enviado de Motorola Moto X2 Em 9 de mar de 2016 2:29 AM, "maaf4d" escreveu: > Florian, > > All my machines can ping each other now but the issue is still not > resolved. I also went through all your suggestions and made sure everything > is okay. Still nothing. > > Randy, > > my ports are forwarded through the firewall but I still can't connect to > the clients. > > Jari, > > When I change the director address to the public IP address, I can't > connect to the director at all > > This is driving me insane lol > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
Florian, All my machines can ping each other now but the issue is still not resolved. I also went through all your suggestions and made sure everything is okay. Still nothing. Randy, my ports are forwarded through the firewall but I still can't connect to the clients. Jari, When I change the director address to the public IP address, I can't connect to the director at all This is driving me insane lol +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
maaf4d kirjoitti 1.3.2016 23:23:
> Hi,
> I would like some help with thi issue where the director cannot
> connect to either one of my file daemons. I installed the client
> version of bacula on a linux computer and a windows computer and
> configured them along with the director so they would communicate and
> run a backup job. Although when i go into the console and check the
> status of my clients, the connection is never successful. It ends up
> telling me that the connection timed out. Could anyone tell me what I
> am doing wrong? Here is my configurations:
> Server:
> Director File:
>
> Director { # define myself
> Name = backup-master-001.novalocal-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 = "f6nJvHpItEmcJ4m7J-WYSJzxdK9S2BGo6" # Console password
> Messages = Daemon
> DirAddress = 127.0.0.1
> }
dir is listening only for the localhost. Ok, that is OK I guess, unless
you need to connect to it using bconsole or such from remote.
But is the fd listening proper cp interface, or localhost too? That is
important.
br. jarif
--
jarif.bit
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
sorry, here it is in the current manual though nothing has changed: http://www.bacula.org/7.4.x-manuals/en/problems/Dealing_with_Firewalls.html On 3/4/2016 11:25 AM, maaf4d wrote: > So I made sure that everything was running and it still didn't work. Then, I > tried to ping the machines and it turns out that the server can ping the > clients but not the other way around. I have no idea why that is the case > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- > > > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Does this address your issue? http://www.bacula.org/5.0.x-manuals/en/problems/problems/Dealing_with_Firewalls.html On 3/4/2016 11:25 AM, maaf4d wrote: > So I made sure that everything was running and it still didn't work. Then, I > tried to ping the machines and it turns out that the server can ping the > clients but not the other way around. I have no idea why that is the case > > +-- > |This was sent by maa...@mst.edu via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- > > > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Director will not connect to a remote client
So I made sure that everything was running and it still didn't work. Then, I tried to ping the machines and it turns out that the server can ping the clients but not the other way around. I have no idea why that is the case +-- |This was sent by maa...@mst.edu via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Director will not connect to a remote client
Hello.
Some question to maybe pinpoint the issue as the config seems fine (to
me at least):
Is the director installed on a machine seperate to the clients?
Are the file daemon services definitely running?
Are the ports bacula uses open (9101, 9102)?
Are you able to ping the remote clients with the bacula user? (from the
machine the director is located on)
If yes: can your clients ping the the director machine, too? (I remember
having struggled a bit with permissions at the beginning)
I am no expert, but I hope these questions help you get an idea where
the problem may be.
Regards,
Florian S.
Am 01.03.2016 um 22:23 schrieb maaf4d:
> Hi,
> I would like some help with thi issue where the director cannot connect to
> either one of my file daemons. I installed the client version of bacula on a
> linux computer and a windows computer and configured them along with the
> director so they would communicate and run a backup job. Although when i go
> into the console and check the status of my clients, the connection is never
> successful. It ends up telling me that the connection timed out. Could anyone
> tell me what I am doing wrong? Here is my configurations:
> Server:
> Director File:
>
> Director { # define myself
> Name = backup-master-001.novalocal-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 = "f6nJvHpItEmcJ4m7J-WYSJzxdK9S2BGo6" # Console password
> Messages = Daemon
> DirAddress = 127.0.0.1
> }
> JobDefs {
> Name = "DefaultJob"
> Type = Backup
> Level = Incremental
> Client = backup-master-001.novalocal-fd
> FileSet = "Full Set"
> Schedule = "WeeklyCycle"
> Storage = File
> Messages = Standard
> Pool = File
> Priority = 10
> Write Bootstrap = "/var/lib/bacula/%c.bsr"
> }
> Job {
> Name = "LocalBackup"
> JobDefs = "DefaultJob"
> }
> Job {
> Name = "RemoteBackup"
> JobDefs = "DefaultJob"
> client = test-fd
> Pool = RemoteFile
> }
> Job {
> Name = "RemoteBackup2"
> JobDefs = "DefaultJob"
> client = marty-pc-fd
> Pool = RemoteFile
> }
> Job {
> Name = "BackupCatalog"
> JobDefs = "DefaultJob"
> Level = Full
> FileSet="Catalog"
> Schedule = "WeeklyCycleAfterBackup"
> RunBeforeJob = "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog"
> RunAfterJob = "/etc/bacula/scripts/delete_catalog_backup"
> Write Bootstrap = "/var/lib/bacula/%n.bsr"
> Priority = 11 # run after main backup
> }
> Job {
> Name = "RestoreFiles"
> Type = Restore
> Client=backup-master-001.novalocal-fd
> FileSet="Full Set"
> Storage = File
> Pool = Default
> Messages = Standard
> Where = /nonexistant/path/to/file/archive/dir/bacula-restores
> }
> Job {
> Name = "RestoreRemote"
> Type = Restore
> Client=test-fd
> FileSet="Full Set"
> Storage = File
> Pool = Default
> Messages = Standard
> Where = /bacula/restore
> }
> Job {
> Name = "RestoreRemote2"
> Type = Restore
> Client=marty-pc-fd
> FileSet="Full Set"
> Storage = File
> Pool = Default
> Messages = Standard
> Where = /bacula/restore
> }
> FileSet {
> Name = "Full Set"
> Include {
> Options {
> signature = MD5
> }
> File = /usr/sbin
> }
> Exclude {
> File = /var/lib/bacula
> File = /nonexistant/path/to/file/archive/dir
> File = /proc
> File = /tmp
> File = /.journal
> File = /.fsck
> }
> }
> Schedule {
> Name = "WeeklyCycle"
> Run = Full 1st sun at 23:05
> Run = Differential 2nd-5th sun at 23:05
> Run = Incremental mon-sat at 23:05
> }
> Schedule {
> Name = "WeeklyCycleAfterBackup"
> Run = Full sun-sat at 23:10
> }
> FileSet {
> Name = "Catalog"
> Include {
> Options {
> signature = MD5
> }
> File = "/var/lib/bacula/bacula.sql"
> }
> }
> Client {
> Name = backup-master-001.novalocal-fd
> Address = 128.104.223.158
> FDPort = 9102
> Catalog = MyCatalog
> Password = "ulDaTfeEvHjt3JcHTR--kMe1XXYupHUWc" # password for FileDaemon
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
> Client {
> Name = test-fd
> Address = 128.104.223.157
> FDPort = 9102
> Catalog = MyCatalog
> Password = "7m1XU9Fp9uJcd76hCpoTIHLPoX3nK8veS" # password for FileDaemon
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
> Client {
> Name = marty-pc-fd
> Address = 64.251.150.227
> FDPort = 9102
> Catalog = MyCatalog
> Password = "xPPgbRxuRNTDy7hHIrYGVZ2MaCv8NkwhX2bgyvR3Kjca" # password for
> FileDaemon
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }
> Storage {
> Name = File
> Address = 128.104.223.158 # N.B. Use a fully qualified name here
> SDPort = 9103
> Password = "eMD7aNwcC9F_N8kwwp0tOAVL7oCXRuH9i"
> Device = FileStorage
> Media Type = File
> }
> Catalog {
> Name = MyCatalog
> dbname = "bacula"; DB Address = ""; dbuser = "bacula"; dbpassword =
> "4KQniFNxHkQn"
> }
> Messages {
> Name = Standard
> mailcomman
[Bacula-users] Director will not connect to a remote client
Hi,
I would like some help with thi issue where the director cannot connect to
either one of my file daemons. I installed the client version of bacula on a
linux computer and a windows computer and configured them along with the
director so they would communicate and run a backup job. Although when i go
into the console and check the status of my clients, the connection is never
successful. It ends up telling me that the connection timed out. Could anyone
tell me what I am doing wrong? Here is my configurations:
Server:
Director File:
Director { # define myself
Name = backup-master-001.novalocal-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 = "f6nJvHpItEmcJ4m7J-WYSJzxdK9S2BGo6" # Console password
Messages = Daemon
DirAddress = 127.0.0.1
}
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Client = backup-master-001.novalocal-fd
FileSet = "Full Set"
Schedule = "WeeklyCycle"
Storage = File
Messages = Standard
Pool = File
Priority = 10
Write Bootstrap = "/var/lib/bacula/%c.bsr"
}
Job {
Name = "LocalBackup"
JobDefs = "DefaultJob"
}
Job {
Name = "RemoteBackup"
JobDefs = "DefaultJob"
client = test-fd
Pool = RemoteFile
}
Job {
Name = "RemoteBackup2"
JobDefs = "DefaultJob"
client = marty-pc-fd
Pool = RemoteFile
}
Job {
Name = "BackupCatalog"
JobDefs = "DefaultJob"
Level = Full
FileSet="Catalog"
Schedule = "WeeklyCycleAfterBackup"
RunBeforeJob = "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog"
RunAfterJob = "/etc/bacula/scripts/delete_catalog_backup"
Write Bootstrap = "/var/lib/bacula/%n.bsr"
Priority = 11 # run after main backup
}
Job {
Name = "RestoreFiles"
Type = Restore
Client=backup-master-001.novalocal-fd
FileSet="Full Set"
Storage = File
Pool = Default
Messages = Standard
Where = /nonexistant/path/to/file/archive/dir/bacula-restores
}
Job {
Name = "RestoreRemote"
Type = Restore
Client=test-fd
FileSet="Full Set"
Storage = File
Pool = Default
Messages = Standard
Where = /bacula/restore
}
Job {
Name = "RestoreRemote2"
Type = Restore
Client=marty-pc-fd
FileSet="Full Set"
Storage = File
Pool = Default
Messages = Standard
Where = /bacula/restore
}
FileSet {
Name = "Full Set"
Include {
Options {
signature = MD5
}
File = /usr/sbin
}
Exclude {
File = /var/lib/bacula
File = /nonexistant/path/to/file/archive/dir
File = /proc
File = /tmp
File = /.journal
File = /.fsck
}
}
Schedule {
Name = "WeeklyCycle"
Run = Full 1st sun at 23:05
Run = Differential 2nd-5th sun at 23:05
Run = Incremental mon-sat at 23:05
}
Schedule {
Name = "WeeklyCycleAfterBackup"
Run = Full sun-sat at 23:10
}
FileSet {
Name = "Catalog"
Include {
Options {
signature = MD5
}
File = "/var/lib/bacula/bacula.sql"
}
}
Client {
Name = backup-master-001.novalocal-fd
Address = 128.104.223.158
FDPort = 9102
Catalog = MyCatalog
Password = "ulDaTfeEvHjt3JcHTR--kMe1XXYupHUWc" # password for FileDaemon
File Retention = 30 days # 30 days
Job Retention = 6 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
Client {
Name = test-fd
Address = 128.104.223.157
FDPort = 9102
Catalog = MyCatalog
Password = "7m1XU9Fp9uJcd76hCpoTIHLPoX3nK8veS" # password for FileDaemon
File Retention = 30 days # 30 days
Job Retention = 6 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
Client {
Name = marty-pc-fd
Address = 64.251.150.227
FDPort = 9102
Catalog = MyCatalog
Password = "xPPgbRxuRNTDy7hHIrYGVZ2MaCv8NkwhX2bgyvR3Kjca" # password for
FileDaemon
File Retention = 30 days # 30 days
Job Retention = 6 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
Storage {
Name = File
Address = 128.104.223.158 # N.B. Use a fully qualified name here
SDPort = 9103
Password = "eMD7aNwcC9F_N8kwwp0tOAVL7oCXRuH9i"
Device = FileStorage
Media Type = File
}
Catalog {
Name = MyCatalog
dbname = "bacula"; DB Address = ""; dbuser = "bacula"; dbpassword =
"4KQniFNxHkQn"
}
Messages {
Name = Standard
mailcommand = "/usr/sbin/bsmtp -h localhost -f \"(Bacula) \<%r>\" -s \"Bacula:
%t %e of %c %l\" %r"
operatorcommand = "/usr/sbin/bsmtp -h localhost -f \"(Bacula) \<%r>\" -s
\"Bacula: Intervention needed for %j\" %r"
mail = root = all, !skipped
operator = root = mount
console = all, !skipped, !saved
append = "/var/log/bacula/bacula.log" = all, !skipped
catalog = all
}
Messages {
Name = Daemon
mailcommand = "/usr/sbin/bsmtp -h localhost -f \"(Bacula) \<%r>\" -s \"Bacula
daemon message\" %r"
mail = root = all, !skipped
console = all, !skipped, !saved
append = "/var/log/bacula/bacula.log" = all, !skipped
}
Pool {
Name = Default
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 365 days # one year
}
Pool {
Name = File
Pool Type = Backup
Label Format = Local-
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 365 days # one year
Maximum Volume By
