Moin Paul,

> Your localhost is actually called "schatten", and I guess that a
> dns lookup of "schatten" does not result in "localhost", nor in 127.0.0.1.

Hmm... you're right :-)

> Don't use "localhost" in disklist.  It will bit you.
> If you don't believe me, just just got bitten...

OK, I begin to understand... Any chance to resolve this situation
here?

I tried to re-manage all here: My "domain" at home is called "magnus"
(instead of something else, part of history, but this shouldn't affect
the problem, because DNS works well with that :->), so nslookup will
say:

Name:   schatten.magnus
Address: 10.10.10.1

1.10.10.10.in-addr.arpa name = schatten.magnus.

So, correct until here.


/etc/amandahosts:
schatten.magnus root
schatten root


disklist:
schatten.magnus /home/thoddi comp-user-tar


amcheck without any errors after renaming the "localhost"-dir in
"curinfo" and "index" (because they are the same, just hostnames
changed :->)


But:

schatten:~# amrecover Weekly -s schatten.magnus
AMRECOVER Version 2.4.2p2. Contacting server on schatten.magnus ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
amrecover: Unexpected server end of file

<#ß=(%*'-GRMPF-§"§$")='_:>    :-)

Why he told me "200 Access OK" first and will fail an few lines
after?

Syslog only said:
May 27 17:06:16 schatten amindexd[11901]: connect from 10.10.10.1


I first thougt about iptables blocking the connection, but the
packetfilter is working correct.


Is the backup gone away? No way to recover it?

-- 
Bis denne,
            Thoddi