Thanks, John, for taking the time to try to give me a hand.
I've only gotten one email report, but I did get that one, so I believe that the
"mailto" is correct. That one came after the Dec. 21 run. It's also the one that gave
me the idea that it took 60 hours.
I can only "find" one log file:
su-2.03# find / -name "log*2000*" -print
/usr/local/etc/amanda/daily/log.20001226.0
This is the one I attached to the message.
As to the errors:
error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
error result for host isgadmin disk /dev/hda1: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
These are puzzling, since I have both a /var/lib/amanda/.amandahosts and a
/home/amanda/.amandahosts file (the passwd entry for amanda is: amanda:x:37:6:Amanda
Admin:/var/lib/amanda:/bin/bash ), both files are identical, both are owned by
amanda:amanda, and both contain "isgback.jhuccp.org amanda.
On what I believe is a related note, I also get this error in the log file:
FAIL dumper isgback /dev/ad0s1a 0 [[access as amanda not allowed from
[EMAIL PROTECTED]] open of /home/amanda/.amandahosts failed
I believe that this is related to the fact that /home/amanda/.amandahosts has
owner:group of 37:102, neither one of which show up in /etc/passwd or /etc/group,
although, as you can see from the preceding paragraph, amanda IS user 37 over on the
isgadmin box. The /home directory is actually an NIS mount from the isgadmin machine,
but this doesn't seem to be working well either, since I get an "Operation not
permitted" error when I try to chown them. One more thing I've discovered in the three
weeks that I've been here that I need to fix.
I just learned from my coworker that the tape drive has been running intermittently
today. Any hope that anything useful is being written to the tape? If so, I'm happy to
let it run over the holidays, and work on the problem on Tuesday. But, if it's just
garbage, I'll kill it now and start working on troubleshooting.
It seems to me that your overall advice is to kill amanda and work on getting amcheck
to run without error. Please help me to make sure I do this right. Is killing amanda
completely as simple as looking at "ps -aux" and killing individually anything related
to amanda or owned by amanda, such as taper or dumper? Should I then manually remove
any files, or will amcleanup do all this for me? Anything else I should do to kill it
completely, so that I can work with amcheck without any interference?
Thanks, again, for all your help. Have a happy New Year.
-Kevin Zembower
E. Kevin Zembower
410-659-6139
>>> [EMAIL PROTECTED] 12/28/00 12:40PM >>>
>How can I tell whether anything good is happening with my amanda
>backup? ...
The usual way is to look at the E-mail report you get after every run.
You are getting those, right? If not, you'd better take a look at
"mailto" in amanda.conf.
Take a look at amanda.conf for the "logdir" variable. In that directory
should be a bunch of files named log.YYYYMMDD.N. You can regenerate a
report like this:
amreport <CONFIG> -l <LOGDIR>/log.YYYYMMDD.N
>Which to me indicates that I successfully made a backup on Aug. 17, Dec. =
>21 and 26. ...
That only says Amanda rewrote the tape label on those days. It does
not mean anything useful happened.
>I attached amdump and the log file, if they help.
And they show all sorts of problems (which would also be in the E-mail):
error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
error result for host isgadmin disk /dev/hda1: isgadmin: [access as amanda not
allowed from [EMAIL PROTECTED]]
See the FAQ at www.amanda.org for information on this error.
planner: FAILED mailinglists /dev/hda1 0 [missing result for /dev/hda1 in
mailinglists response]
planner: FAILED virtual /dev/hda1 0 [missing result for /dev/hda1 in virtual
response]
planner: FAILED centernet /dev/sda1 0 [missing result for /dev/sda1 in centernet
response]
These say Amanda was not able to get any estimates from these hosts.
Later on:
driver: result time 1743.049 from dumper0: FAILED 01-00004 [access as amanda not
allowed from [EMAIL PROTECTED]] open of /home/amanda/.amandahosts failed
I don't know why this happened, but it's bad.
The first rule with Amanda is always to run "amcheck <CONFIG>". If it's
not happy (which I'm pretty sure it will not be for you), amdump is also
not going to work.
>-Kevin Zembower
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
