I forgot to mention that during my debugging, I did have "Heartbeat
Interval" set to 10 on the Client, Storage, and Director resources. The
same error still occurred... Very odd.
On 06/10/2011 07:02 PM, Blake Dunlap wrote:
$20 you have the other bacula comm channel failing due to timeout of
t
Any chance (psheaffer?) someone could contribute the rpms for
openSuSE11.3 x86_64 and put up on the bacula website, soon? I tried the
11.2 versions, but the python version of libraries have been updated so
get a dependency error.
Is it appropriate that I ask here on the forum, or should I submit a
Thank you very much!
It does seem like a major improvement, then. It used to be that when the IPv6
connection failed, bacula would fail in a pretty bad way, and not fail over to
IPv4.
Great to hear that it now gracefully degrades!
Kevin Keane
The NetTech
(North County Tech Center, LLC dba The
Hi,
On Sat, 11 Jun 2011, Kevin Keane wrote:
> The two problems I had:
>
> - The default setting for bacula was wrong. It would only listen on IPv4
> but not IPv6 unless you explicitly added a
> DIRAddresses/FDAddresses/SDAddresses section to the respective config
> files.
This is still t
