>>>>> On Tue, 5 Mar 2019 12:20:16 -0500, Phil Stracchino said: > > I've recently reinstalled one of my servers in one of many attempts to > get a required work VPN tool working properly, and just this morning > reinstalled bacula-client-9.4.2-1.el7.x86_64.rpm and > bacula-libs-9.4.2-1.el7.x86_64.rpm from the Bacula.org community repo. > The FD runs, but does not appear to be listening on 9102, although it > clearly thinks it is: > > > jumpgate:root:~:34 # /opt/bacula/bin/bacula-fd -fP -c > /opt/bacula/etc/bacula-fd.conf -d 200 > bacula-fd: address_conf.c:274-0 Initaddr 0.0.0.0:9102 > jumpgate-fd: jcr.c:131-0 read_last_jobs seek to 192 > jumpgate-fd: jcr.c:138-0 Read num_items=0 > jumpgate-fd: plugins.c:97-0 load_plugins > jumpgate-fd: plugins.c:136-0 Found plugin: name=bpipe-fd.so len=11 > jumpgate-fd: fd_plugins.c:1404-0 is_plugin_compatible called > jumpgate-fd: fd_plugins.c:1390-0 Loaded plugin: bpipe-fd.so > jumpgate-fd: filed.c:270-0 filed: listening on port 9102 > jumpgate-fd: bnet_server.c:86-0 Addresses 0.0.0.0:9102 > > > And so does the OS; lsof -i reports: > bacula-fd 17970 root 3u IPv4 362073772 0t0 TCP *:bacula-fd > (LISTEN) > > > But: > > minbar:root:~:13 # /etc/bacula/checkhost -v jumpgate > Client jumpgate has address 10.24.32.8 > Host jumpgate is alive > problem connecting to "jumpgate", port 9102: No route to host at > /etc/bacula/checkhost line 118
Since you get "No route to host" rather than "Connection refused", my guess is that a firewall (on jumpgate?) is blocking port 9102. __Martin _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
