|
From: Dan L. <da...@la...> - 2010-12-07 01:47:03
|
On 12/6/2010 8:31 AM, ivane91 wrote: > I have 10+ running bacula jobs. But one is failing. > > > 06-Dec 05:10 peludo-backup-dir JobId 313: Fatal error: Network error with FD during Backup: ERR=Connection reset by peer > 06-Dec 05:10 peludo-backup-sd JobId 313: JobId=313 Job="Faltauno.2010-12-06_05.00.00_31" marked to be canceled. > 06-Dec 05:10 peludo-backup-sd JobId 313: Job write elapsed time = 00:10:05, Transfer rate = 315.3 K Bytes/second > 06-Dec 05:10 peludo-backup-sd JobId 313: Error: bsock.c:529 Read expected 65536 got 1448 from client:206.212.246.210:36643 > 06-Dec 05:10 peludo-backup-dir JobId 313: Fatal error: No Job status returned from FD. > > That's the error. The problem seems to be happening at ~10 minutes since the job is started. Some ideas? Is it always the same client? What is different about this client? A firewall perhaps? It could be that the firewall is tearing down the connection mid-backup. If so, consider adding the heartbeat directive to your Client and/or Storage daemon. The Director configuration documentation is where you should start searching. -- Dan Langille - http://langille.org/ |