Take a look in /tmp/amanda/amandad/debug. The config/defs section at the beginning has a bunch of flags in it. Look for "BSD_SECURITY" and "USE_AMANDAHOSTS". If you have the former and not the latter, everything that's been said about .amandahosts really applies to .rhosts, and no amount of fiddling with .amandahosts will make it work.
This is based on my install of 2.4.2-19991216, and only took me two days to track down. I think I'll go put something in FoM. > -----Original Message----- > From: KEVIN ZEMBOWER [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 11, 2001 10:03 AM > To: [EMAIL PROTECTED] > Subject: Re: Newbie: Can't get amanda user to work > > > Thank you to all the generous folks who have given me suggestions. > Unfortunately, I still can't get it to work. I still get the > same error > massage with "[access as amanda not allowed from > [EMAIL PROTECTED]]". > > Here's some clarification on my system. I'm trying to backup the > tapeserver. My tape is on a machine called admin.jhuccp.org. > The userID > for both client and server is "amanda", group is "disk". > > I've tried all these variations in the /home/amanda/.amandahosts and > /var/lib/amanda/.amandahosts files (one at a time; the > comments are how > I kept track of what I tried): > admin:/home/amanda # cat .amandahosts > #admin.jhuccp.org amanda.admin.jhuccp.org > #admin amanda.admin.jhuccp.org > admin [EMAIL PROTECTED] > #admin amanda > #admin.jhuccp.org [EMAIL PROTECTED] > admin:/home/amanda # > > Both files are owned by amanda:disk and have 0600 permissions. > > As an aside, is it still necessary to have both > /var/lib/amanda/.amandahosts and /home/amanda/.amandahosts files? Do > they have to be the same? > > My /etc/inetd.conf and /etc/services were patched by 'patch-system': > admin:/home/amanda # grep amanda /etc/services > amanda 10080/udp > amanda 10080/tcp > kamanda 10081/udp > amandaidx 10082/tcp > admin:/home/amanda # grep amanda /etc/inetd.conf > # amanda backup server with indexing capabilities > # amandaidx stream tcp nowait root > /usr/lib/amanda/amindexd amindexd > # amidxtape stream tcp nowait root > /usr/lib/amanda/amidxtaped amidxtaped > # amanda backup client > # amanda dgram udp wait amanda > /usr/lib/amanda/amandad > amandad > amanda dgram udp wait amanda /usr/local/libexec/amandad > amandad > amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd > amindexd > amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped > amidxtaped > admin:/home/amanda # > > Any additional suggestions? > > Thanks for continuing to think about this. > > -Kevin Zembower > > ----- > E. Kevin Zembower > Unix Administrator > Johns Hopkins University/Center for Communications Programs > 111 Market Place, Suite 310 > Baltimore, MD 21202 > 410-659-6139 > > >>> Ana Maria Escalante <[EMAIL PROTECTED]> 12/10/01 08:32PM > >>> > Hi Kevin: > I am not sure if I understood everything from your > message, but it > is > not clear to me, which user will be doing the backups from the server > (amanda is the default user) and whether your client machine is the > same > as your server. > You must have a .amandahosts file in the client amanda home > directory, that gives access to amanda user from the server machine. > In my setup, my backup admin acount is amanda, my server is > server.domain.mx and my client is client.domain.mx. I have an > .amandahosts > file in amanda s home directory in the client with the following > line: > > server.domain.mx amanda > > You will also need an .amandahosts file in the server s amanda > s home > directory, with the client machines name and root as the authorized > user, > in order to recover from the clients, but that is another story. > If you have a .rhosts file in your clients amanda s home > directory, > it must have this same line. I have heard about it :) > Hope this helps. Good luck ... Ana Maria > > On Mon, 10 Dec 2001, KEVIN ZEMBOWER wrote: > > > I'm trying to get my first setup of amanda working. Running amcheck > > gives me: > > admin:/home/amanda # su amanda -c "/usr/local/sbin/amcheck > DailySet1" > > Amanda Tape Server Host Check > > ----------------------------- > > Holding disk /var/amanda: 5807968 KB disk space available, that's > > plenty > > NOTE: skipping tape-writable test > > Tape DailySet101 label ok > > NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sdb1: does > not > > exist > > NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda1: does > not > > exist > > NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda3: does > not > > exist > > Server check took 16.516 seconds > > > > Amanda Backup Client Hosts Check > > -------------------------------- > > ERROR: admin: [access as amanda not allowed from > > [EMAIL PROTECTED]] amandahostsauth failed > > Client check: 1 host checked in 0.029 seconds, 1 problem found > > > > (brought to you by Amanda 2.4.3b1) > > admin:/home/amanda # > > > > Yet, I have a .amandahosts file with what I think are the proper > > contents and permissions: > > admin:/home/amanda # ll /home/amanda/.amandahosts > > -rw-r--r-- 1 amanda disk 30 Dec 10 16:36 > > /home/amanda/.amandahosts > > admin:/home/amanda # cat /home/amanda/.amandahosts > > admin [EMAIL PROTECTED] > > admin:/home/amanda # > > > > I'm stumped. I've tried or checked all the suggestions in the > > FAQ-a-matic for this topic. It's probably something simple, that I > don't > > see because I'm new to amanda. Any suggestions? > > > > Thanks for your help. > > > > -Kevin Zembower > > > > ----- > > E. Kevin Zembower > > Unix Administrator > > Johns Hopkins University/Center for Communications Programs > > 111 Market Place, Suite 310 > > Baltimore, MD 21202 > > 410-659-6139 > > >
