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.
Yours,
Carsten
--
To UNSUBSCRIBE, email to
I think I based my configuration file on the documentation and examples
that were available at the time.
Tom
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
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
Dear Tom,
I think I based my configuration file on the documentation and examples
that were available at the time.
I'm guessing that you either resolved the problem or gave up on bacula
by now?
If you agree that the problem was in the configuration of your system,
I'd like to close this bug
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
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
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
Yes, you are right.
This is the same trouble in samba package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669891
It is not a bug in package and not a bug in network-manager, but
peoples unhappied :)
Can you try to add /usr/bin/nm-online call into /etc/default/bacula-fd
and check,
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
9 matches
Mail list logo
