Hi, 17.09.2007 16:12,, Lucio wrote:: > Hello *, > > Bacula 2.0.3/Etch, backup on DVD, full backup takes 5 DVDs. Full backup is > scheduled the 1st monday each month, and it always happens the same error: > > ------------------------------------- > 08-set 23:55 mybkp-dir: Start Backup JobId 141, > Job=Datimybkp.2007-09-03_23.55.00 > 14-set 20:42 mybkp-fd: Datimybkp.2007-09-03_23.55.00 Fatal error: job.c:1755 > Comm error with SD. bad response to Append Data. ERR=No data available
From this error message, I assume the SD has already crashed here. > 14-set 20:42 mybkp-dir: Datimybkp.2007-09-03_23.55.00 Error: Bacula 2.0.3 > (06Mar07): 14-set-2007 20:42:56 > JobId: 141 > Job: Datimybkp.2007-09-03_23.55.00 > Backup Level: Incremental, since=2007-08-31 23:55:03 > Client: "mybkp-fd" 2.0.3 (06Mar07) > i486-pc-linux-gnu,debian,4.0 > FileSet: "Full Set" 2007-06-29 10:40:32 > Pool: "Default" (From Job resource) > Storage: "DVD" (From Job resource) > Scheduled time: 03-set-2007 23:55:00 > Start time: 08-set-2007 23:55:33 > End time: 14-set-2007 20:42:56 > Elapsed time: 5 days 20 hours 47 mins 23 secs ... after waiting for a very long time. > Priority: 10 > FD Files Written: 0 > SD Files Written: 0 > FD Bytes Written: 0 (0 B) > SD Bytes Written: 0 (0 B) > Rate: 0.0 KB/s > Software Compression: None > VSS: no > Encryption: no > Volume name(s): > Volume Session Id: 14 > Volume Session Time: 1188214291 > Last Volume Bytes: 0 (0 B) > Non-fatal FD errors: 0 > SD Errors: 0 > FD termination status: Error > SD termination status: Error > Termination: *** Backup Error *** > ------------- > > After this error the SD is dead (it doesn't show up in "ps ax"). The obvious > subsequent errors tell: > > 14-set 20:42 mybkp-dir: Start Backup JobId 143, > Job=Datimybkp.2007-09-04_23.55.00 > 14-set 20:43 mybkp-dir: Datimybkp.2007-09-04_23.55.00 Warning: bnet.c:864 > Could not connect to Storage daemon on debian.internal.mybkp.it:9103. > ERR=Connection refused > > > Now the question is: why does the SD die? Did you get a traceback mailed, or is there a core file for analysis? Otherwise, you could run the SD with trace output enabled and see if that tells you something. Finally, there is a chapter on how to run the daemons under gdb, so if you know how to use that, you could find some more information. > I've googled for the first error, but it seems no one in the world has ever > seen such an error string... Which *does* tell us a bit about how stable the daemons ususally run... Arno > Lucio. > -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
