Justin,
I know what you told us, but I think we have a situation that I (and Martin)
described:
- FD cannot connect to Director due to firewall
- Director CAN connect to FD (I know, I know... :)
- Job starts, Director connects to FD and receives all the queued "Cannot
connect" messages
- Job runs fine
Here is how I tested:
- In my FD config I set in the the Director{} block:
- ConnectToDirector = yes
- A BOGUS IP address for the `Address =` setting
I killed and restarted the FD in foreground and debug mode, and I see that it
goes on to try to connect to an IP address that
is not taken on my network....
----8<----
speedy-fd: events.c:48-0 Events: code=FD0001 daemon=speedy-fd ref=0x238e
type=daemon source=*Daemon* text=Filed startup
13.0.0 (04Jul22)
speedy-fd: filed.c:296-0 filed: listening on port 9102
speedy-fd: bnet_server.c:90-0 Addresses 0.0.0.0:9102
speedy-fd: bsockcore.c:354-0 Current 10.1.1.99:9101 All 10.1.1.99:9101
speedy-fd: bsockcor
e.c:443-0 Could not connect to server Director daemon 10.1.1.99:9101. ERR=No
route to host
speedy-fd: bsockcore.c:253-0 Unable to connect to Director daemon on
10.1.1.99:9101. ERR=No route to host
speedy-fd: bsockcore.c:354-0 Current 10.1.1.99:9101 All 10.1.1.99:9101
speedy-fd: bsockcore.c:443-0 Could not connect to server Director daemon
10.1.1.99:9101. ERR=No route to host
speedy-fd: bsockcore.c:253-0 Unable to connect to Director daemon on
10.1.1.99:9101. ERR=No route to host
----8<----
Meanwhile, from the Director, I do a `status client=xxxx` and BAMM.. Director
connects to Client and I get the FD's status -
so a Job would also work in this manner.
From your Director, can you try:
# telnet <IP of Client> 9102
And from the Client:
# telnet <IP of Director> 9101
And show us the results?
Thank you!
Bill
--
Bill Arlofski
[email protected]
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
