On 10/17/22 20:09, Bill Arlofski via Bacula-users wrote:
On 10/17/22 13:14, Rodrigo Reimberg via Bacula-users wrote:
>
Telnet from DIR to FD on port 9102 not ok, I’m using
ConnectToDirector parameter.
Hello Rodrigo,
Of course this will not work. The client is behind NAT, and the
Director cannot connect to it on port 9102 (or any other port :).
As you know, with the 'ConnectToDirector' feature enabled, the FD
calls into the Dir on port 9101 (default). There is no requirement to
set any connection Schedule. The Client will remain connected until
the `ReconnectionTime` is reached (default 40 mins), at which point
the connection will be dropped and immediately re-established.
Per the documentation, this FD -> DIR connection *should be* used for
all communications between the Director and this client:
----8<----
ConnectToDirector = <yes∣no> When the ConnectToDirector directive is
set to true, the Client will contact the Director according to the
rules. The connection initiated by the Client will be then used by the
Director to start jobs or issue bconsole commands.
----8<----
I just ran some tests, and it looks like there is a bug.
Maybe. However, it depends on what the client is doing. If the client
goes into sleep-mode, it will not re-establish the connection after the
ReconnectionTime. In that case, the Director would not have an active
socket and so may well try to establish one.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
