>Checking running processes is a nightshift job, I'd like to avoid :) Understood. I'm on a first name basis with all three Operations shifts (plus weekends) here, and I'm not sure that's necessarily a good thing. They're nice people, but at 3 AM ...
:-) :-) >Any more tips left? I looked at the code and that error only comes from one place, when driver has tried doing a dump once and it failed but was requeued to "TRYAGAIN", then the second attempt also failed. I'm not sure the message means what it says, that there really was a problem connecting to the host. That may have been what it originally meant, but now it might mean other things (in case it isn't obvious, this code gets a little confusing to navigate). I'm pretty sure it has nothing to do with starting a new tapecycle, except in an indirect way (if at all). My best guess is it has something to do with the amount of holding disk space you have, or possibly other activity going on in the holding disk at the same time Amanda is running (e.g. Amanda thought it had N MBytes but when it actually tried to use the space, less than that was really there). I would need to see the corresponding amdump.<nn> file that goes along with one of these errors, and possibly all the client logs for that same run. If you want to contact me offline of the list for this, that's OK. In the meantime, you might try dropping maxdumps back to 1. That may or may not help -- it's just a guess. >Sascha John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
