On Wed, 19 May 2004 at 9:12am, Joe Konecny wrote

> Yes it's running.  I have the debug file now.  I cleaned out the log
> files and hadn't run amrecover since.  Now it's back.
> 
> amindexd: debug 1 pid 7836 ruid 3 euid 3: start at Wed May 19 08:05:50 2004
> amindexd: version 2.4.4p2
> amindexd: time 0.000: < 220 R4P17 AMANDA index server (2.4.4p2) ready.
> amindexd: time 0.092: > SECURITY USER root
> amindexd: time 0.092: bsd security: remote host R4P17.gmihome.com user root 
> local user bin
> amindexd: time 0.092: amandahosts security check passed
> amindexd: time 0.092: < 200 Access OK
> amindexd: time 0.192: > FEATURES fffffeff9ffe0f
> amindexd: time 0.192: < 200 FEATURES fffffeff9ffe0f
> amindexd: time 0.292: > DATE 2004-05-19
> amindexd: time 0.292: < 200 Working date set to 2004-05-19.
> amindexd: time 0.392: > SCNF DailySet1
> amindexd: time 0.394: < 200 Config set to DailySet1.
> amindexd: time 0.492: > HOST R4P17.gmihome.com
> amindexd: time 0.492: < 501 No index records for host: R4P17.gmihome.com. 
> Have you enabled indexing?

Your indexdir has the name "r4p17.gmihome.com", but it's looking for 
R4P17.  Try 'sethost r4p17.gmihome.com' at the amrecover prompt.  What 
does the disklist entry for this host look like, and what is it's official 
hostname in DNS?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University