Hello Olaf,
Have you checked DNS? Which is the output for dig tux64.home.lan? It seems
you have a second loopback interface defined in your system and bacula
daemons are using this interface for listening to connections.
Best regards,
Ana
On Fri, Jun 5, 2015 at 3:33 PM, Heitor Faria <hei...@bacula.com.br> wrote:
> > Hello Ana,
> >
> >> Your daemons are listening on 127.0.0.2, and bacula is trying to connect
> >> on 198.162.1.11. You can configure Bacula to listen to any IP commenting
> >> the lines: DirAddress, FDAddress and SDAddress in bacula-dir.conf,
> >> bacula-fd.conf and bacula-sd.conf. Or you can check your DNS resolution.
> >> Maybe the FQDN hostname is being resolved to a local IP.
> >
> > A quick search on the config files got:
> >
> > $ find . -name \*.conf -exec egrep -H -i Address {} \; | sed -e '/:#/d'
> >
> > ./bacula-dir.conf: DirAddress = tux64.home.lan
> > ./bacula-sd.conf: SDAddress = tux64.home.lan
> > ./bacula-dir.conf.d/storage.conf: Address = tux64.home.lan
> > ./bacula-dir.conf.d/client-tux32.conf: Address = tux32.home.lan
> > ./bacula-dir.conf.d/client-tux64.conf: Address = tux64.home.lan
> > ./bconsole.conf: address = tux64.home.lan
> > ./tray-monitor.conf: Address = tux64.home.lan
> > ./tray-monitor.conf: Address = tux64.home.lan
> > ./tray-monitor.conf: Address = tux64.home.lan
> > ./bat.conf: address = tux64.home.lan
>
> Hello Olaf: can you resolv all those names through your DNS Server? If not
> you have to associate them to the actual local IP address you want to use
> at /etc/hosts, or just replace them with the address.
About the Dir/Sd/Fd address I think they are more useful if you have more
> than one local network interface at your server. You may comment them.
>
> Regards,
> =======================================================================
> Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified
> Administrator II
> 15 a 26 de junho: Treinamento Telepresencial Bacula:
> http://www.bacula.com.br/?p=2174
> 61 8268-4220
> Site: www.bacula.com.br | Facebook: heitor.faria
> ========================================================================
>
> >
> > $ cat /etc/hosts
> > 127.0.0.1 localhost.localdomain localhost
> > ::1 localhost6.localdomain6 localhost6
> >
> > $ hostname
> > tux64.home.lan
> >
> > so, why does it bind to loopback device ip?
> >
> >> > Have you changed your PID directory to /var/run after upgrade?
> >> Can you
> >> > post the output of "netstat -nltup | grep bacula"?
> >>
> >> $ sudo netstat -nltup | grep bacula
> >> tcp 0 0 127.0.0.2:9101 <http://127.0.0.2:9101>
> >> 0.0.0.0:* LISTEN
> >> 855/bacula-dir
> >> tcp 0 0 127.0.0.2:9102 <http://127.0.0.2:9102>
> >> 0.0.0.0:*
> >> LISTEN 857/bacula-fd
> >> tcp 0 0 127.0.0.2:9103 <http://127.0.0.2:9103>
> >> 0.0.0.0:*
> >> LISTEN 851/bacula-sd
> >>
> >
> > Thank you,
> > Olaf
> >
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > 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
>
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
