[Bug 241480] Re: bacula-fd does not start when installed via bacula-client

[Ante Karamatić]

It's worth mentioning that after the network is started, avahi (on
default install) looks at DNS to see if '.local' domain is served by DNS
server. If that's true, avahi doesn't start. If there is no DNS for
'.local', avahi will start. Since it takes some time to register an IP
with a hostname, it is possible that bacula-fd is started before that
registration happens. This results in unresolvable hostname and thuss
failure to start.

I suggest using 'localhost' if you desire to have '127.0.0.1'. If there
is an non-local interface (eth0, eth1, wlan0, ...), d420.local will be a
record for non-local IP.

This bug is valid, but at the moment is unresolvable. Ubuntu has plans
on replacing SysV init system with upstart, which could solve this
issue.

I'm closing this bug. If you feel that's wrong, please reopen it.

** Changed in: bacula (Ubuntu)
       Status: Triaged => Won't Fix

-- 
bacula-fd does not start when installed via bacula-client
https://bugs.launchpad.net/bugs/241480
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.