> 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
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.
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 rou
> 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
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
loc
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
> 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
> 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
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 D
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ü
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 = "7m1XU9Fp9uJcd76hCpoTIH
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 t
> 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 a
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
h
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 connec
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
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 comm
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 tu
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 p
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 th
20 matches
Mail list logo
