SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
having problem with amrecover under 3.2.0
Author Message
Post having problem with amrecover under 3.2.0 
Running amanda 3.2.0 on a Sun Solaris 10 server.

./amrecover archive
AMRECOVER Version 3.2.0. Contacting server on hertz ...
[request failed: timeout waiting for ACK]

123][root < at > hertz]:amanda/client/archive# cat amrecover.20101210142059.debug
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version 3.2.0: start at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: config_overrides: conf archive
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version 3.2.0: rename at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: security_getdriver(name=bsd) returns 80c40f0
Fri Dec 10 14:20:59 2010: amrecover: security_handleinit(handle=8113390, driver=80c40f0 (BSD))
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: setting up a socket with family 2
Fri Dec 10 14:20:59 2010: amrecover: bind_portrange2: Try port 686: Available - Success
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: socket 4 bound to 0.0.0.0.686
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:20:59 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:21:09 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:21:19 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:29 2010: amrecover: security_seterror(handle=8113390, driver=80c40f0 (BSD) error=timeout waiting for ACK)
Fri Dec 10 14:21:29 2010: amrecover: security_close(handle=8113390, driver=80c40f0 (BSD))

Amcheck does not give any errors

/sbin/amcheck -c archive
Amanda Backup Client Hosts Check
--------------------------------
Client check: 15 hosts checked in 7.920 seconds. 0 problems found.
(brought to you by Amanda 3.2.0)

and amdump works just fine.

My .amandahost file is located in my amandabackup home directory and looks like this

xxx.yyy.edu root amdump amindexd amidxtaped
xxx.yyy.edu amandabackup amdump amindexd amidxtaped

[root < at > hertz]:~amandabackup/sbin# ./amadmin archive version
build: VERSION="Amanda-3.2.0"
BUILT_DATE="Fri Dec 10 13:47:06 EST 2010" BUILT_MACH=""
BUILT_REV="3545" BUILT_BRANCH="3_2_0"
CC="/opt/SunStudio/bin/cc"
paths: bindir="/local/amanda/amanda/bin"
sbindir="/local/amanda/amanda/sbin"
libexecdir="/local/amanda/amanda/libexec"
amlibexecdir="/local/amanda/amanda/libexec/amanda"
mandir="/local/amanda/amanda/share/man"
AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
CONFIG_DIR="/local/amanda/amanda/etc/amanda"
DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"
DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"
VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF
VXDUMP=UNDEF VXRESTORE=UNDEF
SAMBA_CLIENT="/usr/sfw/bin/smbclient"
GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"
UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD=UNDEF MAILER=UNDEF
listed_incr_dir="/var/amanda/gnutar-lists"
defs: DEFAULT_SERVER="hertz" DEFAULT_CONFIG="DailySet1"
DEFAULT_TAPE_SERVER="hertz" DEFAULT_TAPE_DEVICE=""
NEED_STRSTR AMFLOCK_POSIX AMFLOCK_LOCKF AMFLOCK_LNLOCK
SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN="amandabackup" CHECK_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"



Any ideas why this is happening?

_____________________________________________________________________
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: rmcgraw < at > purdue.edu
Purdue University ROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067

Post having problem with amrecover under 3.2.0 
amrecover get a timeout, you must check why the server did not respond.

Do hertz (128.210.3.201) in the name of the amanda server?
What's the inetd config for the amanda service on hertz?
What's in the amandad.*.debug file on hertz?
Any error in syslog?

Jean-Louis

McGraw, Robert P wrote:
Running amanda 3.2.0 on a Sun Solaris 10 server.

./amrecover archive
AMRECOVER Version 3.2.0. Contacting server on hertz ...
[request failed: timeout waiting for ACK]

123][root < at > hertz]:amanda/client/archive# cat amrecover.20101210142059.debug
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version 3.2.0: start at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: config_overrides: conf archive
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version 3.2.0: rename at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: security_getdriver(name=bsd) returns 80c40f0
Fri Dec 10 14:20:59 2010: amrecover: security_handleinit(handle=8113390, driver=80c40f0 (BSD))
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: setting up a socket with family 2
Fri Dec 10 14:20:59 2010: amrecover: bind_portrange2: Try port 686: Available - Success
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: socket 4 bound to 0.0.0.0.686
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:20:59 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:21:09 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr(addr=81133b0, dgram=80e7ed4)
Fri Dec 10 14:21:19 2010: amrecover: (sockaddr_in *)81133b0 = { 2, 10080, 128.210.3.201 }
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr: 80e7ed4->socket = 4
Fri Dec 10 14:21:29 2010: amrecover: security_seterror(handle=8113390, driver=80c40f0 (BSD) error=timeout waiting for ACK)
Fri Dec 10 14:21:29 2010: amrecover: security_close(handle=8113390, driver=80c40f0 (BSD))

Amcheck does not give any errors

/sbin/amcheck -c archive
Amanda Backup Client Hosts Check
--------------------------------
Client check: 15 hosts checked in 7.920 seconds. 0 problems found.
(brought to you by Amanda 3.2.0)

and amdump works just fine.

My .amandahost file is located in my amandabackup home directory and looks like this

xxx.yyy.edu root amdump amindexd amidxtaped
xxx.yyy.edu amandabackup amdump amindexd amidxtaped

[root < at > hertz]:~amandabackup/sbin# ./amadmin archive version
build: VERSION="Amanda-3.2.0"
BUILT_DATE="Fri Dec 10 13:47:06 EST 2010" BUILT_MACH=""
BUILT_REV="3545" BUILT_BRANCH="3_2_0"
CC="/opt/SunStudio/bin/cc"
paths: bindir="/local/amanda/amanda/bin"
sbindir="/local/amanda/amanda/sbin"
libexecdir="/local/amanda/amanda/libexec"
amlibexecdir="/local/amanda/amanda/libexec/amanda"
mandir="/local/amanda/amanda/share/man"
AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
CONFIG_DIR="/local/amanda/amanda/etc/amanda"
DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"
DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"
VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF
VXDUMP=UNDEF VXRESTORE=UNDEF
SAMBA_CLIENT="/usr/sfw/bin/smbclient"
GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"
UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD=UNDEF MAILER=UNDEF
listed_incr_dir="/var/amanda/gnutar-lists"
defs: DEFAULT_SERVER="hertz" DEFAULT_CONFIG="DailySet1"
DEFAULT_TAPE_SERVER="hertz" DEFAULT_TAPE_DEVICE=""
NEED_STRSTR AMFLOCK_POSIX AMFLOCK_LOCKF AMFLOCK_LNLOCK
SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN="amandabackup" CHECK_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"



Any ideas why this is happening?

_____________________________________________________________________
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: rmcgraw < at > purdue.edu
Purdue University ROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067




Post having problem with amrecover under 3.2.0 
After a little more searching I found the problem.

Even thought the debug files did not say, it seem that I needed an amanda-client.conf file in ~amandabackup/etc/amanda. Once I added the file amrecover started working.

This might be a check that needs to be added.

Thanks for your help

Robert





-----Original Message-----
From: Jean-Louis Martineau [mailto:martineau < at > zmanda.com]
Sent: Friday, December 10, 2010 2:57 PM
To: McGraw, Robert P
Cc: 'amanda-users < at > amanda.org'
Subject: Re: having problem with amrecover under 3.2.0


amrecover get a timeout, you must check why the server did not respond.

Do hertz (128.210.3.201) in the name of the amanda server?
What's the inetd config for the amanda service on hertz?
What's in the amandad.*.debug file on hertz?
Any error in syslog?

Jean-Louis

McGraw, Robert P wrote:
Running amanda 3.2.0 on a Sun Solaris 10 server.

./amrecover archive
AMRECOVER Version 3.2.0. Contacting server on hertz ...
[request failed: timeout waiting for ACK]

123][root < at > hertz]:amanda/client/archive# cat
amrecover.20101210142059.debug
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version
3.2.0: start at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: config_overrides: conf archive
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0 euid 0 version
3.2.0: rename at Fri Dec 10 14:20:59 2010
Fri Dec 10 14:20:59 2010: amrecover: security_getdriver(name=bsd)
returns 80c40f0
Fri Dec 10 14:20:59 2010: amrecover:
security_handleinit(handle=8113390, driver=80c40f0 (BSD))
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: setting up a socket
with family 2
Fri Dec 10 14:20:59 2010: amrecover: bind_portrange2: Try port 686:
Available - Success
Fri Dec 10 14:20:59 2010: amrecover: dgram_bind: socket 4 bound to
0.0.0.0.686
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr(addr=81133b0,
dgram=80e7ed4)
Fri Dec 10 14:20:59 2010: amrecover: (sockaddr_in *)81133b0 = { 2,
10080, 128.210.3.201 }
Fri Dec 10 14:20:59 2010: amrecover: dgram_send_addr: 80e7ed4->socket
= 4
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr(addr=81133b0,
dgram=80e7ed4)
Fri Dec 10 14:21:09 2010: amrecover: (sockaddr_in *)81133b0 = { 2,
10080, 128.210.3.201 }
Fri Dec 10 14:21:09 2010: amrecover: dgram_send_addr: 80e7ed4->socket
= 4
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr(addr=81133b0,
dgram=80e7ed4)
Fri Dec 10 14:21:19 2010: amrecover: (sockaddr_in *)81133b0 = { 2,
10080, 128.210.3.201 }
Fri Dec 10 14:21:19 2010: amrecover: dgram_send_addr: 80e7ed4->socket
= 4
Fri Dec 10 14:21:29 2010: amrecover:
security_seterror(handle=8113390, driver=80c40f0 (BSD) error=timeout
waiting for ACK)
Fri Dec 10 14:21:29 2010: amrecover: security_close(handle=8113390,
driver=80c40f0 (BSD))

Amcheck does not give any errors

/sbin/amcheck -c archive
Amanda Backup Client Hosts Check
--------------------------------
Client check: 15 hosts checked in 7.920 seconds. 0 problems
found.
(brought to you by Amanda 3.2.0)

and amdump works just fine.

My .amandahost file is located in my amandabackup home directory and
looks like this

xxx.yyy.edu root amdump amindexd amidxtaped
xxx.yyy.edu amandabackup amdump amindexd amidxtaped

[root < at > hertz]:~amandabackup/sbin# ./amadmin archive version
build: VERSION="Amanda-3.2.0"
BUILT_DATE="Fri Dec 10 13:47:06 EST 2010" BUILT_MACH=""
BUILT_REV="3545" BUILT_BRANCH="3_2_0"
CC="/opt/SunStudio/bin/cc"
paths: bindir="/local/amanda/amanda/bin"
sbindir="/local/amanda/amanda/sbin"
libexecdir="/local/amanda/amanda/libexec"
amlibexecdir="/local/amanda/amanda/libexec/amanda"
mandir="/local/amanda/amanda/share/man"
AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
CONFIG_DIR="/local/amanda/amanda/etc/amanda"
DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"
DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"
VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF
VXDUMP=UNDEF VXRESTORE=UNDEF
SAMBA_CLIENT="/usr/sfw/bin/smbclient"
GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"
UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD=UNDEF MAILER=UNDEF
listed_incr_dir="/var/amanda/gnutar-lists"
defs: DEFAULT_SERVER="hertz" DEFAULT_CONFIG="DailySet1"
DEFAULT_TAPE_SERVER="hertz" DEFAULT_TAPE_DEVICE=""
NEED_STRSTR AMFLOCK_POSIX AMFLOCK_LOCKF AMFLOCK_LNLOCK
SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN="amandabackup" CHECK_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"



Any ideas why this is happening?

_____________________________________________________________________
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: rmcgraw < at > purdue.edu
Purdue University ROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067





Post having problem with amrecover under 3.2.0 
amanda-client.conf is not required. Maybe you added some config in it?

Jean-Louis

McGraw, Robert P wrote:
After a little more searching I found the problem.

Even thought the debug files did not say, it seem that I needed an amanda-client.conf file in ~amandabackup/etc/amanda. Once I added the file amrecover started working.

This might be a check that needs to be added.

Thanks for your help

Robert


Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB