On Mon, Feb 06, 2006 at 05:59:00PM -0500, Gene Heskett wrote:
> On Monday 06 February 2006 17:29, Josef Wolf wrote:

> >Any ideas why amrecover don't want to work?  Looks like it tries to
> > connect a server on localhost.  But whom is it trying to connect to
> > and why is it failing?
> 
> Please, localhost is NOT an FQDN, please reconfigure your installation 
> to use Fully Qualified Domain Names or their alias's if they listed in 
> the /etc/hosts file.

I have double checked:
- All the DLEs are specified with FQDN.
- "hostname -f" reports the fqdn as it should be.

What might be the reason that amrecover assumes localhost is the tape
server?  How comes that it automatically uses "hostname -f" for the
index server but fails to do the same for the tape server?  I bet that
on most installations the index server and the tape server are the same
box.  Wouldn't it make sense to default both to "hostname -f"?

> localhost has a fixed address of 127.0.0.1 on any 
> machine and will eat your lunch when trying to recover because its 
> always the box the recover is running on.  And that may not be the 
> server intended.

In this case I ran amrecover on the amanda server which by accident happens
to be both, the index server _and_ the tape server.

> >Extracting files from holding disk on host localhost.
> >The following files are needed:
> > /tmp/hold/20060206030502/host.do.main._var.0
> 
> Holding disk?

Yes.  The dumps were not flushed.

But this looks wired.  Isn't the holding disk always supposed to be on
the tape server?  So how comes that amrecover can contact the index server
and find the holding disk but can't find the tapes?

> Possibly the 'sethost' command might bail you out, but I've no 
> experience with this, so I'm not positive about it.

Unfortunately, the sethost command does _not_ set the tape server.  Only
the -t command line option seems to set it.


Thanks for the reply.