Ok here is what I have and here are my thoughts on this. (The thoughts may
be important here :/) I have reinstalled and am using the not-so-cute
DailySet1. The other (disklist) was an evolution of mistakes, sorry. Instead
of inetd.conf I am using xinetd.
The user for the services is operator <=== I am thinking mistake here...
I had problems with amanda user
having access to full paths
I am currently running the commands (amdump, amrecover, etc) with root. I
have included the information that you referred to below. uid/gid 11 is
operator. You think if I change everything to amanda (all services and
./configure --with-user= ) that this may resolve this issue?
[root@schroeder tmp]# amrecover DailySet1
AMRECOVER Version 2.4.2p2. Contacting server on schroeder ...
220 schroeder AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-04-09)
200 Working date set to 2002-04-09.
200 Config set to DailySet1.
200 Dump host set to schroeder.
$CWD '/tmp' is on disk 'sda6' mounted at '/tmp'.
Scanning /dumps/amanda...
200 Disk set to sda6.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /tmp
amrecover> quit
200 Good bye.
[root@schroeder tmp]# amadmin DailySet1 find schroeder sda6
Scanning /dumps/amanda...
date host disk lv tape or file file status
2002-04-09 schroeder sda6 0 DailySet100 1 OK
[root@schroeder tmp]# amadmin DailySet1 find schroeder /
Scanning /dumps/amanda...
date host disk lv tape or file file status
2002-04-09 schroeder / 0 DailySet100 11 OK
[root@schroeder tmp]# amgetconf DailySet1 logdir
/usr/adm/amanda/DailySet1
[root@schroeder tmp]# grep -e schroeder |grep sda6 *
amandad.20020409140621.debug:DUMP sda6 0 OPTIONS |;bsd-auth;index;
amandad.20020409140621.debug:OK /dev/sda6
amindexd.20020409140602.debug:> DISK sda6
amindexd.20020409140602.debug:< 200 Disk set to sda6.
amindexd.20020409140602.debug:> DISK sda6
amindexd.20020409140602.debug:< 200 Disk set to sda6.
amindexd.20020409142812.debug:> DISK sda6
amindexd.20020409142812.debug:< 200 Disk set to sda6.
amindexd.20020409142812.debug:> DISK sda6
amindexd.20020409142812.debug:< 200 Disk set to sda6.
selfcheck.20020409140621.debug:selfcheck: checking disk sda6
selfcheck.20020409140621.debug:selfcheck: device /dev/sda6
thanks, doug
-----Original Message-----
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 1:52 PM
To: Doug Johnson
Cc: Amanda-Users (E-mail)
Subject: Re: another amrecover problem.
>amrecover> setdate ---08
>200 Working date set to 2002-04-08.
>No index records for cwd on new date
>...
Here is the key:
>> DATE 2002-04-08
>< 200 Working date set to 2002-04-08.
>> OISD /
>< 500 No dumps available on or before date "2002-04-08"
What amindexd does at this point is roughly equivalent to:
amadmin disklist find schroeder '^/$'
(Is your config really named "disklist"? That's either odd or cute :-).
This, in turn, searches through the log.YYYYMMDD.NN files in your logdir
(amgetconf disklist logdir) directory.
Does the amadmin command say it found any backups for this client/disk?
Looking at those log files (and the directory down to them), does
uid/gid 11 (what amindexd is running as -- did you forget to change that
inetd.conf line?) have access to them?
Grep'ing through the log files, do you see entries for this client/disk?
>Doug Johnson
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
