Hello,
On 03.11.2005 23:32, Eric Langheinrich wrote:
Sorry that I answer only now. I'm rather busy at the moment.
This might be a network problem - in that case, try the Heartbeat
interval directive in all relevant configuration files. In case some
router in between your DIR and FD drops the connection while that large
file is stored, this should resolve the problem.
Arno
Okay, figured out that the Heartbeat Interval directive goes in the
bacula-fd.conf file on the client.
Hmm. I think there were other places, too. IIRC, this was discussed not
long ago on this list, or on bacula-devel, so you might consider
searching in the list archives.
What is a reasonable value? I'm assuming
that the value corresponds to the number of seconds between heartbeats. I'm
starting with 15 for my testing, but want to know if anyone has some
recommendations based on experience.
No experiences, but as I'm hoping that *no* router drops a connection
after only a few minutes of idle time, I'd suggest to start with a
longer timeout than 15 seconds. But then, these heartbeat packages
shouldn't cost much bandwith and CPU power.
Arno, thanks for the help on this one.
I hope this solved your problem!
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
