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