Dustin J. Mitchell-3 wrote: > > In "normal" failure modes, this should be taken care of. Can you give > some detail on the type of failure that's triggering this? > > Also, amcleanup should function as a second line of defense for killing > such processes. >
Here is the error in mail report: FAILED [data timeout] FAILED [cannot read header: got 0 instead of 32768] FAILED [too many dumper retry: "[request failed: timeout waiting for ACK]"] Here is my cronjob: 0 21 * * * /usr/local/sbin/amcleanup DailySet1 10 21 * * * /usr/local/sbin/amcheck DailySet1 30 21 * * * /usr/local/sbin/amdump DailySet1 I put amcleanup before amcheck and amdump. Was it a proper sequences? -- View this message in context: http://www.nabble.com/gtar-program-still-running-after-backup-failed-tf4272149.html#a12174455 Sent from the Amanda - Users mailing list archive at Nabble.com.
