It's not a .amandahosts problem.

Check the xinetd configuration for the amindexd service.
Check system log for xinetd error.

Jean-Louis

Johan Booysen wrote:

Hope someone can help me out here.

I'm testing Amanda 2.5.0 on RHEL5, to upgrade from our older version.

Everything went well and I can successfully back up older clients.

However, when trying to do an amrecover (as root and to the backup
server itself), using the config I've set up (called "daily"), I
consistently get:

# amrecover daily
AMRECOVER Version 2.5.0p2. Contacting server on amandahost ...
amrecover: cannot connect to amandahost: Success

This happens even when I remove the "amandahost" entry from
.amandahosts...

My understanding has always been that /var/lib/amanda/.amandahosts
dictates access to the server when using amrecover, and my .amandahosts
file is "suitably" modified with FQDNs and so on.

Am I missing something?

Thanks.