Amanda-Users

Re: Common 'Please add "amdump" to the line in /home/amanda/.amandahosts on the client' error

2007-07-12 02:28:02
Subject: Re: Common 'Please add "amdump" to the line in /home/amanda/.amandahosts on the client' error
From: "C.Scheeder" <christoph AT scheeder DOT de>
To: Craig Tierney <ctierney AT HPTI DOT com>
Date: Thu, 12 Jul 2007 08:16:46 +0200
Craig Tierney schrieb:
I am having a problem with getting amcheck to run cleanly with a new client I have just added. It seems that the problem is quite common,
but I still cannot figure it out.

I am trying to install Amanda-2.5.2 from source on Redhat Enterprise 5.
I have it configured and working properly on the server named 'amanda'.
By properly, amcheck finishes clean, I can get amdump to backup a directory on the server, and I can use amrecover to look at the files and use amrestore to restore a file.

Now I am trying to install the client on a server named 'datas'. I copied over the amanda install directory, added the services to /etc/services, and copied the amanda service file to /etc/xinetd.d.
I also modified the /home/amanda/.amandahosts file to look like:

amanda amanda amdump
amanda root amrecover
amanda root amandad amindexd amidxtaped

datas amanda amdump
datas root amrecover
datas root amandad amindexd amidxtaped


The /home filesystem is an NFS mount on both systems.  I have tried
having the /home filesystem be local and it made no difference.

The user amanda and the group amanda have consistent uid and gid on
both systems.

My disklist is:

amanda /var/log root-tar
datas /home user-tar

So I try to run amcheck -cl daily, and I get the following response:

[amanda@amanda daily]$ amcheck -cl daily
Amanda Tape Server Host Check
-----------------------------
Holding disk /var/amandatapes/dumps: 50813372 KB disk space available, using 49152000 KB as requested
NOTE: skipping tape checks
WARNING: tapecycle (10) <= runspercycle (28).
NOTE: host info dir /opt/amanda-2.5.2/etc/amanda/daily/curinfo/datas does not exist
NOTE: it will be created on the next run.
NOTE: index dir /opt/amanda-2.5.2/etc/amanda/daily/index/datas does not exist
NOTE: it will be created on the next run.
Server check took 0.003 seconds

Amanda Backup Client Hosts Check
--------------------------------
ERROR: NAK datas: user amanda from 192.168.64.44 is not allowed to execute the service noop: Please add "amdump" to the line in /home/amanda/.amandahosts on the client
Client check: 2 hosts checked in 0.044 seconds, 1 problem found

(brought to you by Amanda 2.5.2)

I have tried setting the permissions on the ~/.amandahosts file
to 400 and 600 (as I saw in other posts), but this did not help.

The /tmp/amanda*amandad file doesn't help much (to me at least):

amandad: debug 1 pid 10481 ruid 1003 euid 1003: start at Wed Jul 11 19:16:18 2007
Reading conf file "/opt/amanda-2.5.2/etc/amanda/amanda-client.conf".
amandad: time 0.055: security_getdriver(name=bsd) returns 0x8e6540
amandad: version 2.5.2
amandad: time 0.055: build: VERSION="Amanda-2.5.2"
amandad: time 0.055:        BUILT_DATE="Thu Jul 5 14:22:23 PDT 2007"
amandad: time 0.055: BUILT_MACH="Linux amanda 2.6.18-8.1.3.el5 #1 SMP Mon Apr 16 15:54:12 EDT 200
7 i686 i686 i386 GNU/Linux"
amandad: time 0.055:        CC="gcc"
amandad: time 0.055: CONFIGURE_COMMAND="'./configure' '--prefix=/opt/amanda-2.5.2' '--with-user=a
manda' '--with-group=amanda' '--with-config=daily' '--with-ssh-security'"
amandad: time 0.055: paths: bindir="/opt/amanda-2.5.2/bin"
amandad: time 0.055:        sbindir="/opt/amanda-2.5.2/sbin"
amandad: time 0.055:        libexecdir="/opt/amanda-2.5.2/libexec"
amandad: time 0.055: mandir="/opt/amanda-2.5.2/man" AMANDA_TMPDIR="/tmp/amanda"
amandad: time 0.055:        AMANDA_DBGDIR="/tmp/amanda"
amandad: time 0.055:        CONFIG_DIR="/opt/amanda-2.5.2/etc/amanda"
amandad: time 0.055: DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad: time 0.055: RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF amandad: time 0.055: XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
amandad: time 0.055:        SAMBA_CLIENT=UNDEF GNUTAR="/bin/gtar"
amandad: time 0.055: COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip"
amandad: time 0.055:         LPRCMD=UNDEF MAILER="/usr/bin/Mail"
amandad: time 0.055: listed_incr_dir="/opt/amanda-2.5.2/var/amanda/gnutar-lists"
amandad: time 0.055: defs:  DEFAULT_SERVER="amanda" DEFAULT_CONFIG="daily"
amandad: time 0.055: DEFAULT_TAPE_SERVER="amanda" HAVE_MMAP NEED_STRSTR amandad: time 0.055: HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad: time 0.055: AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS
amandad: time 0.055:        CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad: time 0.055: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad: time 0.055:        COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.056: dgram_recv(dgram=0x8e84a4, timeout=0, fromaddr=0x8f8490)
amandad: time 0.056: (sockaddr_in *)0x8f8490 = { 2, 591, 192.168.64.44 }
amandad: time 0.056: security_handleinit(handle=0x92b5b58, driver=0x8e6540 (BSD)) amandad: time 0.060: security_seterror(handle=0x92b5b58, driver=0x8e6540 (BSD) error=user amanda from 20 4.235.64.44 is not allowed to execute the service noop: Please add "amdump" to the line in /home/amanda/.amandahosts on the client) amandad: time 0.060: accept error: user amanda from 192.168.64.44 is not allowed to execute the service noop: Please add "amdump" to the line in /home/amanda/.amandahosts on the client
amandad: time 0.060: sending NAK pkt:
<<<<<
ERROR user amanda from 192.168.64.44 is not allowed to execute the service noop: Please add "amdump" to the line in /home/amanda/.amandahosts on the client
 >>>>>
amandad: time 0.061: dgram_send_addr(addr=0x92b5b78, dgram=0x8e84a4)
amandad: time 0.061: (sockaddr_in *)0x92b5b78 = { 2, 591, 192.168.64.44 }
amandad: time 0.061: dgram_send_addr: 0x8e84a4->socket = 0
amandad: time 0.061: security_close(handle=0x92b5b58, driver=0x8e6540 (BSD))

I have turned off the firewall (/etc/init.d/iptables stop) on both
nodes to make sure that isn't the problem.  I have tried putting
the FQDN in the .amandahosts but that doesn't help either.

I would appreciate any ideas on getting this to work.

Thanks,
Craig

Hi,
the message is missleading inthis situation, your problem is probably DNS:
you are missing the reverse mapping for "192.168.64.44" to "amanda".
or you have to add the line

192.168.64.44 amanda amdump

to your .amandahosts
Christoph

<Prev in Thread] Current Thread [Next in Thread>