Next Problem.

[root@client1 data]# amrecover -C config  -s 192.168.10.95 -t 192.168.10.95
AMRECOVER Version 2.4.3. Contacting server on 192.168.10.95 ...
220 backup AMANDA index server (2.4.4p4) ready.
200 Access OK
Setting restore date to today (2004-11-26)
200 Working date set to 2004-11-26.
200 Config set to config.
200 Dump host set to client1.
Trying disk /data ...
$CWD '/data' is on disk '/data' mounted at '/data'.
200 Disk set to /data.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /data

The date on both servers ist correct.

If I restore the backup on the Server everything is ok. 

The dirs are fine too.

-----Ursprüngliche Nachricht-----
Von: Joshua Baker-LePain [mailto:jlb17 AT duke DOT edu] 
Gesendet: Freitag, 26. November 2004 14:50
An: Sebastian Kösters
Cc: amanda-users AT amanda DOT org
Betreff: Re: AW: AW: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 2:48pm, Sebastian Kösters wrote

> Iptables is disabled on both.
> 
> 
> /tmp/amanda on Server is empty
> 
> On Client there are 1260 files namend
> 
> Amandad.xxxxxxx.debug
> 
> Amrecover.xxxxxx.debug
> 
> Runtar.xxxxxxx.debug
> 
> Selfcheck._dir.xxxxx.debug
> 
> Sendbackup.xxxxxx.debug
> 
> Sendsize.xxxxxx.debug
> 
> An amrecover entry looks like this
> 
> amrecover: debug 1 pid 21327 ruid 0 euid 0: start at Fri Nov 26 13:25:44
> 2004
> amrecover: stream_client_privileged: connect to 192.168.10.95.10082
failed:
> Connection refused
> amrecover: cannot connect to 192.168.10.95: Connection refused
> amrecover: pid 21327 finish time Fri Nov 26 13:25:44 2004

And do you have xinetd entries for amindexd and amidxtaped on the server?  
What does '/sbin/chkconfig --list' look like on the server?

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