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


babylon5:alaric:~:5 $ ping  -c3 jumpgate
PING jumpgate.caerllewys.net (10.24.32.8) 56(84) bytes of data.
64 bytes from jumpgate.caerllewys.net (10.24.32.8): icmp_seq=1 ttl=64
time=0.271 ms
64 bytes from jumpgate.caerllewys.net (10.24.32.8): icmp_seq=2 ttl=64
time=0.295 ms
64 bytes from jumpgate.caerllewys.net (10.24.32.8): icmp_seq=3 ttl=64
time=0.238 ms

--- jumpgate.caerllewys.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 26ms
rtt min/avg/max/mdev = 0.238/0.268/0.295/0.023 ms
babylon5:alaric:~:6 $ telnet jumpgate 22
Trying 10.24.32.8...
Connected to jumpgate.caerllewys.net.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.4
^]
telnet> quit
Connection closed.
babylon5:alaric:~:7 $ telnet jumpgate 9102
Trying 10.24.32.8...
telnet: Unable to connect to remote host: No route to host
babylon5:alaric:~:8 $


The same check works perfectly for other clients also running 9.4.2:

minbar:root:~:15 # /etc/bacula/checkhost -v narn
Client narn has address 10.24.32.16
Host narn is alive
Bacula-FD listening on port 9102
Returning value 0



Is anyone else running 9.4.2, successfully or otherwise, on
RHEL/OEL/CentOS 7.6?  Has anyone else seen this problem where the FD
thinks it is listening on 9102, but is apparently deaf?

Is systemd (may it die in darkness) possibly shooting the FD in the foot
somehow?  I'm at a loss to understand why this is not working.


-- 
  Phil Stracchino
  Babylon Communications
  [email protected]
  [email protected]
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958


_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to