On Tue, 18 May 2010 18:38:29 +0200, Foo <bfo...@yahoo.co.uk> wrote: > 18-May 18:04 DIRHOSTNAME-dir JobId 32487: Fatal error: Network error with > FD during Backup: ERR=Connection reset by peer > 18-May 18:04 DIRHOSTNAME-dir JobId 32487: Fatal error: No Job status > returned from FD.
Where the manually run jobs both failed, one of the scheduled nightly jobs succeeded, the other failed in a similar fashion (same error after 2+ hours). The one that succeeded took 32 mins 52 secs at 6.3 MB/s which is slightly faster than the manuals so could this be some timeout limit that the other one ran into and not this one? What do you do in such a case, add a heartbeat? > Is this a networking issue where some "I'm done" packet was lost/held up? > If so, does this go to another port (I don't think so), or does it use a > special protocol/form so a specific network issue may block that but not > everything else? Additionally, I got the following error message in mail (via logcheck): May 18 17:17:49 DIRHOSTNAME bacula-sd: bsock.c:488 Packet size too big from "client:1.2.3.4:36643. Terminating connection. Anyone any ideas what this means? ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
