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

[Kern Sibbald]

On Wednesday 24 September 2008 19:32:44 Ante Karamatić wrote:
> On Wed, 24 Sep 2008 13:58:46 -0000
>
> Kern Sibbald <kern at sibbald.com> wrote:
> > I don't understand why you cannot start Bacula after the network is
> > up and running and DNS is serving names.  That is how it works on all
> > other systems. We have never run into this problem elsewhere, so I
> > cannot understand why it is "unresolvable".
>
> Avahi is an implementation of the DNS Service Discovery and Multicast
> DNS specifications for Zeroconf Networking. It uses 'special' '.local'
> domain.
>
> Problem is that network is up, but the user is using 'hostname.local'
> FQDN. This FQDN isn't managed by DNS, so it isn't resolvable. This
> domain is managed by interaction between all computers, which over
> Zeroconf talk to each other and arrange their FQDN inside '.local'
> domain. This can take a minute or two. This is why Bacula is started
> before the FQDN is resolvable.
>
> We could resolve this problem if we would stall booting of all services
> untill avahi registers server, but this isn't a nice solution :/.
> Upstart enables state driven booting, so all services would boot up,
> except those that depend on avahi. Those will wait until upstart
> declares that mDNS is up.
>
> http://en.wikipedia.org/wiki/Zeroconf

OK, thanks for the explanation. I was unaware of the Zeroconf problems, and 
agree that stalling all services at boot time is not a good solution.  I am 
going to note this because I imagine it will come up in other distros ...

-- 
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.