Gene,
Unsure exactly where you're at by now. Various suggestions of
questionable utility:
Are you using SELinux? Probably not, but it can cause some odd
access failures.
The .ssh directory needs to be in the backup user's home directory.
On my Fedora system, that's /var/lib/amanda. SSH is fussy about
permissions. The .ssh directory must be drwx------ (permissions for
backup user only). The id_rsa file should be -rw------- (again, backup
user only). My somewhat hazy recollection is that anything else causes
ssh to quietly fail. See what /etc/passwd has for the backup user's home
directory.
'/raid/DailySet1 does not exist' In previous posts the raid array
was named myraid. In amanda.conf, what does the tpchanger parameter say?
' ... /buildbot/ ... (Permission denied)' 'buildbot' is highly
suspicious. Did you end up building amanda? This is the sort of thing
that would make me look at --prefix and the various installation
directory parameters in the configure command. Also have a look at the
infofile and indexdir parameters in amanda.conf.
Lou
backup@amanda:/etc/amanda/DailySet1$ amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
NOTE: tapelist file does not exists
it will be created on the next run
NOTE: Holding disk '/hold/DailySet1/': 767950848 KB disk space
available, using 767848448 KB
Warning: Identity file /var/backups/.ssh/id_rsa_amanda not accessible:
No such file or directory.
Host key verification failed.
ERROR: directory '/raid/DailySet1' does not exist
ERROR: conf info dir '/buildbot/amanda/AMdb/DailySet1/
curinfo' (Permission denied)
ERROR: index dir '/buildbot/amanda/DailySet1/AMdb' (Permission denied)
Server check took 0.830 seconds
Amanda Backup Client Hosts Check
--------------------------------
ERROR: amanda.coyote.den: selfcheck request failed: error sending REQ:
write error to: Broken pipe
Client check: 1 host checked in 1.062 seconds. 1 problem found.
(brought to you by Amanda 3.5.1)
That is actually 3 ERROR's & 1 WARNING
The first one above points at the /raid/Dailyset1, and has 40660 perms
from the /, owned by backup:backup.
The second also exists and is owned by backup;backup from the root, but
curinfo does not yet exist
Same thing with the 3rd error, 40660 perms all the way to it and owned
by backup:backup all he way.
What am I doing wrong? And what does it need to satisfy the .ssh
warning, that file and its parent dir does not exist.
Nothing above is telling me what I need to do next.
Thank you.
Cheers, Gene Heskett, CET.
