Backup Central

Hi,

I've just upgraded my Mandrake 9.1 (under which I've had Amanda working
perfectly for many moons) to Mandrake 10.0. Amanda planner is now failing:

FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR tony-lx: [access as amanda not allowed from
amanda < at > tony-lx] amandahostsauth failed

I can't immediately find the solution in the docs, so can someone please
point me in the right direction for fixing trhis problem?

TIA, Tony

--
Tony van der Hoff | mailto:tony < at > mk-net.nildram.co.uk
Buckinghamshire England

On Wed, 30 Jun 2004 at 4:29pm, Tony van der Hoff wrote

I've just upgraded my Mandrake 9.1 (under which I've had Amanda working
perfectly for many moons) to Mandrake 10.0. Amanda planner is now failing:

FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR tony-lx: [access as amanda not allowed from
amanda < at > tony-lx] amandahostsauth failed

I can't immediately find the solution in the docs, so can someone please
point me in the right direction for fixing trhis problem?

This is probably in FAQ-O-MATIC, and certainly in the mailing list
archives. You need to have an entry in .amandahosts in the amanda user's
$HOME on the server that looks like this (given the above error message):

tony-lx amanda

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

Joshua Baker-LePain <jlb17 < at > duke.edu> wrote in message
<Pine.LNX.4.58.0406301459560.10588 < at > chaos.egr.duke.edu>

On Wed, 30 Jun 2004 at 4:29pm, Tony van der Hoff wrote

I've just upgraded my Mandrake 9.1 (under which I've had Amanda working
perfectly for many moons) to Mandrake 10.0. Amanda planner is now
failing:

FAILURE AND STRANGE DUMP SUMMARY:
planner: ERROR tony-lx: [access as amanda not allowed from
amanda < at > tony-lx] amandahostsauth failed

I can't immediately find the solution in the docs, so can someone please
point me in the right direction for fixing trhis problem?

This is probably in FAQ-O-MATIC, and certainly in the mailing list
archives. You need to have an entry in .amandahosts in the amanda user's
$HOME on the server that looks like this (given the above error message):

tony-lx amanda


Thanks, Joshua, for both your messages. There is really no need to respond
to both the list and directly. As I said, I've had Amanda working fine under
Mandrake 9.1, it was the upgrade to 10.0 that caused the problem. And, yes,
when I mentioned the docs, I did include FAQ-O-MATIC, and the archives.

Indeed I have that entry (and one for root, to allow amrecover) in
.amandahosts. However, you did give me cause to ensure that it was there :-)

Does anyone have any other suggestions?

--
Tony van der Hoff | mailto:tony < at > mk-net.nildram.co.uk
Buckinghamshire England

Tony van der Hoff wrote:
Indeed I have that entry (and one for root, to allow amrecover) in
.amandahosts. However, you did give me cause to ensure that it was there :-)

Does anyone have any other suggestions?

Did the use amanda's home directory change during the upgrade? So that
it wouldn't look for .amandahosts in the same place anymore?

Alex

--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29

On Wed, 30 Jun 2004 at 10:51pm, Tony van der Hoff wrote

Thanks, Joshua, for both your messages. There is really no need to respond
to both the list and directly. As I said, I've had Amanda working fine under

SOP. How do I know you're subscribed to the list?

Indeed I have that entry (and one for root, to allow amrecover) in
.amandahosts. However, you did give me cause to ensure that it was there :-)

And does the location of the properly filled in .amandahosts match $HOME
for the amanda user specified in /etc/passwd? Are the permissions right
(can the amanda user read it)? If all that checks out, look in
/tmp/amanda/amandad*debug for more detail on the exact error (and post the
contents here).

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

Joshua Baker-LePain <jlb17 < at > duke.edu> wrote in message
<Pine.LNX.4.58.0406301810450.10588 < at > chaos.egr.duke.edu>

[snip]

OK, it turnes out that the entry in .amandahosts now (since the upgrade)
requires the FQDN for tony-lx, i.e. tony-lx.magpieway.net. It now works. I
can't be bothered to chase this right through, but I suspect something has
changed in the way NIS is working.

Thanks for the pointer.

Cheers, Tony.

--
Tony van der Hoff | mailto:tony < at > mk-net.nildram.co.uk
Buckinghamshire England

On Thu, Jul 01, 2004 at 11:13:44AM +0100, Tony van der Hoff wrote:
OK, it turnes out that the entry in .amandahosts now (since the upgrade)
requires the FQDN for tony-lx, i.e. tony-lx.magpieway.net. It now works.

I've just had a similar adventure here. I've already solved it;
this post is for the benefit of the archives.

Without going into all the details, the solution to my problem
seems to be that if your Amanda server has multiple FQDNs, you
need to list *all* of them in .amandahosts on the clients, since
you have no control over which FQDN Amanda will think it needs to
look up on any given run. Whether this is necessary seems to
depend on the nameserver software that the Amanda *client* is
resolving against (i.e. which nameserver is running on the
host(s) listed in the client's /etc/resolv.conf).

Our Amanda server has two FQDNs. Our clients have been happily
getting backed up for a year, with only one of the server's FQDNs
in their .amandahosts files. But when I switched one client over
to our test BIND 9.2.3 nameserver (production is BIND 8.2.3),
that client started getting "amandahostsauth failed" errors until
I added a .amandahosts entry for the server's second FQDN.

To confirm this, I ran "amcheck -c" ten times. Two runs
succeeded, eight failed (same "amandahostsauth failed" error for
the same client). After I made the .amandahosts change on that
client, I ran 90 more "amcheck -c"'s; all of them succeeded.

It looks as though, when amandad(?) does a reverse lookup on the
Amanda server's IP address, the old BIND predictably returns one
of the host's FQDN's, but the new BIND can return either of them.

--

| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. erics < at > telepres.com
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau