bacula

fraksken · 09-09-2014, 02:21 AM

Hello,

I am attempting to setup a bacula backup server.
The server runs fine and the deamon on the client seems to have been setup correctly.
When I go into the bconsole and do a status client I get the following:

Quote:

Enter a period to cancel a command.
*status client
The defined Client resources are:
1: bacula-fd
2: tools
Select Client (File daemon) resource (1-2): 2
Connecting to Client tools at xx.xx.xx.xx:9102
Failed to connect to Client tools.
====
You have messages.
*messages
09-Sep 09:08 bacula-dir JobId 0: Fatal error: bsock.c:135 Unable to connect to Client: tools on xx.xx.xx.xx:9102. ERR=No route to host

Backup server => Centos 6.5 + bacula 5.0 + webmin 1.7
Followed this manual:

Quote:

http://www.unixmen.com/install-and-c...-6-4-rhel-6-4/

Now I am trying to follow this manual to get a connection:

Quote:

http://webmodelling.com/webbits/misc...us/bacula.aspx

I opened the following ports on both sides: 9101 - 9103 TCP
The client has Centos 7 + Bacula5.
The deamon is running:

Quote:

[root@tools bacula]# systemctl status bacula-fd
bacula-fd.service - Bacula-FileDaemon, a Backup-client
Loaded: loaded (/usr/lib/systemd/system/bacula-fd.service; enabled)
Active: active (running) since Tue 2014-09-09 09:17:43 CEST; 8s ago
Docs: man:bacula-fd(8)
Main PID: 8933 (bacula-fd)
CGroup: /system.slice/bacula-fd.service
└─8933 /usr/sbin/bacula-fd -f -c /etc/bacula/bacula-fd.conf -u roo...

Sep 09 09:17:43 tools.domain.com systemd[1]: Starting Bacula-FileDaemon, a B....
Sep 09 09:17:43 tools.domain.com systemd[1]: Started Bacula-FileDaemon, a Ba....
Hint: Some lines were ellipsized, use -l to show in full.

The bacula server can ping the client:

Quote:

ping xx.xx.xx.xx
PING xx.xx.xx.xx (xx.xx.xx.xx) 56(84) bytes of data.
64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=56 time=13.2 ms
64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=56 time=13.2 ms
64 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=56 time=13.9 ms
^C

What can I be doing wrong?

es0teric · 09-09-2014, 02:44 AM

It seems the client doesn't have a route to whatever IP it's trying to reach. Try running this from that machine, to see what the routing table has to say about how it would go about reaching that IP:

Quote:

ip route get <ip_of_server>

fraksken · 09-09-2014, 02:54 AM

Quote:

Originally Posted by es0teric

It seems the client doesn't have a route to whatever IP it's trying to reach. Try running this from that machine, to see what the routing table has to say about how it would go about reaching that IP:

I get the following results:
Backup server to client server:

Quote:

[root@minion]# ip route get 5.xx.xx.xx
5.xx.xx.xx via 188.xx.xx.xx dev eth0 src 188.xx.xx.xx
cache

And from client server to backup server:

Quote:

[root@tools]# ip route get 188.xx.xx.xx
188.xx.xx.xx via 5.xx.xx.xx dev eth0 src 5.xx.xx.xx
cache

fraksken · 09-12-2014, 04:20 AM

Solved:
Somewhere in the network the port was being blocked. This has been resolved now.