Hi, thanks.

I've followed your advise to the point of nslookup, I get a correct reply
for the IP, but for the name 'merlin', I get:
Server:        192.168.0.1       (which is our DNS server address)
Address:     192.168.0.1#53

** server can't find merlin: NXDOMAIN

What does this mean/where should I look for problems?

Thanks, Trevor.
----- Original Message -----
From: "Christoph Scheeder" <[EMAIL PROTECTED]>
To: "Trevor Fraser" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, August 01, 2002 1:35 PM
Subject: Re: Amrecover:access not allowed.


> Hi,
> first off all you'll have to find where amrecover/amidxd
> gets the strange name from.
>
> 1.) what result gives the command "hostname"?
> it should be merlin or your FQDN.
>
> 2.) your /etc/hosts should have the folowing two lines belonging
> to your computer:
>
> 127.0.0.1       localhost
> 192.168.0.2     merlin.systematic.lan   merlin
>
> if the first line contains other values: they are bad, so fix it.
>
> next do a nslookup on your hostname and your ip-adress.
> the results should be consistant, if not, fix your dns
> Christoph
>
> Trevor Fraser wrote:
>
> > Thank for the info.  /etc/hosts looks fine:
> > *amongst other entries*
> > 192.168.0.2        merlin.systematic.lan        merlin
> > One question: How do I fix the name service to show the correct name for
> > this box, is this the named?
> > Thanks, Trevor.
> > p.s. I did add localhost.localdomain root to the .amandahosts file, no
> > change yet.
> >
> > ----- Original Message -----
> > From: "Christoph Scheeder" <[EMAIL PROTECTED]>
> > To: "Trevor Fraser" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 01, 2002 10:36 AM
> > Subject: Re: Amrecover:access not allowed.
> >
> >
> >
> >>hi,
> >>for an unknown reason amrecover conects to your server with the name
> >>[EMAIL PROTECTED]
> >>
> >>two solution's are possible:
> >>1.)you'll have to fix your /etc/host or nameservice to
> >>    show the correct hostname for this box or
> >>2.)add the line
> >>    localhost.localdomain root
> >>    to your .amandahosts file.
> >>
> >>i would suggest the 1st  solution as your broken nameservices/hosts
> >>probably will bite you again in the future.
> >>Christoph
> >>
> >>Trevor Fraser wrote:
> >>
> >>
> >>>Hello all.
> >>>
> >>>
> >>>
> >>>Last night my boss gave me a test to see if I can recover lost files
> >>>before copying everything from his computer to our amanda server( I
know
> >>>we could backup his computer too, but we've chosen to use samba to
store
> >>>files on a share here and backup this share).  Anyway, so I couldn't do
> >>>it, and obviously he isn't impressed.
> >>>
> >>>
> >>>
> >>>Anyway, the problem comes when I try 'amrecover' from the / directory.
> >>>The error is:
> >>>
> >>>
> >>>
> >>>[root@merlin /]# amrecover
> >>>
> >>>AMRECOVER Version 2.4.2p2.  Contacting server on localhost . . .
> >>>
> >>>220 merlin AMANDA index server (2.4.2p2) ready.
> >>>
> >>>500 Access not allowed: [ access as amanda not allowed from
> >>>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ]
> >>>amandahostsauth failed
> >>>
> >>>[ root@merlin /]#
> >>>
> >>>
> >>>
> >>>My amanda dumpuser is root, and in amanda, amandaidx and amidxtape are
> >>>user = amanda.
> >>>
> >>>My .amandahost looks like this:
> >>>
> >>>
> >>>
> >>>merlin.systematic.lan    root
> >>>
> >>>merlin.systematic.lan    amanda
> >>>
> >>>localhost.localdomain    amanda
> >>>
> >>>
> >>>
> >>>The file belong to root:root and has read and write privileges for the
> >>>user owner only.
> >>>
> >>>
> >>>
> >>>I've read the FAQ's and saw a similar problem, but with regard to
> >>>amcheck.  I can amcheck and amdump fine.  What is the next step in
> >>>troubleshooting?
> >>>
> >>>
> >>>
> >>>Thanks, Trevor.
> >>>
> >>>
> >>>
> >>>
> >
>

Reply via email to