I had the exact same issue and fixed it by changing the source code and re-compiling Bacula:

Bacula version 5.2.12 and modify the source code as follows:

1)

src/lib/bnet.c (changed 6 days to 60 days)

bsock->timeout = 60 * 60 * 60 * 24;   /* 60 days timeout */

   bsock->set_jcr(jcr);

   return bsock;

2)

src/lib/bsock.c (changed 6 days to 60 days)

timeout = 60 * 60 * 60 * 24;   /* 60 days timeout */

This fixed the problem for me.

Uthra

Hi all,

lately we try to save on tapes arount 22 TB, and after 6 days and s

14-May 18:39 de001bs002-dir JobId 818: Error: Watchdog sending kill after 518425 secs to thread stalled reading File daemon.

14-May 18:39 de001bs002-dir JobId 818: Fatal error: Network error with FD during Backup: ERR=Interrupted system call

14-May 18:39 de001bs002-dir JobId 818: Fatal error: No Job status returned from FD.

.

.

.

  Elapsed time:           6 days 25 secs

.

.

all jons die exactly after the same time.

Is there a setting to increase the watch dog period, or to make it aware that the job is actually running?

Can this be a bug?

Thank you!