[Bug 241480] Re: bacula-fd does not start when installed via bacula-client
I know this is 3 years old... but I'm seeing this problem happening randomly on Ubuntu 10.04.3 LTS machines. Thanks for any hints... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/241480 Title: bacula-fd does not start when installed via bacula-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/241480/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
On Wednesday 24 September 2008 19:32:44 Ante Karamatić wrote: > On Wed, 24 Sep 2008 13:58:46 - > > Kern Sibbald <[EMAIL PROTECTED]> 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
On Wed, 24 Sep 2008 13:58:46 - Kern Sibbald <[EMAIL PROTECTED]> 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 -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
On Wednesday 24 September 2008 11:07:52 Ante Karamatić wrote: > 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 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". -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241480] Re: bacula-fd does not start when installed via bacula-client
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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
Thank you for teaching me that. I was wrong in my cause of the problem. My mistake was to use this line in bacula-fd.conf FDAddress = d420.local #FDAddress = 127.0.0.1 I suppose avahi or whatever helps .local work is not ready when the script runs. On Fri, 2008-06-20 at 04:46 +, Ante Karamatić wrote: > Errr... Ubuntu uses upstart so, INIT INFO shouldn't have any effect: > > $ ps ax | grep bacula > pts�0S+ 0:00 grep bacula > $ sudo �etc�init.d�bacula-fd start > * Starting Bacula File daemon...[ OK > ] > $ ps ax | grep bacula > ?Ssl0:00 �usr�sbin�bacula-fd -c �etc�bacula�bacula-fd.conf > pts�0R+ 0:00 grep bacula > $ > > ** Changed in: bacula (Ubuntu) >Importance: Undecided => Medium >Status: New => Triaged > -- Tim Richardson, CPA [EMAIL PROTECTED] +61 458 998 541 GMT+10 all contact details: http:��www.tim-richardson.net�contact Using Linux. -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241480] Re: bacula-fd does not start when installed via bacula-client
Errr... Ubuntu uses upstart so, INIT INFO shouldn't have any effect: $ ps ax | grep bacula pts/0S+ 0:00 grep bacula $ sudo /etc/init.d/bacula-fd start * Starting Bacula File daemon...[ OK ] $ ps ax | grep bacula ?Ssl0:00 /usr/sbin/bacula-fd -c /etc/bacula/bacula-fd.conf pts/0R+ 0:00 grep bacula $ ** Changed in: bacula (Ubuntu) Importance: Undecided => Medium Status: New => Triaged -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 241480] Re: bacula-fd does not start when installed via bacula-client
the fix (file edit) mentioned in the Debian bug report works. -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
