>I apologize if this topic has been discussed recently
>(beaten to death, I am sure....) but I did too good a job
>of delegating, and my colleague who set up our backups is away.
>(and I didn't start reading this list when amanda was working
>well for us :-)
That'll teach 'ya :-).
>I changed IP addresses so that amcheck seems to work sporadically
>(output included, then question continues below)
It's good you're starting with amcheck. Until it's happy, other things
are unlikely to work properly.
>==== WARNING: skipping tape test because amdump or amflush seem to be running;
>==== WARNING: if they are not, you must run amcleanup.
This says there either an amdump/amflush is still running (you might
check with "ps -fu <amanda-user>") or the previous run aborted and left
stuff laying around (which is unusual, but can happen). As it says,
if you don't find any evidence of things still active, run amcleanup to
get it going (and run amcheck again to confirm).
If that does not help, I seem to recall a bug in the 2.4.1p1 time frame
with amcleanup not doing its job in certain cases. Go to your amanda.conf
directory and look for a file named "amdump" and one named "log".
If either (or both) exist, just move them aside for now.
>==== WARNING: eprod: selfcheck request timed out. Host down?
This is, without doubt, the number 1 problem that comes up here, so
you're in good company. The FAQ at www.amanda.org has a number of items
to check, so rather than going through that yet again here, give them a
try and if it still won't work, post back with what you tried and what
the results were.
>I think I also have a problem with the script we run through crontab
>(The script appears below)....I think that the script does not correctly
>erase the tape label and relabel it...because I got an error "cannot overwrite
> active tape edgd128".
What I don't understand is why you would relabel the tapes. That's not
at all a normal thing to do. Usually you just give Amanda a pool of
tapes to work with and it manages them just fine, wrapping around one
end back to the beginning.
The error message is saying Amanda thinks the tape you are tring
to label is still active, i.e. it still has valid data. It's protecting
you from losing important stuff, and you should pay attention to it.
In the absences of your colleague :-), what is tapecycle set to
in amanda.conf? How many tapes do you have to work with? What does
"amadmin csd tape" say?
If you're absolutely certain it's OK to zap the tape, you can (at least
temporarily) put a -f on the amlabel command. That should get past
the "error".
>Seth
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
