>>>>> On Fri, 15 Feb 2019 15:21:16 +0000, William Muriithi said: > > > Also, try "status dir" to see what the Director is doing. > > Hmm, this see to help. I believe this is the job number 7 that has a fatal > error as status. Wish it was more elaborate than that. Have you seen that > error before? > > Daemon started 12-Feb-19 16:02. Jobs: run=0, running=5 mode=0,0 > Heap: heap=270,336 smbytes=173,258 max_bytes=174,054 bufs=447 max_bufs=454 > > Scheduled Jobs: > Level Type Pri Scheduled Name Volume > =================================================================================== > Incremental Backup 10 15-Feb-19 11:58 BackupClient1 000128L6 > Full Backup 10 15-Feb-19 15:08 BackupClient2 000128L6 > Full Backup 11 15-Feb-19 15:10 BackupCatalog 000128L6 > ==== > > Running Jobs: > Console connected at 12-Feb-19 16:02 > Console connected at 14-Feb-19 16:09 > JobId Level Name Status > ====================================================================== > 7 Full BackupClient2.2019-02-12_16.08.21_03 has a fatal error > 8 Full BackupClient1.2019-02-13_11.58.00_07 is waiting execution > 9 Full BackupCatalog.2019-02-13_15.10.00_08 is waiting execution > 10 Full BackupClient1.2019-02-14_11.58.00_14 is waiting execution > 11 Full BackupCatalog.2019-02-14_15.10.00_15 is waiting execution > ====
No, I've never seen it stuck with "has a fatal error" -- that looks like a bug, i.e. the job should terminate soon after it gets a fatal error. __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
