I had misunderstood the meaning of the FDAddress directive. I had understood it
to be the address of the client whereas it is really the address where the
client should listen for DIR connections. Now it is removed, the client listens
on all addresses with is really what I want.
Best
-Chris-
I do know that best practice is to always specify fully qualified domain
names in the conf files (hostname.domain). What do you have specified in
your bacula-fd.conf file? Additionally, are you specifying localhost
anywhere in your bacula-dir.conf file? If so, should correct it to the
relevant fqdn
I took out the FDAddress directive and now it is working. The FD is
listening on all addresses. Many thanks Marcin.
Chris
On Tue, 19 Sep 2023, 10:46 Marcin Haba, wrote:
> Hello Chris,
>
> You need to remove the FDAddress directive (in bacula-fd.conf in
> FileDaemon resource) to set FD listening
Hello Chris,
You need to remove the FDAddress directive (in bacula-fd.conf in
FileDaemon resource) to set FD listening on all interfaces or you can
set the FDAddress directive to the desired network interface address.
After this change you need to restart the file daemon.
More information you can
I have set up a new remote client running FD only on Debian 12. The client
is on the same LAN as the DIR/SD.
I get a connection refused error from the job.
The FD is running but is listening on 127.0.1.1 port 9102 which is probably
why the connection is refused.
Client bacula-fd -t returns no er
