On Thu, 23 Feb 2012 10:49:55 -0500, Josh Fisher wrote: > On 2/23/2012 4:11 AM, Silver Salonen wrote: >> On Wednesday 22 February 2012 15:20:10 Silver Salonen wrote: >> >> What's also interesting about these failures are these lines >> (similar in all these failing jobs): >> FD Files Written: 381 >> SD Files Written: 0 >> FD Bytes Written: 391,430,239 (391.4 MB) >> SD Bytes Written: 0 (0 B) >> Last Volume Bytes: 260 (260 B) >> >> And the actual volume file seems to contain all the data (its size >> is 373MB). >> >> What can we conclude from that? >> Does the failure/timeout/whatever occur after the FD--SD connection, >> eg. when SD tries to communicate with DIR about the end of the job or >> smth? > > Or does the Dir abort the job after a timeout/whatever occurs for the > Dir->FD connection? Since the problem started after changing network > environment, I suspect a switch or router is timing out the Dir->FD > connection, perhaps when the FD is busy compressing a large file or > something. Try turning compression off? Just a guess.
Tried it. No changes :( -- Silver ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users