amandahostsauth failed
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.
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
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
amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
Hi I have checked my FQDN entries in /var/lib/amanda/.amandahosts I have the correct entries in my /etc/hosts file. I have the three services in my /etc/xinet.d file amanda , amandaidx and amidxtape and I am running amrevoce as root Any ideas as I am not running it as amanda. server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
Hi I had a look at # less amrecover.20050516105131.debug amrecover: debug 1 pid 25626 ruid 0 euid 0: start at Mon May 16 10:51:31 2005 amrecover: stream_client_privileged: connected to 192.168.1.55.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.829 amrecover.20050516105131.debug lines 1-3/3 (END) Also # less amindexd.20050516105131.debug amindexd: debug 1 pid 25627 ruid 1014 euid 1014: start at Mon May 16 10:51:31 2005 amindexd: version 2.4.4p4 amindexd: time 0.000: 220 server AMANDA index server (2.4.4p4) ready. amindexd: time 0.000: SECURITY USER root amindexd: time 0.001: bsd security: remote host server.domain.co.uk user root local user amanda amindexd: time 0.001: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 200 Good bye. amindexd: time 0.001: pid 25627 finish time Mon May 16 10:51:31 2005 I am running as root My ~amanda /.amandahost file is as follows server.domain.co.uk amanda server.domain.co.uk root /etc/hosts file 192.168.X.XX server.domain.co.uk server On Mon, 2005-05-16 at 08:25 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: amrecover Error 500 Access not allowed: [access as amanda notallowed from [EMAIL PROTECTED] amandahostsauth failed
Chuck, You need both client and server machines listed in the .amandahosts file on the server. Currently you've only got the one server listed there. talk to you soon mate Matt on 16/05/2005 16:09 Chuck Amadi said the following: Hi I had a look at # less amrecover.20050516105131.debug amrecover: debug 1 pid 25626 ruid 0 euid 0: start at Mon May 16 10:51:31 2005 amrecover: stream_client_privileged: connected to 192.168.1.55.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.829 amrecover.20050516105131.debug lines 1-3/3 (END) Also # less amindexd.20050516105131.debug amindexd: debug 1 pid 25627 ruid 1014 euid 1014: start at Mon May 16 10:51:31 2005 amindexd: version 2.4.4p4 amindexd: time 0.000: 220 server AMANDA index server (2.4.4p4) ready. amindexd: time 0.000: SECURITY USER root amindexd: time 0.001: bsd security: remote host server.domain.co.uk user root local user amanda amindexd: time 0.001: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 200 Good bye. amindexd: time 0.001: pid 25627 finish time Mon May 16 10:51:31 2005 I am running as root My ~amanda /.amandahost file is as follows server.domain.co.uk amanda server.domain.co.uk root /etc/hosts file 192.168.X.XX server.domain.co.uk server On Mon, 2005-05-16 at 08:25 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- *Matthew Claridge* Product Support Engineer RWA Limited Direct line: 02920 815 054 Email: [EMAIL PROTECTED] Web: www.rwa-net.co.uk
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]
amandahostsauth failed
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 ? 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
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 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
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
[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
amandahostsauth failed
Hi all,... ...slowly getting my amanda system to work with our tape libary, by now I am still not able to dump any data to tape. In the end, amdump each and every time fails with ERROR planner localhost: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed I found some solutions to amandahostsauth failures while googling around, modified both the /etc/amandahosts and /var/backups/.amandahosts file in several ways and yet haven't found a working solution for that problem. Amanda is only running on one single server (Debian testing) and is configured to just dump a huge drive connected right to that server, so there's just one host involved in this configuration. Can anyone point me a direction to success? :) TIA and bye, 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
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 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]
ERROR: u07: [access as amanda not allowed from amanda@u03] amandahostsauth failed
I'm trying to backup the machine u07 from u07 (the one with the tape drive). I'm getting a ash-2.00$ amcheck daily Amanda Tape Server Host Check - Holding disk /Disk2/AMANDA: 3376999 KB disk space available, that's plenty ERROR: cannot overwrite active tape DailySet101 (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/adm/amanda/DailySet1/curinfo/u07: does not exist NOTE: index dir /usr/adm/amanda/DailySet1/index/u07: does not exist Server check took 0.117 seconds Amanda Backup Client Hosts Check ERROR: u07: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Client check: 2 hosts checked in 1.405 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) I have a line for the amanda users in .amandahosts on u03: u07 amanda and on u07 in /etc/services: amanda 10080/udp # amanda I have the following debug info on u07 in /tmp/amanda: bash-2.03$ cat /tmp/amanda/amandad.20040128135031.debug amandad: debug 1 pid 6646 ruid 400 euid 400: start at Wed Jan 28 13:50:31 2004 amandad: version 2.4.4p1 amandad: build: VERSION=Amanda-2.4.4p1 amandad:BUILT_DATE=Fri Nov 28 18:42:47 WET 2003 amandad:BUILT_MACH=SunOS u07 5.8 Generic_108528-13 sun4u sparc SUNW,UltraAX-i2 Solaris amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=sys' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ amandad:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump amandad:RESTORE=/usr/sbin/ufsrestore GNUTAR=/usr/local/bin/tar amandad:COMPRESS_PATH=/usr/local/bin/gzip amandad:UNCOMPRESS_PATH=/usr/local/bin/gzip amandad:MAILER=/usr/ucb/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=u07 DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=u07 DEFAULT_TAPE_DEVICE=/dev/null amandad:HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID amandad:DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 001-0003EF18 SEQ 1075294975 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 001-0003EF18 SEQ 1075294975 amandad: time 0.002: bsd security: remote host u03 user amanda local user amanda amandad: time 0.002: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amandad: time 0.002: sending REP packet: Amanda 2.4 REP HANDLE 001-0003EF18 SEQ 1075294975 ERROR [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amandad: time 0.004: got packet: Amanda 2.4 ACK HANDLE 001-0003EF18 SEQ 1075294975 amandad: time 0.004: pid 6646 finish time Wed Jan 28 13:50:31 2004
Re: ERROR: u07: [access as amanda not allowed from amanda@u03] amandahostsauth failed
--On Wednesday, January 28, 2004 13:52:10 +0100 Eugen Leitl [EMAIL PROTECTED] wrote: I'm trying to backup the machine u07 from u07 (the one with the tape drive). I'm getting a ash-2.00$ amcheck daily Amanda Tape Server Host Check - Holding disk /Disk2/AMANDA: 3376999 KB disk space available, that's plenty ERROR: cannot overwrite active tape DailySet101 (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/adm/amanda/DailySet1/curinfo/u07: does not exist NOTE: index dir /usr/adm/amanda/DailySet1/index/u07: does not exist Server check took 0.117 seconds Amanda Backup Client Hosts Check ERROR: u07: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Client check: 2 hosts checked in 1.405 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) I have a line for the amanda users in .amandahosts on u03: u07 amanda You need a line for the server in the .amandahosts on the client, so in your case need the following line in your .amandahosts on u07: u03 amanda Frank and on u07 in /etc/services: amanda 10080/udp # amanda I have the following debug info on u07 in /tmp/amanda: bash-2.03$ cat /tmp/amanda/amandad.20040128135031.debug amandad: debug 1 pid 6646 ruid 400 euid 400: start at Wed Jan 28 13:50:31 2004 amandad: version 2.4.4p1 amandad: build: VERSION=Amanda-2.4.4p1 amandad:BUILT_DATE=Fri Nov 28 18:42:47 WET 2003 amandad:BUILT_MACH=SunOS u07 5.8 Generic_108528-13 sun4u sparc SUNW,UltraAX-i2 Solaris amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=sys' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ amandad:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump amandad:RESTORE=/usr/sbin/ufsrestore GNUTAR=/usr/local/bin/tar amandad:COMPRESS_PATH=/usr/local/bin/gzip amandad:UNCOMPRESS_PATH=/usr/local/bin/gzip amandad:MAILER=/usr/ucb/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=u07 DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=u07 DEFAULT_TAPE_DEVICE=/dev/null amandad:HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID amandad:DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 001-0003EF18 SEQ 1075294975 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 001-0003EF18 SEQ 1075294975 amandad: time 0.002: bsd security: remote host u03 user amanda local user amanda amandad: time 0.002: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amandad: time 0.002: sending REP packet: Amanda 2.4 REP HANDLE 001-0003EF18 SEQ 1075294975 ERROR [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amandad: time 0.004: got packet: Amanda 2.4 ACK HANDLE 001-0003EF18 SEQ 1075294975 amandad: time 0.004: pid 6646 finish time Wed Jan 28 13:50:31 2004
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 :-).
amandahostsauth failed
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) The backup server is multihomed to enable it to backup 2 network segments. The machine scratchy has the same .amandahosts in /home/amanda as other hosts that pass the check. The only difference between scratchy and the other hosts is that scratchy is on a different network segment. One network segment is a private lan with private IPs that is natted to the real world. The other segment has public IP addresses. I get the same error whether or not the backup server is multihomed to both networks or not. The scratchy client was compiled (and recompiled) with ./configure --with-user=amanda --with-group=amanda --without-server. The default amandahosts enabled was left alone (this worked on the other 2 clients). IPtable, IPchains, etc. is not running on the machine and it is set up to allow amanda in /etc/hosts.allow. Ideas? TIA, Santiago
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: ERRROR: linux1: [access as amanda not allowed from amanda@Linux2.igorsputerfarm.local] amandahostsauth failed
Well, it worked. I suppuse this was the one combination I overlooked Thanks a lot. Igor. --- Jordi Vidal [EMAIL PROTECTED] wrote: ERRROR: linux1: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth Try: Linux2.igorsputerfarm.local amanda If it doen't work then is a name resolution problem, check dns or /etc/hosts and ensure that .amandahosts is in the amanda user home (home/amanda for me). Regards. PS: You will probably need also an entry for root in the tapeserver's .amadahosts to run amrecover from clients. Linux1.igorsputerfarm.local root _ Descargue GRATUITAMENTE MSN Explorer en http://explorer.yupimsn.com/intl.asp __ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/
Re: ERRROR: linux1: [access as amanda not allowed from amanda@Linux2.igorsputerfarm.local] amandahostsauth failed
ERRROR: linux1: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Frank Smith gave you the right reading on this and what should go into your .amandahosts file. You already have this line: linux2.igorsputerfarm.local Without a user name in the second column, Amanda will default to who it is running as. If you set up inetd/xinetd to run it as amanda, this should work. And I *think* (but don't recall exactly when it went into the code) that case does not matter, i.e. linux2 and Linux2 should match. But that might be another thing to try since you didn't say what version of Amanda you're using. However ... Here is the /var/lib/amanda/.amandahost file. ... Is /var/lib/amanda the home directory for user amanda? Who owns the .amandahosts file and what are the modes? It should be owned by amanda and mode 0600 (or 0400). Does amanda have access to the file through the parent directories? Can you do this: # su - amanda -c cat .amandahost Finally, take a look at the corresponding /tmp/amanda/amandad*debug file on the client. It may have more diagnostic messages. Igor John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
ERRROR: linux1: [access as amanda not allowed from amanda@Linux2.igorsputerfarm.local] amandahostsauth failed
Hi All: OK, I give up. I am using RedHat Linux 7.1 I keep getting this error when I am running: bash $ amcheck Linux1Set Here's the story: Domain name: igorsputerfarm.local Linux2 - tape server Linux1 - backup client. I have Linux1Set configuration on the server (linux2) disklistis: linux1 /dev/hda1 dump-comp-serv Linux1Set config is on the tape server (linux2) when I ran amcheck Linux1Set on the server I get this error: ERRROR: linux1: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed I am running this command as amanda user Here is the /var/lib/amanda/.amandahost file. It is on the client (linux1). I can't thing of any other conbination. HELP! localhost amanda localhost.localdomain amanda localhost [EMAIL PROTECTED] localhost.localdomain [EMAIL PROTECTED] Linux2 amanda Linux2 [EMAIL PROTECTED] linux2.igorsputerfarm.local [EMAIL PROTECTED] linux2 amanda@linux2 linux2.igorsputerfarm.local amanda@linux2 linux1 amanda linux1.igorsputerfarm.local amanda linux1 [EMAIL PROTECTED] linux1.igorsputerfarm.local [EMAIL PROTECTED] [EMAIL PROTECTED] amanda [EMAIL PROTECTED] [EMAIL PROTECTED] linux1 Linux2.igorsputerfarm.local linux1 amanda.linux2.igorsputerfarm.local Thanks Igor __ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/
Re: ERRROR: linux1: [access as amanda not allowed from amanda@Linux2.igorsputerfarm.local] amandahostsauth failed
--On Saturday, March 23, 2002 21:40:49 -0800 Mr Igor Vertiletsky [EMAIL PROTECTED] wrote: when I ran amcheck Linux1Set on the server I get this error: ERRROR: linux1: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Whenever you get an error like that, look at the string containing the @, put what follows the @ on the left and what's before the @ on the right, and don't put the @ itself anywhere. For example, your error contains [EMAIL PROTECTED], so your line in .amandahosts should be: Linux2.igorsputerfarm.local amanda Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
amandahostsauth failed
I'm getting the following error on amcheck: ERROR: crypto-gw.irs.dev: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed my .amandahosts file: crypto-gw% cat /usr/home/amanda/.amandahosts crypto-gw.irs.dev amanda relay.irs.dev amanda crypto-gw% ls -al /usr/home/amanda/.amandahosts -rw--- 1 amanda operator 47 Feb 20 07:46 /usr/home/amanda/.amandahosts crypto-gw% my /etc/inetd.conf: crypto-gw% cat /etc/inetd.conf | grep amandad amanda dgram udp waitamanda /usr/local/libexec/amandad amandad I've looked at the FAQ and nothing there jumps out at me as to what's wrong. Any ideas?
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
amandahostsauth failed
Hi All, i did some amcheck getting this message: *** Amanda Backup Client Hosts Check ERROR: daphne: [access as amanda not allowed from amanda@daphne] amandahostsauth failed *** Is this a point of trouble with rsh? what do i have to do with it? I create in: /export/home/amanda/.amandahosts containing: daphne.webcom.deamanda helena.webcom.deamanda tanxs for some hints (not hits) :-) Bernd
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
On Thursday 15 February 2001 09:06, Gerhard den Hollander wrote: You get a message saying Banzai ! Did you install the WWII - japanese slang add-on to Amanda ? [Just kidding] ; Ehm do you have the .amandahosts in user amandas homedir ? or only in roots homedir ? In amandas home dir. root doesn't even have .amandahosts The amanda FAQ (docs/FAQ in the source tree) sez this Q: Why does `amcheck' say `access as username not allowed...' A: There must be something wrong with .amandahosts configuration (or .rhosts, if you have configured --without-amandahosts). That I know. But, the fact is there's nothing wrong with it. I have about two dozen machines setup in exactly the same way that this one is. All of them work... This is because I compiled amanda client and made a tgz package that I install on each machine... And then change the .amandahosts file... Make sure you specify the names exactly as they appear in the error message after the `@' sign in .amandahosts/.rhosts. You'll need a fully-qualified domain name or not, depending on how your client resolves IP addresses to host names. Well I'll double check, but I can be pretty sure that everything is setup exactly like it is on all the other hosts. -- David Klasinc Turbolinux Inc. http://www.turbolinux.com
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
On Feb 15, 2001, David Klasinc [EMAIL PROTECTED] wrote:
if I do it as user amanda, then it fails. I have users root and amanda in
.amandahosts.
What are the exact contents of .amandahosts on the client?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
Banzai! I get the above message when trying to backup one specific host. Client and server are bot v2.4.2 and if I do amcheck as root then everything works fine, if I do it as user amanda, then it fails. I have users root and amanda in .amandahosts. Any ideas what could be wrong? Thanks, -- David Klasinc Turbolinux Inc. http://www.turbolinux.com
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
* David Klasinc [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 08:53:33AM +0100) Banzai! I get the above message when trying to backup one specific host. Client and You get a message saying Banzai ! Did you install the WWII - japanese slang add-on to Amanda ? [Just kidding] server are bot v2.4.2 and if I do amcheck as root then everything works fine, if I do it as user amanda, then it fails. I have users root and amanda in ..amandahosts. Any ideas what could be wrong? Ehm do you have the .amandahosts in user amandas homedir ? or only in roots homedir ? The amanda FAQ (docs/FAQ in the source tree) sez this Q: Why does `amcheck' say `access as username not allowed...' A: There must be something wrong with .amandahosts configuration (or .rhosts, if you have configured --without-amandahosts). First, if the username is not what you expect (i.e., not what you have specified in the --with-user flag, at configure time), check the inetd configuration file: you must have specified the wrong username there. Make sure you specify the names exactly as they appear in the error message after the `@' sign in .amandahosts/.rhosts. You'll need a fully-qualified domain name or not, depending on how your client resolves IP addresses to host names. HTH Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Also by the time I'm 60, I want to get better at the art of living. =`\, And still be riding an acoustic motorbike. (=)/(=) -- not exactly Mark Knopfler
