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- > On 19 Sep 2023, at 13:23, Rob Gerber <r...@craeon.net> wrote: > > 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. > > Robert Gerber > 402-237-8692 > r...@craeon.net <mailto:r...@craeon.net> > On Tue, Sep 19, 2023, 5:31 AM Chris Wilkinson <winstonia...@gmail.com > <mailto:winstonia...@gmail.com>> wrote: > 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 errors. > > I suppose the FD needs to listen on any address but I can't see how to do > that. > > Is there a bacula-fd.conf setting for this? > > Thanks > Chris Wilkinson > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net <mailto:Bacula-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/bacula-users > <https://lists.sourceforge.net/lists/listinfo/bacula-users>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
