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

2016-03-14 Thread maaf4d
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 +---

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

2016-03-14 Thread 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

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

2016-03-14 Thread maaf4d
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. +-

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

2016-03-14 Thread maaf4d
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. +--

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

2016-03-14 Thread maaf4d
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:*

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

2016-03-13 Thread 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 se

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

2016-03-10 Thread maaf4d
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

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

2016-03-10 Thread maaf4d
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 mac

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

2016-03-10 Thread maaf4d
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. +--

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

2016-03-10 Thread maaf4d
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. +-

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

2016-03-10 Thread 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

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

2016-03-10 Thread 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 tc

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

2016-03-09 Thread maaf4d
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

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

2016-03-09 Thread maaf4d
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 Passwor

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

2016-03-08 Thread maaf4d
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 th

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

2016-03-04 Thread maaf4d
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 +--

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

2016-03-01 Thread 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 w