Re: amandahostsauth failed
Luis Rodrigues wrote: > Hi, > > I've setup a Debian system to act as the backup server. Have some clients > running debian > with i could make to work without problems. > > But my redhat clients don't want to work, I get: > ERROR: client.aa.aa : [access as amanda not allowed from [EMAIL PROTECTED] > amandahostsauth failed > but e correctly put in /var/lib/amanda/.amandahosts the line server.aa.aa > backup > the file is owned by amanda so I think its not permissions. > > Does anyone have an ideia. Not only does it have to be owned by the user Amanda is running as, I believe it also requires permissions to be 0600, so check that. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amandahostsauth failed
On 2006-05-05 16:19, Luis Rodrigues wrote: Hi, I've setup a Debian system to act as the backup server. Have some clients running debian with i could make to work without problems. But my redhat clients don't want to work, I get: ERROR: client.aa.aa : [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed but e correctly put in /var/lib/amanda/.amandahosts the line server.aa.aa backup the file is owned by amanda so I think its not permissions. Does anyone have an ideia. http://wiki.zmanda.com/index.php/Amcheck:_access_as_localuser_not_allowed_from_remoteuser%40remotehost The .amandahosts file probably should contain the remote user "backup" it defaults to the local user if empty (which seems to be "amanda" in your case). server.aa.aa backup -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amandahostsauth failed
Hi, vlpg, on Samstag, 02. April 2005 at 23:52 you wrote to amanda-users: v> Thank You. The backup is working... v> but when I try to restore it, it isn't working... v> foghorn:~#amrecover v> AMRECOVER Version 2.4.4p3. Contacting server on localhost ... v> 220 foghorn AMANDA index server (2.4.4p3) ready. v> 500 Access not allowed: [access as backup not allowed from v> [EMAIL PROTECTED] amandahostsauth failed v> Do someone have some hint ? For the archives : http://www.amanda.org/docs/topten.html#id2519209 Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amandahostsauth failed
--On Saturday, April 02, 2005 18:52:28 -0300 vlpg <[EMAIL PROTECTED]> wrote: > Thank You. The backup is working... > but when I try to restore it, it isn't working... > > foghorn:~#amrecover > AMRECOVER Version 2.4.4p3. Contacting server on localhost ... > 220 foghorn AMANDA index server (2.4.4p3) ready. > 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] > amandahostsauth failed > > Do someone have some hint ? First, don't use 'localhost' in your disklist or anywhere else, it will cause problems later (see the list archives for full discussions of why). Second, on the Amanda server (which could also be a client) you need to add a line to your .amandahosts file for each client to allow root to restore from that client: client.domain root If you really need to restore the backup you just made, using locahost would work if the client is also the server, but is NOT recommended. localhost won't work if the client is on a different machine, or if someday you change servers. Frank > > Thanks for the help - Vinicius -- Frank Smith[EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amandahostsauth failed
Thank You. The backup is working... but when I try to restore it, it isn't working... foghorn:~#amrecover AMRECOVER Version 2.4.4p3. Contacting server on localhost ... 220 foghorn AMANDA index server (2.4.4p3) ready. 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed Do someone have some hint ? Thanks for the help - Vinicius
Re: amandahostsauth failed
--On Saturday, April 02, 2005 17:08:19 -0300 vlpg <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm trying to configure a backup server, but it isn't working... > > My client is 192.168.20.81 and my server is 192.168.20.156 > I want to make the back of /tmp and /etc > > My client's port: > 10080/tcp closed unknown > 10081/tcp closed unknown > 10082/tcp closed amandaidx > 10083/tcp closed amidxtape > > My server's port: > 111/tcp open rpcbind > 113/tcp open auth > 916/tcp open unknown > 10080/tcp closed unknown > 10081/tcp closed unknown > 10082/tcp open amandaidx > 10083/tcp open amidxtape > > My log file is (I change my domain): > START driver date 20050402 > DISK planner 192.168.20.81 /etc > DISK planner 192.168.20.81 /tmp > START planner date 20050402 > INFO planner Adding new disk 192.168.20.81:/etc. > INFO planner Adding new disk 192.168.20.81:/tmp. > ERROR planner 192.168.20.81: [access as backup not allowed from [EMAIL > PROTECTED] amandahostsauth failed > FINISH planner date 20050402 > WARNING driver WARNING: got empty schedule from planner > STATS driver startup time 0.184 > START taper datestamp 20050402 label HISS04 tape 0 > INFO taper tape HISS04 kb 0 fm 0 [OK] > FINISH driver date 20050402 time 0.351 > > I have add the client ip in the server's /etc/hosts.allow > > Had someone a hint ? You need an .amandahosts file on the client (in your backup user's home directory, and not world readable) containing: foghorn.MYDOMAINbackup and remember to replace MYDOMAIN with whatever was in the 'ERROR' message you quoted above. Frank > > Thanks for the help - Vinicius > > > -- Frank Smith[EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
[Fwd: Re: amandahostsauth failed]
thanks, That solved the problem. ddaas ddaasd wrote: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need to add the line server root to the file ~amanda/.amandahosts . Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
RE: amandahostsauth failed
Sorry wrong URL. It was http://www.amanda.org/docs/topten.html I ran into the same problem. I believe the answer was in Amanda FAQ @ http://www.amanda.org/docs/faq.html Jim Scheuerman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ddaasd Sent: Tuesday, February 22, 2005 11:18 AM To: amanda-users@amanda.org Subject: amandahostsauth failed The problem was amandaidx from xinetd. Now the error message looks like: (root)#amrecover -C myconfig -s 192.168.0.2 AMRECOVER Version 2.4.4p1. Contacting server on 192.168.0.2 ... 220 backup AMANDA index server (2.4.4p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed :( <>Hi list, <>I am stuck with amrecover. <>I want to recover data from my tapes. <>On the backed up client (the host from the disklist file) I run amrestore. <>I get the following error message: <> <>AMRECOVER Version 2.4.4p1. Contacting server on localhost ... <>amrecover: cannot connect to localhost: Connection refused <> <>I also tried #amrecover -C myconfig -s IP_OF_THE_BACKUP_SERVER <> <>I receive the same message. <> <>How can I restore my backups? What do I do wrong? <> <> <>ddaas
RE: amandahostsauth failed
I ran into the same problem. I believe the answer was in Amanda FAQ @ http://www.amanda.org/docs/faq.html Jim Scheuerman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ddaasd Sent: Tuesday, February 22, 2005 11:18 AM To: amanda-users@amanda.org Subject: amandahostsauth failed The problem was amandaidx from xinetd. Now the error message looks like: (root)#amrecover -C myconfig -s 192.168.0.2 AMRECOVER Version 2.4.4p1. Contacting server on 192.168.0.2 ... 220 backup AMANDA index server (2.4.4p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed :( <>Hi list, <>I am stuck with amrecover. <>I want to recover data from my tapes. <>On the backed up client (the host from the disklist file) I run amrestore. <>I get the following error message: <> <>AMRECOVER Version 2.4.4p1. Contacting server on localhost ... <>amrecover: cannot connect to localhost: Connection refused <> <>I also tried #amrecover -C myconfig -s IP_OF_THE_BACKUP_SERVER <> <>I receive the same message. <> <>How can I restore my backups? What do I do wrong? <> <> <>ddaas
Re: amandahostsauth failed
Hi, Kristian, on Dienstag, 24. Februar 2004 at 13:00 you wrote to amanda-users: >> backer.domain.xyz backup KR> Hmmm, that did it! Actually, removing "localhost" from the KR> amandahosts helped much, and now the whole system seems to do KR> something. Goood - thanks a lot! :)) The good old localhost-question. ;) KR> Btw: Where to post a new amanda tapetype definition for the FAQs? You could add it to the FAQ at http://amanda.sourceforge.net/fom-serve/cache/45.html Check if it is necessary to add it, because it is likely that the tapetype is already in there. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amandahostsauth failed
Hi Stefan et al,... On Tue, 24 Feb 2004 12:45:17 +0100 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote: > > backer backup > > even better > > backer.domain.xyz backup Hmmm, that did it! Actually, removing "localhost" from the amandahosts helped much, and now the whole system seems to do something. Goood - thanks a lot! :)) Btw: Where to post a new amanda tapetype definition for the FAQs? Cheers, Kris -- Kristian Rink -- Programmierung/Systembetreuung planConnect GmbH * Strehlener Str. 12 - 14 * 01069 Dresden 0176 24472771 * [EMAIL PROTECTED]
Re: amandahostsauth failed
Hi, Kristian, on Dienstag, 24. Februar 2004 at 11:42 you wrote to amanda-users: KR> ...slowly getting my amanda system to work with our tape libary, by KR> now I am still not able to dump any data to tape. In the end, amdump KR> each and every time fails with KR> ERROR planner localhost: [access as backup not allowed from KR> [EMAIL PROTECTED] amandahostsauth failed KR> I found some solutions to amandahostsauth failures while googling KR> around, modified both the /etc/amandahosts and KR> /var/backups/.amandahosts file in several ways and yet haven't KR> found a working solution for that problem. Amanda is only running on KR> one single server (Debian testing) and is configured to just dump a KR> huge drive connected right to that server, so there's just one host KR> involved in this configuration. Can anyone point me a direction to KR> success? :) What do you have in your .amandahosts? Where is it? Should go to ~backup and look like backer backup even better backer.domain.xyz backup (FQDN - fully qualified hostname) As the client connects as the dump-user (which seems to be backup in your setup), amandad has got to let it in and looks it up in ~dumpuser/.amandahosts -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amandahostsauth failed
>On Thu, Jan 23, 2003 at 09:17:43AM -0700, Santiago wrote: >> ... >> ERROR: scratchy: [access as amanda not allowed from amanda@backup] amandahostsauth >failed >> ... >Make sure that the entry in scratchy's /etc/hosts file has the fully >quallified domain name of the backup machine. ... If that doesn't help, perhaps an explanation of what that message says will. It says user "amanda" from the host "backup" (amanda@backup) tried to authenticate. To do that, you have to have those values **exactly** as it says in the message in your .amandahosts file. Assuming what you posted is *precisely* what you got, you need: backup amanda Note that the "backup" host name is not qualified. That, in turn, implies some other things (see below), but maybe this will get you going. >Simon. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] And now for the "more than you ever wanted to know section" ... :-) When amandad is fired up on the client (scratchy), all it gets is an IP address of the connecting host. It does a "reverse" (gethostbyaddr) lookup to determine the connecting host name. It uses the "primary" (first) name returned to do the lookup in .amandahosts. This is standard coding practice for doing such lookups. If you're using /etc/hosts for host name/IP resolution, the order of names on a line matters -- the first name is the "primary" and will be used by most code for lookups. So, for instance, let's say you have a machine named "real-host" in your domain "my.domain". And let's say that for convenience you want to give it an alias of "backup". If you enter that like this: 11.22.33.44 backup backup.my.domain real-host real-host.my.domain ... a lookup (gethostbyname) of *any* of the names will return the same IP number (11.22.33.44). But a reverse lookup of 11.22.33.44 will return "backup", which is probably not what you want (it actually returns all the names, but most code only uses the first). You probably want to get back the fully qualified "real" name. So the line should be: 11.22.33.44 real-host.my.domain real-host backup.my.domain backup In my experience, the standard practice is to list the fully qualified "real" host name first. Order doesn't really matter after that, but it's more human-readable to list the related aliases, then other fully qualified names and aliases. I wrote a couple of tiny tools to help test all this out: ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c They will help you ask questions and get the same thing back Amanda (or other software) does from these standard system calls. And my apologies if this is all well known to you. I tend to ramble a bit at times :-).
Re: amandahostsauth failed
On Thu, Jan 23, 2003 at 09:17:43AM -0700, Santiago wrote: > Thanks so much to everyone responding to my first question. I got that > fixed right away. However, I am still running into the following issue. > Possibly my configuration is poor . .. > > the error is: > > Amanda Backup Client Hosts Check > > ERROR: scratchy: [access as amanda not allowed from amanda@backup] > amandahostsauth failed > Client check: 3 hosts checked in 0.020 seconds, 1 problem found > > (brought to you by Amanda 2.4.3) Make sure that the entry in scratchy's /etc/hosts file has the fully quallified domain name of the backup machine. For example: xxx.xxx.xxx.xx scratchy.yourdomain.org scratchy That ought to fix it :-) Simon.
Re: amandahostsauth failed
OK, it turned out to be the fully qualified (vs not) name in
.amandahosts.
I changed to just use the short name (which is what was used in the
amanda error message and amcheck doesn't give any errors now.
I found this in the faq-o-matic.
gene
On Mon, 2002-02-04 at 10:18, gene wrote:
> On Friday, I finally succeeded in getting Amanda to complete a
> successful backup run on the tape server. Today I'm trying to add a
> Linux (RH 7.2) client. I can't seem to get past the 'amanadahostauth
> failed' when running an amcheck.
>
> I have a .amandahosts file on the client (lincvs):
>
> datadev.mydomain.com amanda
>
> datadev is the tape server (Solaris 8). I do have ipchains running on
> lincvs and I have put in rules to allow ports 10080, 10082, and 10883
> thru. I have also stopped ipchains completely and run the amcheck from
> the tapeserver with the same results.
>
> Both datadev (tapeserver) and lincvs (client) are runing 2.4.2p2. The
> RedHat box (lincvs) is running with the amanda rpm's that came with 7.2.
> lincvs is
>
>
> I have run the C pgm from the O'Reilly B/U book that checks that the
> services are called correctly and that is ok (on both client and
> tapeserver).
>
> I'm sure I'm overlooking something, and I'm still digging through the
> faq-o-matic and any newsgroup searches, as well as looking at Chapter 4
> in the O'Reilly Backup and Recovery book. Any/all help is appreciated.
>
> The amcheck output from the tapeserver is below. I know I need to do a
> amrmtape to re-use the DailySet101 tape below while I'm testing):
>
> {datadev:amanda}$ amcheck Daily
> Amanda Tape Server Host Check
> -
> Holding disk /backup/amanda: 11432812 KB disk space available, that's
> plenty
> ERROR: cannot overwrite active tape DailySet101
>(expecting tape DailySet102 or a new tape)
> NOTE: skipping tape-writable test
> NOTE: info dir /var/amanda/DailySet1/curinfo/lincvs.mydomain.com: does
> not exist
> Server check took 3.784 seconds
>
> Amanda Backup Client Hosts Check
>
> ERROR: lincvs.mydomain.com: [access as amanda not allowed from
> amanda@datadev] amandahostsauth failed
> Client check: 2 hosts checked in 0.098 seconds, 1 problem found
>
> (brought to you by Amanda 2.4.2p2)
>
>
> Thanks for your help!
>
>
> Gene
>
>
>
>
>
>
>
> --
> Gene Matthews
> Matthews Midrange Consulting, Inc.
> (678) 923-8327
> (877) 882-6291 (toll free)
> http://mmc-inc.com
>
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
Re: amandahostsauth failed
OK, it turned out to be the fully qualified (vs not) name in
.amandahosts.
I changed to just use the short name (which is what was used in the
amanda error message and amcheck doesn't give any errors now.
I found this in the faq-o-matic.
gene
On Mon, 2002-02-04 at 10:18, gene wrote:
> On Friday, I finally succeeded in getting Amanda to complete a
> successful backup run on the tape server. Today I'm trying to add a
> Linux (RH 7.2) client. I can't seem to get past the 'amanadahostauth
> failed' when running an amcheck.
>
> I have a .amandahosts file on the client (lincvs):
>
> datadev.mydomain.com amanda
>
> datadev is the tape server (Solaris 8). I do have ipchains running on
> lincvs and I have put in rules to allow ports 10080, 10082, and 10883
> thru. I have also stopped ipchains completely and run the amcheck from
> the tapeserver with the same results.
>
> Both datadev (tapeserver) and lincvs (client) are runing 2.4.2p2. The
> RedHat box (lincvs) is running with the amanda rpm's that came with 7.2.
> lincvs is
>
>
> I have run the C pgm from the O'Reilly B/U book that checks that the
> services are called correctly and that is ok (on both client and
> tapeserver).
>
> I'm sure I'm overlooking something, and I'm still digging through the
> faq-o-matic and any newsgroup searches, as well as looking at Chapter 4
> in the O'Reilly Backup and Recovery book. Any/all help is appreciated.
>
> The amcheck output from the tapeserver is below. I know I need to do a
> amrmtape to re-use the DailySet101 tape below while I'm testing):
>
> {datadev:amanda}$ amcheck Daily
> Amanda Tape Server Host Check
> -
> Holding disk /backup/amanda: 11432812 KB disk space available, that's
> plenty
> ERROR: cannot overwrite active tape DailySet101
>(expecting tape DailySet102 or a new tape)
> NOTE: skipping tape-writable test
> NOTE: info dir /var/amanda/DailySet1/curinfo/lincvs.mydomain.com: does
> not exist
> Server check took 3.784 seconds
>
> Amanda Backup Client Hosts Check
>
> ERROR: lincvs.mydomain.com: [access as amanda not allowed from
> amanda@datadev] amandahostsauth failed
> Client check: 2 hosts checked in 0.098 seconds, 1 problem found
>
> (brought to you by Amanda 2.4.2p2)
>
>
> Thanks for your help!
>
>
> Gene
>
>
>
>
>
>
>
> --
> Gene Matthews
> Matthews Midrange Consulting, Inc.
> (678) 923-8327
> (877) 882-6291 (toll free)
> http://mmc-inc.com
>
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
Re: amandahostsauth failed
>ERROR: daphne: [access as amanda not allowed from amanda@daphne] >amandahostsauth failed >*** > >Is this a point of trouble with rsh? No. Amanda does not use rsh. >I create in: > >/export/home/amanda/.amandahosts > >containing: > >daphne.webcom.de amanda >helena.webcom.de amanda Read the amcheck message carefully. The host name it reports is "daphne" rather than "daphne.webcom.de". So you need this in the file: daphne amanda However, this error might indicate a system misconfiguration on daphne. It says that when Amanda (or any other program) does a reverse lookup of the IP address for daphne, it does not get back a fully qualified host name. That's usually a bad thing, and you need to talk to whoever set up your name system (DNS, /etc/hosts or whatever) about why that is happening. >Bernd John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
