Bug#679479: [pkg-bacula-devel] Bug#679479: bacula-fd fails to start because network is not initialized
On Mon, Dec 01, 2014 at 01:04:34PM -0800, Tom Epperly wrote: On Mon, Dec 1, 2014 at 10:41 AM, Carsten Leonhardt l...@carotec.de wrote: Dear Tom, is (or was, as your bug report is over 2 years old now) there a specific reason why you had the FDAddress = faerun.epperly.home directive in your bacula-fd.conf? Just omitting the directive should (have) give(n) you a functioning backup. I think I based my configuration file on the documentation and examples that were available at the time. What could (should?) be done to avoid that other people encounter the bug that you reported? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679479: [pkg-bacula-devel] Bug#679479: bacula-fd fails to start because network is not initialized
From my perspective, it seems like there must be a class of system services that need to be started after the network is configured and DNS is available. Bacula and other members of that class of services should have a common mechanism to be started after network+DNS are available. I think my fix was to add delays to the bacula init script to make sure netmanager was done. Tom On Mon, Dec 1, 2014 at 1:24 PM, Geert Stappers stapp...@stappers.nl wrote: On Mon, Dec 01, 2014 at 01:04:34PM -0800, Tom Epperly wrote: On Mon, Dec 1, 2014 at 10:41 AM, Carsten Leonhardt l...@carotec.de wrote: Dear Tom, is (or was, as your bug report is over 2 years old now) there a specific reason why you had the FDAddress = faerun.epperly.home directive in your bacula-fd.conf? Just omitting the directive should (have) give(n) you a functioning backup. I think I based my configuration file on the documentation and examples that were available at the time. What could (should?) be done to avoid that other people encounter the bug that you reported? Groeten Geert Stappers -- Leven en laten leven -- To unsubscribe, send mail to 679479-unsubscr...@bugs.debian.org.
Bug#679479: [pkg-bacula-devel] Bug#679479: bacula-fd fails to start because network is not initialized
Hi!
Sorry for reply delay.
There is not a bug, so all we can do - add some information about this
case into README.Debian.
You can try one of next workarounds:
1. Allow bacula-fd to listen on all addresses - remove line FDAddress
= .. or change it to FDAddress = 0.0.0.0
2. If you always get the same IP-address from dhcp, then you can add
record for faerun.epperly.home into /etc/hosts or specify IP address in
bacula-fd.conf.
In such case bacula-fd correctly start and will be available on this
address after actual network configuration.
3. You can disable autostart of bacula-fd service (update-rc.d
bacula-fd disable) and start it later after network configuration by
dhclient or network-manager.
If network interface configured from /etc/network/interfaces and you
use dhclient (not udcpc or other), than create executable
/etc/dhcp/dhclient-exit-hooks.d/bacula with content
invoke-rc.d bacula-fd restart
(see man dhclient-script for details)
If network interface configured by NetworkManager directly, than create
executable /etc/NetworkManager/dispatcher.d/bacula with content
if [ $1 = eth1 -a $2 = up ]; then invoke-rc.d bacula-fd
restart; fi
(see man network-manager for details)
On Thu, 28 Jun 2012 20:32:04 -0700, Tom Epperly wrote:
Package: bacula-fd
Version: 5.2.6+dfsg-1
Severity: normal
Dear Maintainer,
bacula-fd does not start when I boot my machine. I am not sure which
upgrade stopped bacula-fd, but it hasn't been working for a while.
My machine used to use ifup/ifdown to manage initializing eth1 and
initiating
DHCP to get the IP address etc. Some upgrade switched it to use
NetworkManager to initiate DHCP.
This is the error message flashes on the screen during boot up.
[] Starting Bacula File daemon...:28-Jun 20:20 bacula-fd: ERROR
TERMINATION
at address_conf.c:521
Config error: can't add port (faerun.epperly.home) to (can't resolve
hostname(fa
erun.epperly.home) Non-authoritative for host not found, or
ServerFail.)
: line 49, col 33 of file /etc/bacula/bacula-fd.conf
FDAddress = faerun.epperly.home
failed!
This happens no my home desktop, and it also happens on my Ubuntu
laptop at work.
I tried adding $network to the Required-Start for the
init.d/bacula-fd
script, but it didn't fix the problem.
I can service bacula-fd start just fine from a terminal window once
the network is initialized.
Tom
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-fd depends on:
ii bacula-common 5.2.6+dfsg-1
ii libacl12.2.51-8
ii libc6 2.13-33
ii libgcc11:4.7.1-1
ii libpython2.7 2.7.3-1
ii libssl1.0.01.0.1c-3
ii libstdc++6 4.7.1-1
ii libwrap0 7.6.q-23
ii lsb-base 4.1+Debian7
ii ucf3.0025+nmu3
ii zlib1g 1:1.2.7.dfsg-11
bacula-fd recommends no packages.
Versions of packages bacula-fd suggests:
ii bacula-traymonitor 5.2.6+dfsg-1
-- Configuration Files:
/etc/init.d/bacula-fd changed:
set -e
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/bacula-fd
NAME=bacula-fd
PORT=9102
DESC=Bacula File daemon
test -f $DAEMON || exit 0
if [ -n `getent services bacula-fd` ]; then
PORT=`getent services bacula-fd | awk '{ gsub(/tcp,,$2);
print $2; }
'`
fi
. /lib/lsb/init-functions
. /usr/share/bacula-common/common-functions.init
if [ -r /etc/default/$NAME ]; then
. /etc/default/$NAME
fi
CONFIG=${CONFIG:-/etc/bacula/$NAME.conf}
create_var_run_dir
PIDFILE=/var/run/bacula/$NAME.$PORT.pid
do_start()
{
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--oknodo --exec $DAEMON -- -c $CONFIG $ARGS
}
do_stop()
{
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE
\
--exec $DAEMON -- -c $CONFIG $ARGS
}
case $1 in
start)
if [ $ENABLED = no ]; then
log_failure_msg Not starting $DESC: disabled via
/etc/default/$
NAME
exit 0
fi
log_daemon_msg Starting $DESC...
if do_start ; then
log_end_msg 0
else
log_end_msg 1
fi
;;
stop)
log_daemon_msg Stopping $DESC...
if do_stop ; then
log_end_msg 0
else
log_end_msg 1
fi
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
;;
status)
status_of_proc -p $PIDFILE $DAEMON $NAME
;;
*)
N=/etc/init.d/$NAME
echo Usage: $N {start|stop|restart|force-reload|status} 2
exit 1
;;
esac
exit 0
-- no debconf information
___
pkg-bacula-devel mailing list
pkg-bacula-de...@lists.alioth.debian.org
Bug#679479: [pkg-bacula-devel] Bug#679479: bacula-fd fails to start because network is not initialized
Thanks for your reply. I understand from a developer's perspective that
there is no bug.
Somewhere along the line, I believe a Debian upgrade switched me from using
/etc/network/interfaces and ifupdown to using NetworkManager. It happened a
while ago, so I don't remember how it all happened. At this point, my
backups stopped happening. Perhaps, it should be considered a bug in the
code that switched me to using NetworkManager. The fact that it happened on
two systems: one managed by me and one managed by someone else at work
suggests that it is not just an isolated issue.
Tom
On Sun, Jul 8, 2012 at 12:41 AM, Alexander Golovko
alexan...@ankalagon.ruwrote:
Hi!
Sorry for reply delay.
There is not a bug, so all we can do - add some information about this
case into README.Debian.
You can try one of next workarounds:
1. Allow bacula-fd to listen on all addresses - remove line FDAddress =
.. or change it to FDAddress = 0.0.0.0
2. If you always get the same IP-address from dhcp, then you can add
record for faerun.epperly.home into /etc/hosts or specify IP address in
bacula-fd.conf.
In such case bacula-fd correctly start and will be available on this
address after actual network configuration.
3. You can disable autostart of bacula-fd service (update-rc.d bacula-fd
disable) and start it later after network configuration by dhclient or
network-manager.
If network interface configured from /etc/network/interfaces and you use
dhclient (not udcpc or other), than create executable
/etc/dhcp/dhclient-exit-hooks.**d/bacula with content
invoke-rc.d bacula-fd restart
(see man dhclient-script for details)
If network interface configured by NetworkManager directly, than create
executable /etc/NetworkManager/**dispatcher.d/bacula with content
if [ $1 = eth1 -a $2 = up ]; then invoke-rc.d bacula-fd restart; fi
(see man network-manager for details)
On Thu, 28 Jun 2012 20:32:04 -0700, Tom Epperly wrote:
Package: bacula-fd
Version: 5.2.6+dfsg-1
Severity: normal
Dear Maintainer,
bacula-fd does not start when I boot my machine. I am not sure which
upgrade stopped bacula-fd, but it hasn't been working for a while.
My machine used to use ifup/ifdown to manage initializing eth1 and
initiating
DHCP to get the IP address etc. Some upgrade switched it to use
NetworkManager to initiate DHCP.
This is the error message flashes on the screen during boot up.
[] Starting Bacula File daemon...:28-Jun 20:20 bacula-fd: ERROR
TERMINATION
at address_conf.c:521
Config error: can't add port (faerun.epperly.home) to (can't resolve
hostname(fa
erun.epperly.home) Non-authoritative for host not found, or ServerFail.)
: line 49, col 33 of file /etc/bacula/bacula-fd.conf
FDAddress = faerun.epperly.home
failed!
This happens no my home desktop, and it also happens on my Ubuntu
laptop at work.
I tried adding $network to the Required-Start for the init.d/bacula-fd
script, but it didn't fix the problem.
I can service bacula-fd start just fine from a terminal window once
the network is initialized.
Tom
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-fd depends on:
ii bacula-common 5.2.6+dfsg-1
ii libacl12.2.51-8
ii libc6 2.13-33
ii libgcc11:4.7.1-1
ii libpython2.7 2.7.3-1
ii libssl1.0.01.0.1c-3
ii libstdc++6 4.7.1-1
ii libwrap0 7.6.q-23
ii lsb-base 4.1+Debian7
ii ucf3.0025+nmu3
ii zlib1g 1:1.2.7.dfsg-11
bacula-fd recommends no packages.
Versions of packages bacula-fd suggests:
ii bacula-traymonitor 5.2.6+dfsg-1
-- Configuration Files:
/etc/init.d/bacula-fd changed:
set -e
PATH=/sbin:/bin:/usr/sbin:/**usr/bin
DAEMON=/usr/sbin/bacula-fd
NAME=bacula-fd
PORT=9102
DESC=Bacula File daemon
test -f $DAEMON || exit 0
if [ -n `getent services bacula-fd` ]; then
PORT=`getent services bacula-fd | awk '{ gsub(/tcp,,$2); print
$2; }
'`
fi
. /lib/lsb/init-functions
. /usr/share/bacula-common/**common-functions.init
if [ -r /etc/default/$NAME ]; then
. /etc/default/$NAME
fi
CONFIG=${CONFIG:-/etc/bacula/**$NAME.conf}
create_var_run_dir
PIDFILE=/var/run/bacula/$NAME.**$PORT.pid
do_start()
{
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--oknodo --exec $DAEMON -- -c $CONFIG $ARGS
}
do_stop()
{
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \
--exec $DAEMON -- -c $CONFIG $ARGS
}
case $1 in
start)
if [ $ENABLED = no ]; then
log_failure_msg Not starting $DESC: disabled via
/etc/default/$
NAME
exit 0
fi
log_daemon_msg Starting $DESC...
