From: Geert S. <Gee...@va...> - 2012-10-03 08:34:12
|
Op 20121002 om 12:15 schreef DAHLBOKUM Markus (FPT INDUSTRIAL): <bigsnip/> > > I have added the heartbeat interval on all daemons, but no change. The _all_ deamons involved is important. <bigsnip/> > > Markus > > > I now could check if bacula fd to sd connection timed out because of the > network switches. This was not the case. My job still cancels. > > > > What I did now was to check if the heartbeat is really working. So I installed > wireshark and tracked my network connections. > > I see my traymonitor connecting every 5 sec to dir, sd and fd. But I can’t see > any heartbeat between my two servers. There should be something every 5 sec, > too. > > > > Can someone tell me how and when the heartbeat should occur? AFAIK is it a "keep alive" signal, which is needed when there is no data transfer. That "idle" occurs shortly afther job start. It is when the file deamon is searching / collecting the files that the bacula-dir requested. > Is it active when no job is running? No, it comes only in action during a job's idle time. Heartbeat is silent when there no "interaction" with a bacula-fd. > In my config I set the following line for dir, sd and fd: > > Heartbeat Interval = 5 > > This should result in a heartbeat every 5 sec? Could be. I imagine that there _could be_ a minimal (usefull) interval, say twenty seconds. That 20 is a value I made up to illustrate why the heartbeat isn't visible every five seconds by Wireshark. In our Bacula configuration did the addition 'Heartbeat Interval = 60' solve time out issues. I had no need to sniff them. > I’m thankful for every help I can get. > > Regards, > Markus Cheers Geert Stappers -- http://www.vanadcimplicity.com/ |