Re: having problem with amrecover under 3.2.0

[Jean-Louis Martineau]

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
  

RE: having problem with amrecover under 3.2.0

[McGraw, Robert P]

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:martin...@zmanda.com]
> Sent: Friday, December 10, 2010 2:57 PM
> To: McGraw, Robert P
> Cc: 'amanda-users@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][r...@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
> >
> > [r...@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
> &

Re: having problem with amrecover under 3.2.0

[Jean-Louis Martineau]

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][r...@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
 
[r...@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 SystemEMAIL: rmcg...@purdue.edu
Purdue UniversityROOM: MATH-807
Department of Mathematics   PHONE: (765) 494-6055
150 N. University Street  
West Lafayette, IN 47907-2067
 

  

having problem with amrecover under 3.2.0

[McGraw, Robert P]

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][r...@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
 
[r...@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 SystemEMAIL: rmcg...@purdue.edu
Purdue UniversityROOM: MATH-807
Department of Mathematics   PHONE: (765) 494-6055
150 N. University Street  
West Lafayette, IN 47907-2067
 

Problem with amrecover (following)

[[EMAIL PROTECTED]]

Hello,

I was surprised by the messahe from amrecover :

No index records for disk for specified date
If date correct, notify system administrator


I look in the debuf files on the server machine and I found the problem
but not the solution. The file "amindexd.20070226214504.debug" contains
the following lines :

#cat amindexd.20070226214504.debug
amindexd: debug 1 pid 11692 ruid 34 euid 34: start at Mon Feb 26
21:45:04 2007
amindexd: version 2.5.1p3
amindexd: error [spawn /bin/gzip: dup2 err: Bad file descriptor]
close debug file: Bad file descriptoramindexd: error
[spawn /usr/bin/sort: dup2 err: Bad file descriptor]
close debug file: Bad file descriptor

The file amindexd is :
ll /usr/lib/amanda/amindexd
-rwxr-xr-x 1 root root 31900 2007-02-20 20:31 /usr/lib/amanda/amindexd

The file is brand new, and dated long after my first revocer tests which
were more successful, is it a problem with the 2.5.1p3 ?

I reload the preceeding version (2.5.1p1) on the server and all seems to
be OK, I can now restore my files ...


Regards

Storm66

PS : linux distribution : Debian

Problem with amrecover

[[EMAIL PROTECTED]]

Hello,

I lost today a disk at 18:30 containing my home directory ... I think,
the last save was at 13:00 I will restore it .
But I encounter a little problem with amrecover, here is the
screencopy :

AMRECOVER Version 2.5.1p3. Contacting server on k400 ...
220 k400 AMANDA index server (2.5.1p3) ready.
200 Access OK
Setting restore date to today (2007-02-25)
200 Working date set to 2007-02-25.
Scanning /lacie/SAUVE/DISK...
200 Config set to jour.
200 Dump host set to k2000.
Trying disk / ...
Trying disk rootfs ...
Use the setdisk command to choose dump disk to recover
amrecover> listdisk
200- List of disk for host k2000
201- /etc
201- /home/jpp
201- /var/tmp/test
200 List of disk for host k2000
amrecover> setdisk /home/jpp
200 Disk set to /home/jpp.
No index records for disk for specified date
If date correct, notify system administrator
amrecover>
==
When I go to the machine on which I save things on disk using a set of 7
directories all seems to be OK.
When I receive the mail from the backup process all was OK.

I enclose the log of the last save (last_log.txt).
 
The index files are still in their directory 
cd .../index/hostname/_home_jpp
ls -altr 
total 800
drwxrwxrwx 5 backup root 4096 2007-02-17 13:00 ..
-rw--- 1 backup backup  59783 2007-02-19 13:01 20070219130002_1.gz
-rw--- 1 backup backup  60937 2007-02-20 13:01 20070220130002_1.gz
-rw--- 1 backup backup  60989 2007-02-21 13:01 20070221130002_1.gz
-rw--- 1 backup backup  61080 2007-02-22 13:01 20070222130002_1.gz
-rw--- 1 backup backup  62277 2007-02-23 13:01 20070223130002_1.gz
-rw--- 1 backup backup 431026 2007-02-24 13:06 20070224130001_0.gz
-rw--- 1 backup backup  39438 2007-02-25 13:00 20070225130002_1.gz
drwxr-sr-x 2 backup backup   4096 2007-02-25 23:41 .

If I decompress a file it contains a list of files which seems OK.

Can somebody help ?

Regards

JP Pozzi

PS:
All was reset on 2007/02/19 with a new disk to save ...

DISK planner k2000 /home/jpp
DISK planner k2000 /var/tmp/test
START planner date 20070225130002
WARNING planner tapecycle (7) <= runspercycle (7)
START driver date 20070225130002
WARNING planner Last full dump of k2000:/etc on tape jour-004 overwritten in 5 
runs.
WARNING planner Last full dump of k400:/etc on tape jour-004 overwritten in 5 
runs.
WARNING planner Last full dump of k400:/boot on tape jour-004 overwritten in 5 
runs.
WARNING planner Last full dump of k2000:/var/tmp/test on tape jour-004 
overwritten in 5 runs.
STATS driver startup time 0.114
START taper datestamp 20070225130002 label jour-006 tape 0
INFO planner Full dump of k400:/etc promoted from 5 days ahead.
INFO planner Full dump of k2000:/etc promoted from 5 days ahead.
INFO planner Full dump of k400:/boot promoted from 5 days ahead.
INFO planner Full dump of k2000:/var/tmp/test promoted from 5 days ahead.
FINISH planner date 20070225130002 time 11.706
SUCCESS dumper k2000 /var/tmp/test 20070225130002 0 [sec 0.751 kb 5550 kps 
7384.0 orig-kb 5550]
SUCCESS chunker k2000 /var/tmp/test 20070225130002 0 [sec 0.780 kb 5550 kps 
7359.3]
STATS driver estimate k2000 /var/tmp/test 20070225130002 0 [sec 1 nkb 5582 ckb 
5600 kps 5550]
SUCCESS taper k2000 /var/tmp/test 20070225130002 0 [sec 0.126 kb 5568 kps 
44131.6 {wr: writers 175 rdwait 0.000 wrwait 0.068 filemark 0.000}]
SUCCESS dumper k400 /boot 20070225130002 0 [sec 1.283 kb 14720 kps 11465.7 
orig-kb 14720]
SUCCESS chunker k400 /boot 20070225130002 0 [sec 1.376 kb 14720 kps 11039.7]
STATS driver estimate k400 /boot 20070225130002 0 [sec 1 nkb 14752 ckb 14752 
kps 12267]
SUCCESS taper k400 /boot 20070225130002 0 [sec 0.274 kb 14720 kps 53621.1 {wr: 
writers 461 rdwait 0.000 wrwait 0.180 filemark 0.000}]
SUCCESS dumper k2000 /home/jpp 20070225130002 1 [sec 4.361 kb 7170 kps 1643.8 
orig-kb 28330]
SUCCESS chunker k2000 /home/jpp 20070225130002 1 [sec 4.381 kb 7170 kps 1694.8]
STATS driver estimate k2000 /home/jpp 20070225130002 1 [sec 4 nkb 28362 ckb 
15456 kps 3220]
SUCCESS taper k2000 /home/jpp 20070225130002 1 [sec 0.165 kb 7200 kps 43454.9 
{wr: writers 226 rdwait 0.000 wrwait 0.088 filemark 0.000}]
SUCCESS dumper k400 /etc 20070225130002 0 [sec 19.905 kb 36540 kps 1835.7 
orig-kb 36540]
SUCCESS chunker k400 /etc 20070225130002 0 [sec 20.012 kb 36540 kps 1885.0]
STATS driver estimate k400 /etc 20070225130002 0 [sec 28 nkb 36512 ckb 36512 
kps 1292]
SUCCESS taper k400 /etc 20070225130002 0 [sec 4.398 kb 36544 kps 8308.8 {wr: 
writers 1143 rdwait 0.074 wrwait 3.733 filemark 0.000}]
SUCCESS dumper k2000 /etc 20070225130002 0 [sec 9.341 kb 42690 kps 4569.7 
orig-kb 42690]
SUCCESS chunker k2000 /etc 20070225130002 0 [sec 9.363 kb 42690 kps 4709.5]
STATS driver estimate k2000 /etc 20070225130002 0 [sec 7 nkb 42722 ckb 42752 
kps 5870]
SUCCESS taper k2000 /etc 20070225130002 0 [sec 0.988 kb 42720 kps 43200.1 {wr: 
writers

Re: problem with amrecover

[Jean-Francois Malouin]

* Eric Doutreleau <[EMAIL PROTECTED]> [20070123 11:48]:
> Jean-Francois Malouin a écrit :
> >* Eric Doutreleau <[EMAIL PROTECTED]> [20070123 09:23]:
> >  
> >>hi i have some problems with the new framework of security of amanda
> >>
> >>my server and my client is in the version 2.5.1p2
> >>
> >>the amanda-client.conf on the client is this one
> >>
> >>conf "int" # your config name
> >>index_server "backup" # your amindexd server
> >>tape_server "backup" # your amidxtaped server
> >>#tapedev "" # your tape device
> >># auth - authentication scheme to use between server and client.
> >># Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
> >># Default: [auth "bsdtcp"]
> >>auth "bsdtcp"
> >>
> >>when i run amrecover i got these results
> >>
> >>amrecover -s backup
> >>AMRECOVER Version 2.5.1p2. Contacting server on backup ...
> >>[request failed: Connection refused]
> >>
> >>on the server the debug file
> >>amindexd.20070123151619.debug
> >>amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 
> >>15:16:19 2007
> >>amindexd: version 2.5.1p2
> >>close debug file: Bad file descriptor
> >>
> >>does someone knows how to solve the problem?
> >>
> >
> >What's in your ~amanda/.amandahosts
> >(and check permissions too!)
> >
> >Explained in:
> >http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
> >
> >hth
> >jf
> >  
> hi
> my .amandahosts is owned by my backup user and is mode 700
> it contains
> rezo.int-evry.frrootamindexd amidxtaped
> 
> I guess all is ok for that

You should check the debug files on both client and server.
For .amandahosts I would stuff in an extra line:

rezo.int-evry.framanda  amindexd amidxtaped

replace 'amanda' by your backup user. If it still fails
you might have to investigate how name resolution is
performed on the server.

jf

> 

-- 
<° ><

Re: problem with amrecover

[Eric Doutreleau]

Jean-Francois Malouin a écrit :

* Eric Doutreleau <[EMAIL PROTECTED]> [20070123 09:23]:
  

hi i have some problems with the new framework of security of amanda

my server and my client is in the version 2.5.1p2

the amanda-client.conf on the client is this one

conf "int" # your config name
index_server "backup" # your amindexd server
tape_server "backup" # your amidxtaped server
#tapedev "" # your tape device
# auth - authentication scheme to use between server and client.
# Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
# Default: [auth "bsdtcp"]
auth "bsdtcp"

when i run amrecover i got these results

amrecover -s backup
AMRECOVER Version 2.5.1p2. Contacting server on backup ...
[request failed: Connection refused]

on the server the debug file
amindexd.20070123151619.debug
amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 
15:16:19 2007

amindexd: version 2.5.1p2
close debug file: Bad file descriptor

does someone knows how to solve the problem?



What's in your ~amanda/.amandahosts
(and check permissions too!)

Explained in:
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication

hth
jf
  

hi
my .amandahosts is owned by my backup user and is mode 700
it contains
rezo.int-evry.frrootamindexd amidxtaped

I guess all is ok for that

Re: problem with amrecover

[Jean-Francois Malouin]

* Eric Doutreleau <[EMAIL PROTECTED]> [20070123 09:23]:
> hi i have some problems with the new framework of security of amanda
> 
> my server and my client is in the version 2.5.1p2
> 
> the amanda-client.conf on the client is this one
> 
> conf "int" # your config name
> index_server "backup" # your amindexd server
> tape_server "backup" # your amidxtaped server
> #tapedev "" # your tape device
> # auth - authentication scheme to use between server and client.
> # Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
> # Default: [auth "bsdtcp"]
> auth "bsdtcp"
> 
> when i run amrecover i got these results
> 
> amrecover -s backup
> AMRECOVER Version 2.5.1p2. Contacting server on backup ...
> [request failed: Connection refused]
> 
> on the server the debug file
> amindexd.20070123151619.debug
> amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 
> 15:16:19 2007
> amindexd: version 2.5.1p2
> close debug file: Bad file descriptor
> 
> does someone knows how to solve the problem?

What's in your ~amanda/.amandahosts
(and check permissions too!)

Explained in:
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication

hth
jf
-- 
<° ><

problem with amrecover

[Eric Doutreleau]

hi i have some problems with the new framework of security of amanda

my server and my client is in the version 2.5.1p2

the amanda-client.conf on the client is this one

conf "int" # your config name
index_server "backup" # your amindexd server
tape_server "backup" # your amidxtaped server
#tapedev "" # your tape device
# auth - authentication scheme to use between server and client.
# Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
# Default: [auth "bsdtcp"]
auth "bsdtcp"

when i run amrecover i got these results

amrecover -s backup
AMRECOVER Version 2.5.1p2. Contacting server on backup ...
[request failed: Connection refused]

on the server the debug file
amindexd.20070123151619.debug
amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 
15:16:19 2007

amindexd: version 2.5.1p2
close debug file: Bad file descriptor

does someone knows how to solve the problem?

Re: permission problem with amrecover

[Gene Heskett]

On Friday 28 April 2006 05:31, Thomas Ginestet wrote:
>Gene Heskett a écrit :
>
>Thanks a lot Gene (and you too Matt ;-) ), your script is such a good
> idea. Using the x bit was better ;-). But I have others problems like
> the generated tapelist with owner amanda and group amanda (and
> restricted permissions to owner) which complains when running
> amrecover. The easiest way for me is to remove  all file installed
> with my debian packager and reinstall by hand with corrects arguments
> in my ./configure My Debian mind tell me to download source package,
> modify arguments and then re-package Amanda but...I'm so lazy on
> Friday.
>
>Thomas

Chuckle, been there, done that, bought the t-shirt & wore it out even.
But at least you now know what to do.

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

Re: permission problem with amrecover

[Thomas Ginestet]

Gene Heskett a écrit :


On Thursday 27 April 2006 07:56, Thomas Ginestet wrote:
[...]
 


501 Could not read config file /etc/amanda/DailySet/amanda.conf!


I've checked amindexd logs:

backup:/var/log/amanda# vi amindexd.20060426132954.debug

amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26
13:23:57 2006

amindexd: version 2.5.0

amindexd: < 220 backup AMANDA index server (2.5.0) ready.

amindexd: > SECURITY USER root

bsd security: remote host backup.gpsa.fr user root local user backup

amindexd: < 200 Access OK

amindexd: > FEATURES feff9ffe07

amindexd: < 200 FEATURES feff9ffe07

amindexd: > DATE 2006-04-26

amindexd: < 200 Working date set to 2006-04-26.

amindexd: > SCNF DailySet

could not open conf file "/etc/amanda/DailySet/amanda.conf":
Permission denied

amindexd: < 501 Could not read config file
/etc/amanda/DailySet/amanda.conf!



My permissions for /etc/amanda/DailySet/amanda.conf:

backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
-rwxrwx---  1 root amanda 4451 2006-04-25 16:19
/etc/amanda/DailySet/amanda.conf

I don't understand why it complain about that...
   


You've apparently edited the amanda.conf as root (never do that,
always become amanda to do that) and the perms are now fubar.  It
should look something like this:

-rw-r--r--  1 amanda disk 22049 Apr 16
08:59 /usr/local/etc/amanda/Daily/amanda.conf

The user amanda should be a member of the group disk or backup.
AFAIK, there is no group 'amanda', at least not here.

Is this a new install?

 


Any help would be appreciate


Thomas
   


Yes, I've tried to properly reconfigure Amanda but with Debian tools.
I didn't find how to set --with-user=amanda --with-group=backup .
options, that's why I've changed all permissions by hand.
I'm so lost with permissionsfollowing your advices, this is what
I've set:

backup:~# ls -l /usr/sbin/am* => owner amanda group backup for all
except for amcheck:

-rwSr--r-- 1 root backup 35164 2006-04-03 14:07 /usr/sbin/amcheck
   


-rwsr-x---  1 root disk 88191 Apr 25 00:09 /usr/local/sbin/amcheck
The s's are all lowercase here, no idea what diff that might indicate.

 


backup:~# ls -al /usr/local/sbin/am* => owner amanda group backup for
all except for amcheck:

-rwSr--r-- 1 root backup 93903 2006-04-03 10:09
/usr/local/sbin/amcheck

backup:~# ls -l /usr/local/libexec => owner amanda group backup for
all except for:

-rwSr--r-- 1 root backup 86228 2006-04-03 10:09 dumper

-rwSr--r-- 1 root backup 40553 2006-04-03 10:08 killpgrp

-rwSr--r-- 1 root backup 100783 2006-04-03 10:09 planner

-rwSr--r-- 1 root backup 38055 2006-04-03 10:08 rundump

-rwSr--r-- 1 root backup 38062 2006-04-03 10:08 runtar

backup:~# ls -l /usr/lib/amanda => owner amanda group backup for all

backup:~# ls -l /var/log/amanda => owner amanda group backup for all


backup:~# ls -l /etc/amanda => owner amanda group backup for all


backup:~# ls -l /etc/amandahosts => owner amanda group backup for all


backup:~# ls -l /tmp/amanda => owner amanda group backup for all



My dumpuser on amanda.conf is amanda but I can't launch amcheck
anymore: backup:~# su amanda -c "/usr/sbin/amcheck DailySet" bash:
/usr/sbin/amcheck: Permission non accordée (access not allowed for
english guys ;-))
I must have forgotten something else but I don't know what...
   



see my ls -l on amcheck above, or:

-rwsr-x---  1 root disk 88191 Apr 25 00:09 /usr/local/sbin/amcheck

You are missing the 'x' bit in the perms in your copy.

This is why we generally recommend building from the tarballs, doing the 
unpack, configure, and make stages in the user amanda's home directory. 
THEN you become root and do the make install, and all perms are then 
correctly set automaticly.


So far, very few packagers making packages to match their fav systems 
have demonstrated a working understanding of the amanda theory of using 
just enough permissions to do the job.


I've been building the new snapshots as they become available for 
several years now, and I've boiled it down to a short script that I use 
after becoming the user amanda, and unpacking the tarball 
in /home/amanda, and then cp'ing this script I keep a copy of sitting 
in /home/amanda:

--
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo " Warning "
echo "Amanda needs to be configured and built by the user amanda,"
echo "but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local \
--with-tapedev="FILE:/amandatapes" \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--with-config=Daily \
--with-gnutar=/usr/local/bin/tar

make
-
which is named gh.cf into the freshly unpacked directory, then cd'ing to 
that

Re: permission problem with amrecover

[Gene Heskett]

On Thursday 27 April 2006 07:56, Thomas Ginestet wrote:
[...]
>>>501 Could not read config file /etc/amanda/DailySet/amanda.conf!
>>>
>>>
>>>I've checked amindexd logs:
>>>
>>>backup:/var/log/amanda# vi amindexd.20060426132954.debug
>>>
>>>amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26
>>>13:23:57 2006
>>>
>>>amindexd: version 2.5.0
>>>
>>>amindexd: < 220 backup AMANDA index server (2.5.0) ready.
>>>
>>>amindexd: > SECURITY USER root
>>>
>>>bsd security: remote host backup.gpsa.fr user root local user backup
>>>
>>>amindexd: < 200 Access OK
>>>
>>>amindexd: > FEATURES feff9ffe07
>>>
>>>amindexd: < 200 FEATURES feff9ffe07
>>>
>>>amindexd: > DATE 2006-04-26
>>>
>>>amindexd: < 200 Working date set to 2006-04-26.
>>>
>>>amindexd: > SCNF DailySet
>>>
>>>could not open conf file "/etc/amanda/DailySet/amanda.conf":
>>>Permission denied
>>>
>>>amindexd: < 501 Could not read config file
>>>/etc/amanda/DailySet/amanda.conf!
>>>
>>>
>>>
>>>My permissions for /etc/amanda/DailySet/amanda.conf:
>>>
>>>backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
>>>-rwxrwx---  1 root amanda 4451 2006-04-25 16:19
>>>/etc/amanda/DailySet/amanda.conf
>>>
>>>I don't understand why it complain about that...
>>
>>You've apparently edited the amanda.conf as root (never do that,
>> always become amanda to do that) and the perms are now fubar.  It
>> should look something like this:
>>
>>-rw-r--r--  1 amanda disk 22049 Apr 16
>>08:59 /usr/local/etc/amanda/Daily/amanda.conf
>>
>>The user amanda should be a member of the group disk or backup.
>> AFAIK, there is no group 'amanda', at least not here.
>>
>>Is this a new install?
>>
>>>Any help would be appreciate
>>>
>>>
>>>Thomas
>
>Yes, I've tried to properly reconfigure Amanda but with Debian tools.
> I didn't find how to set --with-user=amanda --with-group=backup .
> options, that's why I've changed all permissions by hand.
>I'm so lost with permissionsfollowing your advices, this is what
>I've set:
>
>backup:~# ls -l /usr/sbin/am* => owner amanda group backup for all
>except for amcheck:
>
>-rwSr--r-- 1 root backup 35164 2006-04-03 14:07 /usr/sbin/amcheck
-rwsr-x---  1 root disk 88191 Apr 25 00:09 /usr/local/sbin/amcheck
The s's are all lowercase here, no idea what diff that might indicate.

>backup:~# ls -al /usr/local/sbin/am* => owner amanda group backup for
>all except for amcheck:
>
>-rwSr--r-- 1 root backup 93903 2006-04-03 10:09
> /usr/local/sbin/amcheck
>
>backup:~# ls -l /usr/local/libexec => owner amanda group backup for
> all except for:
>
>-rwSr--r-- 1 root backup 86228 2006-04-03 10:09 dumper
>
>-rwSr--r-- 1 root backup 40553 2006-04-03 10:08 killpgrp
>
>-rwSr--r-- 1 root backup 100783 2006-04-03 10:09 planner
>
>-rwSr--r-- 1 root backup 38055 2006-04-03 10:08 rundump
>
>-rwSr--r-- 1 root backup 38062 2006-04-03 10:08 runtar
>
>backup:~# ls -l /usr/lib/amanda => owner amanda group backup for all
>
>backup:~# ls -l /var/log/amanda => owner amanda group backup for all
>
>
>backup:~# ls -l /etc/amanda => owner amanda group backup for all
>
>
>backup:~# ls -l /etc/amandahosts => owner amanda group backup for all
>
>
>backup:~# ls -l /tmp/amanda => owner amanda group backup for all
>
>
>
>My dumpuser on amanda.conf is amanda but I can't launch amcheck
> anymore: backup:~# su amanda -c "/usr/sbin/amcheck DailySet" bash:
>/usr/sbin/amcheck: Permission non accordée (access not allowed for
>english guys ;-))
>I must have forgotten something else but I don't know what...

see my ls -l on amcheck above, or:

-rwsr-x---  1 root disk 88191 Apr 25 00:09 /usr/local/sbin/amcheck

You are missing the 'x' bit in the perms in your copy.

This is why we generally recommend building from the tarballs, doing the 
unpack, configure, and make stages in the user amanda's home directory. 
THEN you become root and do the make install, and all perms are then 
correctly set automaticly.

So far, very few packagers making packages to match their fav systems 
have demonstrated a working understanding of the amanda theory of using 
just enough permissions to do the job.

I've been building the new snapshots as they become available for 
several years now, and I've boiled it down to a short script that I use 
after becoming the user amanda, and unpacking the tarball 
in /home/amanda, and then cp'ing this script I keep a copy of sitting 
in /home/amanda:
--
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
 echo
 echo " Warning "
 echo "Amanda needs to be configured and built by the user amanda,"
 echo "but must be installed by user root."
 echo
 exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
 --with-group=disk \
 --with-owner=amanda \
 --with-gnu-ld \
 --prefix=/usr/local \
 --with-tapedev="FILE:/amandatapes" \
 --with-debugging=/tmp/amanda-dbg/ \
 --with-tape-server=coyote \
 --with-amandahosts \
 --with-configdir=/usr/local/etc/ama

Re: permission problem with amrecover

[Matt Hyclak]

On Thu, Apr 27, 2006 at 01:56:51PM +0200, Thomas Ginestet enlightened us:
> Gene Heskett a écrit :
> 
> >On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
> > 
> >
> >>Hi list,
> >>
> >>Thanks to your help, I've successful launched amcheck and amdump :-)
> >>I've tried amrecover to check recovery too but some new problems
> >>occured.
> >>
> >>After playing with  access not allowed error, I'm still stuck on the
> >>following one:
> >>
> >>backup:/# amrecover DailySet
> >>
> >>AMRECOVER Version 2.5.0. Contacting server on backup ...
> >>
> >>220 backup AMANDA index server (2.5.0) ready.
> >>
> >>200 Access OK
> >>
> >>Setting restore date to today (2006-04-26)
> >>
> >>200 Working date set to 2006-04-26.
> >>
> >>501 Could not read config file /etc/amanda/DailySet/amanda.conf!
> >>
> >>
> >>I've checked amindexd logs:
> >>
> >>backup:/var/log/amanda# vi amindexd.20060426132954.debug
> >>
> >>amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26
> >>13:23:57 2006
> >>
> >>amindexd: version 2.5.0
> >>
> >>amindexd: < 220 backup AMANDA index server (2.5.0) ready.
> >>
> >>amindexd: > SECURITY USER root
> >>
> >>bsd security: remote host backup.gpsa.fr user root local user backup
> >>
> >>amindexd: < 200 Access OK
> >>
> >>amindexd: > FEATURES feff9ffe07
> >>
> >>amindexd: < 200 FEATURES feff9ffe07
> >>
> >>amindexd: > DATE 2006-04-26
> >>
> >>amindexd: < 200 Working date set to 2006-04-26.
> >>
> >>amindexd: > SCNF DailySet
> >>
> >>could not open conf file "/etc/amanda/DailySet/amanda.conf":
> >>Permission denied
> >>
> >>amindexd: < 501 Could not read config file
> >>/etc/amanda/DailySet/amanda.conf!
> >>
> >>
> >>
> >>My permissions for /etc/amanda/DailySet/amanda.conf:
> >>
> >>backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
> >>-rwxrwx---  1 root amanda 4451 2006-04-25 16:19
> >>/etc/amanda/DailySet/amanda.conf
> >>
> >>I don't understand why it complain about that...
> >>   
> >>
> >
> >You've apparently edited the amanda.conf as root (never do that, always 
> >become amanda to do that) and the perms are now fubar.  It should look 
> >something like this:
> >
> >-rw-r--r--  1 amanda disk 22049 Apr 16 
> >08:59 /usr/local/etc/amanda/Daily/amanda.conf
> >
> >The user amanda should be a member of the group disk or backup. AFAIK, 
> >there is no group 'amanda', at least not here.
> >
> >Is this a new install?
> >
> >
> > 
> >
> >>Any help would be appreciate
> >>
> >>
> >>Thomas
> >>   
> >>
> >
> > 
> >
> Yes, I've tried to properly reconfigure Amanda but with Debian tools. I 
> didn't find how to set --with-user=amanda --with-group=backup . 
> options, that's why I've changed all permissions by hand.
> I'm so lost with permissionsfollowing your advices, this is what 
> I've set:
> 
> backup:~# ls -l /usr/sbin/am* => owner amanda group backup for all 
> except for amcheck:
> 
> -rwSr--r-- 1 root backup 35164 2006-04-03 14:07 /usr/sbin/amcheck
> 
> backup:~# ls -al /usr/local/sbin/am* => owner amanda group backup for 
> all except for amcheck:
> 
> -rwSr--r-- 1 root backup 93903 2006-04-03 10:09 /usr/local/sbin/amcheck
> 
> backup:~# ls -l /usr/local/libexec => owner amanda group backup for all 
> except for:
> 
> -rwSr--r-- 1 root backup 86228 2006-04-03 10:09 dumper
> 
> -rwSr--r-- 1 root backup 40553 2006-04-03 10:08 killpgrp
> 
> -rwSr--r-- 1 root backup 100783 2006-04-03 10:09 planner
> 
> -rwSr--r-- 1 root backup 38055 2006-04-03 10:08 rundump
> 
> -rwSr--r-- 1 root backup 38062 2006-04-03 10:08 runtar
> 
> backup:~# ls -l /usr/lib/amanda => owner amanda group backup for all
> 
> backup:~# ls -l /var/log/amanda => owner amanda group backup for all
> 
> 
> backup:~# ls -l /etc/amanda => owner amanda group backup for all
> 
> 
> backup:~# ls -l /etc/amandahosts => owner amanda group backup for all
> 
> 
> backup:~# ls -l /tmp/amanda => owner amanda group backup for all
> 
> 
> 
> My dumpuser on amanda.conf is amanda but I can't launch amcheck anymore:
> backup:~# su amanda -c "/usr/sbin/amcheck DailySet" bash: 
> /usr/sbin/amcheck: Permission non accordée (access not allowed for 
> english guys ;-))
> I must have forgotten something else but I don't know what...
> 
> 

You're missing the execute bit on all of those files...

Matt

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263

Re: permission problem with amrecover

[Thomas Ginestet]

Gene Heskett a écrit :


On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
 


Hi list,

Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems
occured.

After playing with  access not allowed error, I'm still stuck on the
following one:

backup:/# amrecover DailySet

AMRECOVER Version 2.5.0. Contacting server on backup ...

220 backup AMANDA index server (2.5.0) ready.

200 Access OK

Setting restore date to today (2006-04-26)

200 Working date set to 2006-04-26.

501 Could not read config file /etc/amanda/DailySet/amanda.conf!


I've checked amindexd logs:

backup:/var/log/amanda# vi amindexd.20060426132954.debug

amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26
13:23:57 2006

amindexd: version 2.5.0

amindexd: < 220 backup AMANDA index server (2.5.0) ready.

amindexd: > SECURITY USER root

bsd security: remote host backup.gpsa.fr user root local user backup

amindexd: < 200 Access OK

amindexd: > FEATURES feff9ffe07

amindexd: < 200 FEATURES feff9ffe07

amindexd: > DATE 2006-04-26

amindexd: < 200 Working date set to 2006-04-26.

amindexd: > SCNF DailySet

could not open conf file "/etc/amanda/DailySet/amanda.conf":
Permission denied

amindexd: < 501 Could not read config file
/etc/amanda/DailySet/amanda.conf!



My permissions for /etc/amanda/DailySet/amanda.conf:

backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
-rwxrwx---  1 root amanda 4451 2006-04-25 16:19
/etc/amanda/DailySet/amanda.conf

I don't understand why it complain about that...
   



You've apparently edited the amanda.conf as root (never do that, always 
become amanda to do that) and the perms are now fubar.  It should look 
something like this:


-rw-r--r--  1 amanda disk 22049 Apr 16 
08:59 /usr/local/etc/amanda/Daily/amanda.conf


The user amanda should be a member of the group disk or backup. AFAIK, 
there is no group 'amanda', at least not here.


Is this a new install?


 


Any help would be appreciate


Thomas
   



 

Yes, I've tried to properly reconfigure Amanda but with Debian tools. I 
didn't find how to set --with-user=amanda --with-group=backup . 
options, that's why I've changed all permissions by hand.
I'm so lost with permissionsfollowing your advices, this is what 
I've set:


backup:~# ls -l /usr/sbin/am* => owner amanda group backup for all 
except for amcheck:


-rwSr--r-- 1 root backup 35164 2006-04-03 14:07 /usr/sbin/amcheck

backup:~# ls -al /usr/local/sbin/am* => owner amanda group backup for 
all except for amcheck:


-rwSr--r-- 1 root backup 93903 2006-04-03 10:09 /usr/local/sbin/amcheck

backup:~# ls -l /usr/local/libexec => owner amanda group backup for all 
except for:


-rwSr--r-- 1 root backup 86228 2006-04-03 10:09 dumper

-rwSr--r-- 1 root backup 40553 2006-04-03 10:08 killpgrp

-rwSr--r-- 1 root backup 100783 2006-04-03 10:09 planner

-rwSr--r-- 1 root backup 38055 2006-04-03 10:08 rundump

-rwSr--r-- 1 root backup 38062 2006-04-03 10:08 runtar

backup:~# ls -l /usr/lib/amanda => owner amanda group backup for all

backup:~# ls -l /var/log/amanda => owner amanda group backup for all


backup:~# ls -l /etc/amanda => owner amanda group backup for all


backup:~# ls -l /etc/amandahosts => owner amanda group backup for all


backup:~# ls -l /tmp/amanda => owner amanda group backup for all



My dumpuser on amanda.conf is amanda but I can't launch amcheck anymore:
backup:~# su amanda -c "/usr/sbin/amcheck DailySet" bash: 
/usr/sbin/amcheck: Permission non accordée (access not allowed for 
english guys ;-))

I must have forgotten something else but I don't know what...


Thomas

Re: permission problem with amrecover

[Gene Heskett]

On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
>Hi list,
>
>Thanks to your help, I've successful launched amcheck and amdump :-)
>I've tried amrecover to check recovery too but some new problems
> occured.
>
>After playing with  access not allowed error, I'm still stuck on the
>following one:
>
>backup:/# amrecover DailySet
>
>AMRECOVER Version 2.5.0. Contacting server on backup ...
>
>220 backup AMANDA index server (2.5.0) ready.
>
>200 Access OK
>
>Setting restore date to today (2006-04-26)
>
>200 Working date set to 2006-04-26.
>
>501 Could not read config file /etc/amanda/DailySet/amanda.conf!
>
>
>I've checked amindexd logs:
>
>backup:/var/log/amanda# vi amindexd.20060426132954.debug
>
>amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26
>13:23:57 2006
>
>amindexd: version 2.5.0
>
>amindexd: < 220 backup AMANDA index server (2.5.0) ready.
>
>amindexd: > SECURITY USER root
>
>bsd security: remote host backup.gpsa.fr user root local user backup
>
>amindexd: < 200 Access OK
>
>amindexd: > FEATURES feff9ffe07
>
>amindexd: < 200 FEATURES feff9ffe07
>
>amindexd: > DATE 2006-04-26
>
>amindexd: < 200 Working date set to 2006-04-26.
>
>amindexd: > SCNF DailySet
>
>could not open conf file "/etc/amanda/DailySet/amanda.conf":
> Permission denied
>
>amindexd: < 501 Could not read config file
> /etc/amanda/DailySet/amanda.conf!
>
>
>
>My permissions for /etc/amanda/DailySet/amanda.conf:
>
>backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
>-rwxrwx---  1 root amanda 4451 2006-04-25 16:19
>/etc/amanda/DailySet/amanda.conf
>
>I don't understand why it complain about that...

You've apparently edited the amanda.conf as root (never do that, always 
become amanda to do that) and the perms are now fubar.  It should look 
something like this:

-rw-r--r--  1 amanda disk 22049 Apr 16 
08:59 /usr/local/etc/amanda/Daily/amanda.conf

The user amanda should be a member of the group disk or backup. AFAIK, 
there is no group 'amanda', at least not here.

Is this a new install?


>Any help would be appreciate
>
>
>Thomas

-- 
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

permission problem with amrecover

[Thomas Ginestet]

Hi list,

Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems occured.

After playing with  access not allowed error, I'm still stuck on the 
following one:


backup:/# amrecover DailySet

AMRECOVER Version 2.5.0. Contacting server on backup ...

220 backup AMANDA index server (2.5.0) ready.

200 Access OK

Setting restore date to today (2006-04-26)

200 Working date set to 2006-04-26.

501 Could not read config file /etc/amanda/DailySet/amanda.conf!


I've checked amindexd logs:

backup:/var/log/amanda# vi amindexd.20060426132954.debug

amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26 
13:23:57 2006


amindexd: version 2.5.0

amindexd: < 220 backup AMANDA index server (2.5.0) ready.

amindexd: > SECURITY USER root

bsd security: remote host backup.gpsa.fr user root local user backup

amindexd: < 200 Access OK

amindexd: > FEATURES feff9ffe07

amindexd: < 200 FEATURES feff9ffe07

amindexd: > DATE 2006-04-26

amindexd: < 200 Working date set to 2006-04-26.

amindexd: > SCNF DailySet

could not open conf file "/etc/amanda/DailySet/amanda.conf": Permission 
denied


amindexd: < 501 Could not read config file /etc/amanda/DailySet/amanda.conf!



My permissions for /etc/amanda/DailySet/amanda.conf:

backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf
-rwxrwx---  1 root amanda 4451 2006-04-25 16:19 
/etc/amanda/DailySet/amanda.conf


I don't understand why it complain about that...

Any help would be appreciate


Thomas

Re: Problem with amrecover

[Jon LaBadie]

On Fri, Feb 04, 2005 at 11:21:07AM -, soed2003 wrote:
> 
> --- In [EMAIL PROTECTED], Jon LaBadie <[EMAIL PROTECTED]> wrote:
> > On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
> > > Hi!
> > > 
> > > I have problem using amrecover. I get the following output:
> > > 
> > > amidxtaped: time 0.002: Ready to execv amrestore with:
> > > path = /usr/local/sbin/amrestore
> > > argv[0] = "amrestore"
> > > argv[1] = "-p"
> > > argv[2] = "-h"
> > > argv[3] = "/dev/nst0"
> > > argv[4] = "^zampo.edzen.net$"
> > > argv[5] = "^/usr/local/cvsroot$"
> > > argv[6] = "20050115"
> > 
> > As the exact amrestore command is shown,
> > can you reproduce the error by running it manually?
> > 
> > If so, it may be time to try and pull off manually
> > some of the tape files and see if they are recorded
> > correctly.  This will involve using mt and dd commands.
> > Then tar or dump on the result.
> > 
> > -- 
> > Jon H. LaBadie  [EMAIL PROTECTED]
> >  JG Computing
> >  4455 Province Line Road(609) 252-0159
> >  Princeton, NJ  08540-4322  (609) 683-7220 (fax)
> 
> Hi 
> I tried the exact amrestore command and got this:
> 
> amrestore -p -h /dev/nst0 ^zampo.edzen.net$ ^/usr/local/cvsroot$ 20050204
> amrestore:   0: skipping start of tape: date 20050202 label zampo102
> amrestore:   1: skipping zampo.edzen.net._home_soredz_.mutt.20050202.0
> amrestore: error reading file header: Input/output error
> 
> How to restore with dd? mt is used to rewind the tape, right?
> 
> Any ideas? I'm getting desperate. First I had trouble getting amanda to 
> perform the 
> backups. Then when I finally made it I cant restore anything. 
> 
And of course, backups are worthless unless you can get your data back.

mt is used for more than rewinding.

Amanda backs up entities in its disklist file, aka DLE's, such as 
/home/soredz/.mutt
on zampo.edzen.net.  (Based on the above, I presume this is an entry in your
disklist file, that it is a directory, and you are using gnutar to do the backup
of this DLE, is that correct?)

Each of these DLE's is backed up to an archive file and put on tape as a single
tape file with 32KB of amanda info added at the front of the archive.  If your
disklist file has 10 DLE's, each is on the tape in a separate tape file.  Plus
there are two special amanda files, one each at the start and end of the tape.

Using unix commands like dd, mt, tar, restore, ... you should be able to
retrieve your data even with out amanda commands.  That is assuming the
data on the tape is good, the archive properly made, taped, and retrievable.

Basically you position the tape at the beginning of the tape file you want.

mt -f  rewind
mt -f  fsf 

If you want to look at which DLE this tape file contains, look at the first
32KB with dd.

dd if= bs=32k count=1

If you want the archive file on your hard disk, repeat the mt commands to
get to the start of the tape file again and use dd.

dd if= of= bs=32k skip=1

Theoretically there was no need to repeat the mt commands, you could have
done the 2 dd commands one after the other (without the skip=1)

dd if= of= bs=32k count=1
dd if= of=   bs=32k

Now you have your archive file on hard disk.  It may be compresses with gzip
and need uncompression (depends on your config settings).

You should be able to recover what is there with gnutar or your restore command
as appropriate for how the archive was made.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Problem with amrecover

[soed2003]

--- In [EMAIL PROTECTED], Jon LaBadie <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
> > Hi!
> > 
> > I have problem using amrecover. I get the following output:
> > 
> > amidxtaped: time 0.002: Ready to execv amrestore with:
> > path = /usr/local/sbin/amrestore
> > argv[0] = "amrestore"
> > argv[1] = "-p"
> > argv[2] = "-h"
> > argv[3] = "/dev/nst0"
> > argv[4] = "^zampo.edzen.net$"
> > argv[5] = "^/usr/local/cvsroot$"
> > argv[6] = "20050115"
> 
> As the exact amrestore command is shown,
> can you reproduce the error by running it manually?
> 
> If so, it may be time to try and pull off manually
> some of the tape files and see if they are recorded
> correctly.  This will involve using mt and dd commands.
> Then tar or dump on the result.
> 
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Hi 
I tried the exact amrestore command and got this:

amrestore -p -h /dev/nst0 ^zampo.edzen.net$ ^/usr/local/cvsroot$ 20050204
amrestore:   0: skipping start of tape: date 20050202 label zampo102
amrestore:   1: skipping zampo.edzen.net._home_soredz_.mutt.20050202.0
amrestore: error reading file header: Input/output error

How to restore with dd? mt is used to rewind the tape, right?

Any ideas? I'm getting desperate. First I had trouble getting amanda to perform 
the 
backups. Then when I finally made it I cant restore anything. 

Re: Problem with amrecover

[Jon LaBadie]

On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
> Hi!
> 
> I have problem using amrecover. I get the following output:
> 
> amidxtaped: time 0.002: Ready to execv amrestore with:
> path = /usr/local/sbin/amrestore
> argv[0] = "amrestore"
> argv[1] = "-p"
> argv[2] = "-h"
> argv[3] = "/dev/nst0"
> argv[4] = "^zampo.edzen.net$"
> argv[5] = "^/usr/local/cvsroot$"
> argv[6] = "20050115"

As the exact amrestore command is shown,
can you reproduce the error by running it manually?

If so, it may be time to try and pull off manually
some of the tape files and see if they are recorded
correctly.  This will involve using mt and dd commands.
Then tar or dump on the result.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Problem with amrecover

[Andreas Putzo]

On Saturday 22 January 2005 15:07, Andreas Putzo wrote:
> Hi,
>
> On Saturday 22 January 2005 14:45, Sören Edzen wrote:
> > I have problem using amrecover. I get the following output:

> Try mt -f /dev/rmt0 rewind before using amrecover or use

>> /dev/st0. I even tried to rewind the tape with mt before executing
>> amrecover.

Oh sorry, overlooked, that you already tried this.

andreas

Re: Problem with amrecover

[Andreas Putzo]

Hi,

On Saturday 22 January 2005 14:45, Sören Edzen wrote:

> I have problem using amrecover. I get the following output:
[...]
> Extracting files using tape drive /dev/nst0 on host zampo.edzen.net.
> Load tape zampo103 now
> Continue [?/Y/n/s/t]?
> EOF, check amidxtaped..debug file on zampo.edzen.net.
> amrecover: short block 0 bytes
> UNKNOWN file
> amrecover: Can't read file header
> extract_list - child returned non-zero status: 1
> -- End output amrecover ---

Try mt -f /dev/rmt0 rewind before using amrecover or use 
/dev/rmt0 with amrecover, because /dev/nst0 is the non-rewinding device 
file. If the tape is not at the beginning, amrecover can't read the whole 
tape.


regards,
andreas

Problem with amrecover

[Sören Edzen]

Hi!

I have problem using amrecover. I get the following output:

--Start output amrecover ---
[EMAIL PROTECTED]:/dist/tmp/amrecover> amrecover zampo
AMRECOVER Version 2.4.4p4. Contacting server on zampo ...
220 zampo AMANDA index server (2.4.4p4) ready.
200 Access OK
Setting restore date to today (2005-01-22)
200 Working date set to 2005-01-22.
Scanning /amanda_dump/zampo...
200 Config set to zampo.
501 Host zampo is not in your disklist.
Trying host zampo.edzen.net ...
200 Dump host set to zampo.edzen.net.
Trying disk /dist ...
Trying disk sda1 ...
Can't determine disk and mount point from $CWD '/dist/tmp/amrecover'
amrecover> setdate 2005-01-15
200 Working date set to 2005-01-15.
amrecover> setdisk /usr/local/cvsroot
200 Disk set to /usr/local/cvsroot.
amrecover> add *
Added dir / at date 2005-01-15
Added dir /.mutt at date 2005-01-15
Added dir /.vim at date 2005-01-15
Added dir /CVSROOT at date 2005-01-15
Added dir /Java-I at date 2005-01-15
Added dir /Java-II at date 2005-01-15
Added dir /Mail at date 2005-01-15
Added dir /MediaDB at date 2005-01-15
Added dir /Procmail at date 2005-01-15
Added dir /cs1 at date 2005-01-15
Added dir /edzen.net at date 2005-01-15
Added dir /edzen.org at date 2005-01-15
Added dir /etc at date 2005-01-15
Added dir /jmbreak at date 2005-01-15
Added dir /mbtimer at date 2005-01-15
Added dir /micro.se at date 2005-01-15
Added dir /microbreak.se at date 2005-01-15
Added dir /microbreak at date 2005-01-15
Added dir /stop_mbtimer at date 2005-01-15
amrecover> extract

Extracting files using tape drive /dev/nst0 on host zampo.edzen.net.
The following tapes are needed: zampo103

Restoring files into directory /dist/tmp/amrecover
Continue [?/Y/n]?

Extracting files using tape drive /dev/nst0 on host zampo.edzen.net.
Load tape zampo103 now
Continue [?/Y/n/s/t]?
EOF, check amidxtaped..debug file on zampo.edzen.net.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
-- End output amrecover ---

-- Start amidxtaped..debug -
midxtaped: debug 1 pid 14537 ruid 37 euid 37: start at Sat Jan 22
13:24:26 2005
amidxtaped: version 2.4.4p4
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.001: bsd security: remote host zampo.edzen.net
user root local user amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: > CONFIG=zampo
amidxtaped: time 0.001: > LABEL=zampo103
amidxtaped: time 0.001: > FSF=8
amidxtaped: time 0.001: > HEADER
amidxtaped: time 0.001: > DEVICE=/dev/nst0
amidxtaped: time 0.001: > HOST=^zampo.edzen.net$
amidxtaped: time 0.002: > DISK=^/usr/local/cvsroot$
amidxtaped: time 0.002: > DATESTAMP=20050115
amidxtaped: time 0.002: > END
amidxtaped: time 0.002: amrestore_nargs=0
amidxtaped: time 0.002: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^zampo.edzen.net$"
argv[5] = "^/usr/local/cvsroot$"
argv[6] = "20050115"
amrestore:   0: skipping start of tape: date 20050115 label
zampo103
amrestore:   1: skipping
zampo.edzen.net._home_soredz_.vim.20050115.0
amrestore: error reading file header: Input/output error
amidxtaped: time 3.528: amrestore terminated normally with status:
2
amidxtaped: time 3.529: rewinding tape ...
amidxtaped: time 7.595: done
amidxtaped: time 7.595: pid 14537 finish time Sat Jan 22 13:24:34
2005
-- End amidxtaped..debug ---

I have searched the amanda-users e-mail archive without finding a
satisfying solution. amdump, amcheck works fine. amverify finds
everything that should be on the tape as far as I know. I have
/dev/nst0 as device, as far as I know it's the one I should use, not
/dev/st0. I even tried to rewind the tape with mt before executing
amrecover.

The os is suse linux 9.1

Output from uname -a: Linux zampo 2.6.5-7.111.19-default #1 Fri Dec
10 15:10:58 UTC 2004 i686 athlon i386 GNU/Linux

amanda version: 2.4.4p4
gnutar version: 1.13.25-298
tapedrive: STT8000N


Is there anyone out there who has a clue on what might be the
problem for me? 

TIA
Sören

-- 
Sören Edzen, Sjöfartsgatan 22A, 97437 Luleå, Sweden
Phone: 0920-255133, Cell: 070-6531975
mailto: [EMAIL PROTECTED]

AW: AW: AW: AW: AW: AW: Problem with amrecover

[Sebastian Kösters]

>Using what method?

I do that:

Amrestore 3.client1._data.1

And then just untar it

>Look at the index files themselves for that client.  Do they exist?  What 
do the contents look like?

Where must I locate the index files?

In /var/lib/amanda/config/index/client1/_data/ ?

If yes...this Directory is empty.

-Ursprüngliche Nachricht-
Von: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 26. November 2004 15:42
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 3:39pm, Sebastian Kösters wrote

> [EMAIL PROTECTED] data]# amrecover -C config  -s 192.168.10.95 -t
192.168.10.95
> AMRECOVER Version 2.4.3. Contacting server on 192.168.10.95 ...
> 220 backup AMANDA index server (2.4.4p4) ready.
> 200 Access OK
> Setting restore date to today (2004-11-26)
> 200 Working date set to 2004-11-26.
> 200 Config set to config.
> 200 Dump host set to client1.
> Trying disk /data ...
> $CWD '/data' is on disk '/data' mounted at '/data'.
> 200 Disk set to /data.
> No index records for disk for specified date
> If date correct, notify system administrator
> Invalid directory - /data
> 
> The date on both servers ist correct.
> 
> If I restore the backup on the Server everything is ok. 

Using what method?

> The dirs are fine too.

Look at the index files themselves for that client.  Do they exist?  What 
do the contents look like?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: AW: AW: AW: AW: AW: AW: Problem with amrecover

[Sebastian Kösters]

Thanks very much!


-Ursprüngliche Nachricht-
Von: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 26. November 2004 15:48
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 3:47pm, Sebastian Kösters wrote

> >Look at the index files themselves for that client.  Do they exist?  What

> do the contents look like?
> 
> Where must I locate the index files?

Whereever amanda.conf tells you the 'indexdir' is.

> In /var/lib/amanda/config/index/client1/_data/ ?
> 
> If yes...this Directory is empty.

If your indexdir is empty, then you likely haven't turned on indexing in 
your dumptypes.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: AW: AW: AW: AW: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 3:47pm, Sebastian Kösters wrote

> >Look at the index files themselves for that client.  Do they exist?  What 
> do the contents look like?
> 
> Where must I locate the index files?

Whereever amanda.conf tells you the 'indexdir' is.

> In /var/lib/amanda/config/index/client1/_data/ ?
> 
> If yes...this Directory is empty.

If your indexdir is empty, then you likely haven't turned on indexing in 
your dumptypes.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: AW: AW: AW: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 3:39pm, Sebastian Kösters wrote

> [EMAIL PROTECTED] data]# amrecover -C config  -s 192.168.10.95 -t 
> 192.168.10.95
> AMRECOVER Version 2.4.3. Contacting server on 192.168.10.95 ...
> 220 backup AMANDA index server (2.4.4p4) ready.
> 200 Access OK
> Setting restore date to today (2004-11-26)
> 200 Working date set to 2004-11-26.
> 200 Config set to config.
> 200 Dump host set to client1.
> Trying disk /data ...
> $CWD '/data' is on disk '/data' mounted at '/data'.
> 200 Disk set to /data.
> No index records for disk for specified date
> If date correct, notify system administrator
> Invalid directory - /data
> 
> The date on both servers ist correct.
> 
> If I restore the backup on the Server everything is ok. 

Using what method?

> The dirs are fine too.

Look at the index files themselves for that client.  Do they exist?  What 
do the contents look like?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: AW: AW: AW: AW: Problem with amrecover

[Sebastian Kösters]

Next Problem.

[EMAIL PROTECTED] data]# amrecover -C config  -s 192.168.10.95 -t 192.168.10.95
AMRECOVER Version 2.4.3. Contacting server on 192.168.10.95 ...
220 backup AMANDA index server (2.4.4p4) ready.
200 Access OK
Setting restore date to today (2004-11-26)
200 Working date set to 2004-11-26.
200 Config set to config.
200 Dump host set to client1.
Trying disk /data ...
$CWD '/data' is on disk '/data' mounted at '/data'.
200 Disk set to /data.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /data

The date on both servers ist correct.

If I restore the backup on the Server everything is ok. 

The dirs are fine too.

-Ursprüngliche Nachricht-
Von: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 26. November 2004 14:50
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 2:48pm, Sebastian Kösters wrote

> Iptables is disabled on both.
> 
> 
> /tmp/amanda on Server is empty
> 
> On Client there are 1260 files namend
> 
> Amandad.xxx.debug
> 
> Amrecover.xx.debug
> 
> Runtar.xxx.debug
> 
> Selfcheck._dir.x.debug
> 
> Sendbackup.xx.debug
> 
> Sendsize.xx.debug
> 
> An amrecover entry looks like this
> 
> amrecover: debug 1 pid 21327 ruid 0 euid 0: start at Fri Nov 26 13:25:44
> 2004
> amrecover: stream_client_privileged: connect to 192.168.10.95.10082
failed:
> Connection refused
> amrecover: cannot connect to 192.168.10.95: Connection refused
> amrecover: pid 21327 finish time Fri Nov 26 13:25:44 2004

And do you have xinetd entries for amindexd and amidxtaped on the server?  
What does '/sbin/chkconfig --list' look like on the server?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: AW: AW: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 2:48pm, Sebastian Kösters wrote

> Iptables is disabled on both.
> 
> 
> /tmp/amanda on Server is empty
> 
> On Client there are 1260 files namend
> 
> Amandad.xxx.debug
> 
> Amrecover.xx.debug
> 
> Runtar.xxx.debug
> 
> Selfcheck._dir.x.debug
> 
> Sendbackup.xx.debug
> 
> Sendsize.xx.debug
> 
> An amrecover entry looks like this
> 
> amrecover: debug 1 pid 21327 ruid 0 euid 0: start at Fri Nov 26 13:25:44
> 2004
> amrecover: stream_client_privileged: connect to 192.168.10.95.10082 failed:
> Connection refused
> amrecover: cannot connect to 192.168.10.95: Connection refused
> amrecover: pid 21327 finish time Fri Nov 26 13:25:44 2004

And do you have xinetd entries for amindexd and amidxtaped on the server?  
What does '/sbin/chkconfig --list' look like on the server?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: AW: AW: AW: Problem with amrecover

[Sebastian Kösters]

Iptables is disabled on both.


/tmp/amanda on Server is empty

On Client there are 1260 files namend

Amandad.xxx.debug

Amrecover.xx.debug

Runtar.xxx.debug

Selfcheck._dir.x.debug

Sendbackup.xx.debug

Sendsize.xx.debug

An amrecover entry looks like this

amrecover: debug 1 pid 21327 ruid 0 euid 0: start at Fri Nov 26 13:25:44
2004
amrecover: stream_client_privileged: connect to 192.168.10.95.10082 failed:
Connection refused
amrecover: cannot connect to 192.168.10.95: Connection refused
amrecover: pid 21327 finish time Fri Nov 26 13:25:44 2004

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im
Auftrag von Joshua Baker-LePain
Gesendet: Freitag, 26. November 2004 14:22
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 2:20pm, Sebastian Kösters wrote

> Everything is like you said but it does not work.
> 
> It’s a testnetwork --> no firewall

So iptables is completely disabled?  On both hosts?

If so, are there any files created in /tmp/amanda on the server when you 
try to run amrecover?  What about on the client?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: AW: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 2:20pm, Sebastian Kösters wrote

> Everything is like you said but it does not work.
> 
> It’s a testnetwork --> no firewall

So iptables is completely disabled?  On both hosts?

If so, are there any files created in /tmp/amanda on the server when you 
try to run amrecover?  What about on the client?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: AW: AW: Problem with amrecover

[Sebastian Kösters]

Everything is like you said but it does not work.

It’s a testnetwork --> no firewall

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im
Auftrag von Joshua Baker-LePain
Gesendet: Freitag, 26. November 2004 14:12
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 2:10pm, Sebastian Kösters wrote

> I even got the same error ;(
> 
> host.allow: 
> 
> amindexd, amidxtaped: 192.168.10.22
> 
> host.deny is empty

Those should both be hosts (/etc/hosts.allow, /etc/hosts.deny).  Also, 
check your firewall settings.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 2:10pm, Sebastian Kösters wrote

> I even got the same error ;(
> 
> host.allow: 
> 
> amindexd, amidxtaped: 192.168.10.22
> 
> host.deny is empty

Those should both be hosts (/etc/hosts.allow, /etc/hosts.deny).  Also, 
check your firewall settings.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: AW: Problem with amrecover

[Sebastian Kösters]

I even got the same error ;(

host.allow: 

amindexd, amidxtaped: 192.168.10.22

host.deny is empty

-Ursprüngliche Nachricht-
Von: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 26. November 2004 14:03
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: Problem with amrecover

On Fri, 26 Nov 2004 at 1:58pm, Sebastian Kösters wrote

> Hi and thanks,
> 
> new .amandahosts entry on Server now looks like this:
> 
> localhost amanda
> localhost.localdomain amanda
> backup amanda
> client1 root
> 
> what must an entry in /etc/hosts.allow look like?

amindexd, amidxtaped: client1'sIPaddress

Of course, that's assuming you have ALL : ALL in hosts.deny.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: AW: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 1:58pm, Sebastian Kösters wrote

> Hi and thanks,
> 
> new .amandahosts entry on Server now looks like this:
> 
> localhost amanda
> localhost.localdomain amanda
> backup amanda
> client1 root
> 
> what must an entry in /etc/hosts.allow look like?

amindexd, amidxtaped: client1'sIPaddress

Of course, that's assuming you have ALL : ALL in hosts.deny.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

AW: Problem with amrecover

[Sebastian Kösters]

Hi and thanks,

new .amandahosts entry on Server now looks like this:

localhost amanda
localhost.localdomain amanda
backup amanda
client1 root

what must an entry in /etc/hosts.allow look like?

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im
Auftrag von Joshua Baker-LePain
Gesendet: Freitag, 26. November 2004 13:50
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: Problem with amrecover

On Fri, 26 Nov 2004 at 1:45pm, Sebastian Kösters wrote

> Hi,
> 
> i got a Problem with amrecover.
> 
> If I try to connect to the backupserver I got this error:
> 
> AMRECOVER Version 2.4.4p4. Contacting server on 192.168.10.95 ...
> amrecover: cannot connect to 192.168.10.95: Connection refused

Are you running amrecover as root?  You should be.  And, thus

> .amandahosts look like this (on server) :
> 
> localhost amanda
> localhost.localdomain amanda
> backup amanda

you need an entry for root from the client in the server's .amandahosts 
file.

You also need to make sure that hosts.allow on the server allows amindexd 
and amidxtaped from the client.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Problem with amrecover

[Joshua Baker-LePain]

On Fri, 26 Nov 2004 at 1:45pm, Sebastian Kösters wrote

> Hi,
> 
> i got a Problem with amrecover.
> 
> If I try to connect to the backupserver I got this error:
> 
> AMRECOVER Version 2.4.4p4. Contacting server on 192.168.10.95 ...
> amrecover: cannot connect to 192.168.10.95: Connection refused

Are you running amrecover as root?  You should be.  And, thus

> .amandahosts look like this (on server) :
> 
> localhost amanda
> localhost.localdomain amanda
> backup amanda

you need an entry for root from the client in the server's .amandahosts 
file.

You also need to make sure that hosts.allow on the server allows amindexd 
and amidxtaped from the client.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Problem with amrecover

[Sebastian Kösters]

Hi,

i got a Problem with amrecover.

If I try to connect to the backupserver I got this error:

AMRECOVER Version 2.4.4p4. Contacting server on 192.168.10.95 ...
amrecover: cannot connect to 192.168.10.95: Connection refused

hosts on server looks like this:

127.0.0.1   backup localhost.localdomain localhost
192.168.10.22   client1
192.168.10.189 client2

.amandahosts look like this (on server) :

localhost amanda
localhost.localdomain amanda
backup amanda


The hosts on the Client looks like this: 

192.168.10.95 backup

.amandahosts looks like this:

localhost amanda
localhost.localdomain amanda
backup amanda
backup root

taking a backup from this Client works fine.

Both (Server and Client) are in the same Network.

No errors in log.

What can I do?

Amanda V: 2.4.4p4
OS: Fedora 3
Client OS: Fedora 3

Regards,
Sebastian 

Re: Problem with amrecover

[Frank Smith]

--On Wednesday, August 04, 2004 05:53:22 +0100 Alvaro Rosales <[EMAIL PROTECTED]> 
wrote:

> Hi guys,
> I finally had been able to make backups with mi amanda sever, but when I try to run 
> amrecover I get this error:
> amindexd: time 0.093: check failed: [access as operator not allowed from [EMAIL 
> PROTECTED]
> lim951-2.pe.yr.com.] amandahostsauth failed
> 
> My client .amandahosts file list the server 
> and my server .amadahosts file lits the client 

For backups, you need the amanda user in the .amadahosts file on the
clinet (and the server if it is also a client).  It looks like you're
using the user 'operator' for backups.

For restores, amrecover and amrestore need to be run as root, so you need
an entry for the remote machine's root in the file on the tape server.

The error message tells you what it sees for the connection,  Look for the
string that looks like an email address '[EMAIL PROTECTED]',
split on the '@' and reverse it, like this:

fslim951-2.pe.yr.com root

and add that to your tape server's .amandahosts file.

Frank

> 
> 
> Any ideas?
> Thanks a lot
> 
>  Original Message -
> From: "Stefan G. Weichinger" <[EMAIL PROTECTED]>
> Date: Wed, 4 Aug 2004 01:14:04 +0200
> To: [EMAIL PROTECTED]
> Subject: AMANDA Documentation at www.oops.co.at
> 
>> 
>> Hello, amanda-users,
>> 
>> about one month has gone now, since I put a pre-release of "The
>> Official AMANDA Documentation" online at
>> http://www.oops.co.at/AMANDA-docs/index.html
>> 
>> This was just meant as a ground for discussion (for
>> amanda-core-members), but it seems to hit the needs of several more
>> people:
>> 
>> The hits at www.oops.co.at have risen since then, and still rise.
>> 
>> No problem with that, just some thoughts:
>> 
>> - The current info is just equivalent to the infos in the (in some
>> parts outdated and incorrect :-( ) AMANDA-docs.
>> 
>> - The current formatting is far from being complete, there is much
>> potential for improvement (think XML-tags, indexing, ...)
>> 
>> Given the fact that I am more than busy with other
>> documentation-related tasks I just want to tell all of you that:
>> 
>> - every kind of correction is welcome.
>> - every kind of addition is welcome.
>> 
>> Feel free to express your thoughts, I will try the best to transform
>> your input into contributions to AMANDA.
>> 
>> best regards,
>> Stefan G. Weichinger
>> 
> 
> -- 
> _
> Web-based SMS services available at http://www.operamail.com.
> From your mailbox to local or overseas cell phones.
> 
> Powered by Outblaze

Problem with amrecover

[Alvaro Rosales]

Hi guys,
I finally had been able to make backups with mi amanda sever, but when I try to run 
amrecover I get this error:
amindexd: time 0.093: check failed: [access as operator not allowed from [EMAIL 
PROTECTED]
lim951-2.pe.yr.com.] amandahostsauth failed

My client .amandahosts file list the server 
and my server .amadahosts file lits the client 


Any ideas?
Thanks a lot

 Original Message -
From: "Stefan G. Weichinger" <[EMAIL PROTECTED]>
Date: Wed, 4 Aug 2004 01:14:04 +0200
To: [EMAIL PROTECTED]
Subject: AMANDA Documentation at www.oops.co.at

> 
> Hello, amanda-users,
> 
> about one month has gone now, since I put a pre-release of "The
> Official AMANDA Documentation" online at
> http://www.oops.co.at/AMANDA-docs/index.html
> 
> This was just meant as a ground for discussion (for
> amanda-core-members), but it seems to hit the needs of several more
> people:
> 
> The hits at www.oops.co.at have risen since then, and still rise.
> 
> No problem with that, just some thoughts:
> 
> - The current info is just equivalent to the infos in the (in some
> parts outdated and incorrect :-( ) AMANDA-docs.
> 
> - The current formatting is far from being complete, there is much
> potential for improvement (think XML-tags, indexing, ...)
> 
> Given the fact that I am more than busy with other
> documentation-related tasks I just want to tell all of you that:
> 
> - every kind of correction is welcome.
> - every kind of addition is welcome.
> 
> Feel free to express your thoughts, I will try the best to transform
> your input into contributions to AMANDA.
> 
> best regards,
> Stefan G. Weichinger
> 

-- 
_
Web-based SMS services available at http://www.operamail.com.
>From your mailbox to local or overseas cell phones.

Powered by Outblaze

Re: Problem with amrecover and tapeless

[Marc Langlois]

Pascal,

I recall a similar error when the chg-disk changer wasn't setting the
"data" sym-link to the correct "tape" slot. Try using the command:

settape chg-disk

before doing the extract. It also worked if I manually ran the command:

amtape  slot 

in another window before doing the extract.

I eventually got the config right in amanda.conf, and it works properly
now. Here are my relevant amanda.conf entries:

runtapes 1 
tpchanger "chg-disk" 
tapedev "file:/d1/amanda_tapes" 
rawtapedev "file:/d1/amanda_tapes"
changerfile "/usr/local/etc/amanda/daily/changer"
changerdev "/dev/null"
amrecover_changer "changer"

Marc Langlois.

On Wed, 2004-02-25 at 08:12, Pascal Robert wrote:
> Hi,
> 
> we are doing backups on hard drives, this part works fine, but when I 
> try to do a recover, I get this error "EOF, check amidxtaped.debug 
> file".  This is a except from my session:
> 
> [EMAIL PROTECTED] /]# /usr/sbin/amrecover -s .xx.cesart.com -t 
> .xx.cesart.com -C Hosting
> AMRECOVER Version 2.4.2p2. Contacting server on .xxx.cesart.com ...
> 220 backup AMANDA index server (2.4.4p2) ready.
> 200 Access OK
> Setting restore date to today (2004-02-25)
> 200 Working date set to 2004-02-25.
> Scanning /backups/amandadumps/holding...
> 200 Config set to Hosting.
> 200 Dump host set to xx.cesart.com.
> $CWD '/' is on disk '/' mounted at '/'.
> 200 Disk set to /.
> /
> amrecover> cd home/probert
> /home/probert
> amrecover> add MMI-030922.host-b.gz
> Added /home/probert/MMI-030922.host-b.gz
> amrecover> list
> TAPE Hosting08 LEVEL 2 DATE 2004-02-25
>  /home/probert/MMI-030922.host-b.gz
> amrecover> settape .xx.cesart.com:file:/backups/amandadumps/tape08
> Using tape file:/backups/amandadumps/tape08 from server 
> backup.01.cesart.com.
> amrecover> extract
> 
> Extracting files using tape drive file:/backups/amandadumps/tape08 on 
> host backup.01.cesart.com.
> The following tapes are needed: Hosting08
> 
> Restoring files into directory /
> Continue? [Y/n]: y
> 
> Load tape Hosting08 now
> Continue? [Y/n]: y
> EOF, check amidxtaped.debug file on .xx.cesart.com.
> 
> And in the debug file:
> 
> amidxtaped: time 0.000: Ready to execv amrestore with:
> path = /usr/local/amanda/sbin/amrestore
> argv[0] = "amrestore"
> argv[1] = "-h"
> argv[2] = "-p"
> argv[3] = "file:/backups/amandadumps/tape08"
> argv[4] = "x.cesart.com"
> argv[5] = "^/$"
> argv[6] = "20040225"
> amrestore: WARNING: not at start of tape, file numbers will be offset
> amrestore:   0: reached end of information
> amidxtaped: time 0.002: amrestore terminated normally with status: 1
> amidxtaped: time 0.002: rewinding tape ...
> amidxtaped: time 0.002: done
> amidxtaped: time 0.002: pid 2491 finish time Wed Feb 25 09:31:20 2004

Re: Problem with amrecover

[Uwe Beger]

On Tuesday 24 February 2004 15:36, Stefan G. Weichinger wrote:
> Hi, Bram Metsch,
> on Dienstag, 24. Februar 2004 at 15:19 you wrote to amanda-users:
> the archive. Or am I too naive to assume they would read the docs?
I'm afraid you are right ;-)
Uwe.

Problem with amrecover and tapeless

[Pascal Robert]

Hi,

we are doing backups on hard drives, this part works fine, but when I 
try to do a recover, I get this error "EOF, check amidxtaped.debug 
file".  This is a except from my session:

[EMAIL PROTECTED] /]# /usr/sbin/amrecover -s .xx.cesart.com -t 
.xx.cesart.com -C Hosting
AMRECOVER Version 2.4.2p2. Contacting server on .xxx.cesart.com ...
220 backup AMANDA index server (2.4.4p2) ready.
200 Access OK
Setting restore date to today (2004-02-25)
200 Working date set to 2004-02-25.
Scanning /backups/amandadumps/holding...
200 Config set to Hosting.
200 Dump host set to xx.cesart.com.
$CWD '/' is on disk '/' mounted at '/'.
200 Disk set to /.
/
amrecover> cd home/probert
/home/probert
amrecover> add MMI-030922.host-b.gz
Added /home/probert/MMI-030922.host-b.gz
amrecover> list
TAPE Hosting08 LEVEL 2 DATE 2004-02-25
/home/probert/MMI-030922.host-b.gz
amrecover> settape .xx.cesart.com:file:/backups/amandadumps/tape08
Using tape file:/backups/amandadumps/tape08 from server 
backup.01.cesart.com.
amrecover> extract

Extracting files using tape drive file:/backups/amandadumps/tape08 on 
host backup.01.cesart.com.
The following tapes are needed: Hosting08

Restoring files into directory /
Continue? [Y/n]: y
Load tape Hosting08 now
Continue? [Y/n]: y
EOF, check amidxtaped.debug file on .xx.cesart.com.
And in the debug file:

amidxtaped: time 0.000: Ready to execv amrestore with:
path = /usr/local/amanda/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "file:/backups/amandadumps/tape08"
argv[4] = "x.cesart.com"
argv[5] = "^/$"
argv[6] = "20040225"
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore:   0: reached end of information
amidxtaped: time 0.002: amrestore terminated normally with status: 1
amidxtaped: time 0.002: rewinding tape ...
amidxtaped: time 0.002: done
amidxtaped: time 0.002: pid 2491 finish time Wed Feb 25 09:31:20 2004

Re: Problem with amrecover

[stan]

On Tue, Feb 24, 2004 at 03:09:52PM +0100, [EMAIL PROTECTED] wrote:
> Hi amanda-users,
> 
> I'm trying to do an "amrecover" as root (because amanda tells me to do so as
> root... ) to recover files on the amanda-server itself, but I just get the
> following error-message:
> 
> "500 Access not allowed: [access as amanda not allowed from
> [EMAIL PROTECTED] amandahostsauth failed"

You have to add a line in .amandahost allowing root. This is _NOT_
required, untill you go to restore. Been there, doen that :-(
-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin

RE: Problem with amrecover

[Jack Parker]

Now that you ask I can't find it.  I found something originally (I
thought) through www.amanda.org.  The link you provide is similar, in
that it is still doing it month to month, but has added features to
allow one to retain the search criteria for each month.  Thanks - I'll
have a deeper look now.

Regards,
Jack Parker

> -Original Message-
> From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 24, 2004 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with amrecover
> 
> Hi, Jack,
> 
> on Dienstag, 24. Februar 2004 at 16:02 you wrote to amanda-users:
> 
> JP> Personally, trying to browse the archives was rather difficult, I
had
> to
> JP> visit each month's worth of posts and search within it - each time
I
> JP> would find a dozen or more matches for my samba query, none of
which
> JP> resolved my question - which someday I may even ask.  Is there a
> better
> JP> searchable interface to the archives?
> 
> Better than what? Which one did you use?
> 
> When I have to use an archive aside from my personal one, I often use
> 
> http://marc.theaimsgroup.com/?l=amanda-users&r=1&w=2
> 
> You can search through all the archive there, not only per month.
> --
> best regards,
> Stefan
> 
> Stefan G. Weichinger
> mailto:[EMAIL PROTECTED]
> 
> 
> 
> 
> 

Re: Problem with amrecover

[Stefan G. Weichinger]

Hi, Jack,

on Dienstag, 24. Februar 2004 at 16:02 you wrote to amanda-users:

JP> Personally, trying to browse the archives was rather difficult, I had to
JP> visit each month's worth of posts and search within it - each time I
JP> would find a dozen or more matches for my samba query, none of which
JP> resolved my question - which someday I may even ask.  Is there a better
JP> searchable interface to the archives?

Better than what? Which one did you use?

When I have to use an archive aside from my personal one, I often use

http://marc.theaimsgroup.com/?l=amanda-users&r=1&w=2

You can search through all the archive there, not only per month.
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

RE: Problem with amrecover

[Jack Parker]

Personally, trying to browse the archives was rather difficult, I had to
visit each month's worth of posts and search within it - each time I
would find a dozen or more matches for my samba query, none of which
resolved my question - which someday I may even ask.  Is there a better
searchable interface to the archives?

Regards,
Jack Parker


> -Original Message-
> From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 24, 2004 9:37 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with amrecover
> 
> Hi, Bram Metsch,
> 
> on Dienstag, 24. Februar 2004 at 15:19 you wrote to amanda-users:
> 
> BM> On Tue, 24 Feb 2004 15:09:52 +0100
> BM> [EMAIL PROTECTED] wrote:
> 
> >> "500 Access not allowed: [access as amanda not allowed from
> >> [EMAIL PROTECTED] amandahostsauth failed"
> >>
> >> What am I doing wrong?
> 
> BM> Hello Henning,
> BM> on your amanda server, you have to put a line
> BM> localhost.localdomain root
> BM> into your .amandahosts file.
> 
> localhost-question.
> second time within 4 hours.
> 
> This should REALLY go into the docs soon, as people don't even browse
> the archive. Or am I too naive to assume they would read the docs?
> --
> best regards,
> Stefan
> 
> Stefan G. Weichinger
> mailto:[EMAIL PROTECTED]
> 
> 
> 
> 
> 

Re: Problem with amrecover

[Stefan G. Weichinger]

Hi, Bram Metsch,

on Dienstag, 24. Februar 2004 at 15:19 you wrote to amanda-users:

BM> On Tue, 24 Feb 2004 15:09:52 +0100
BM> [EMAIL PROTECTED] wrote:

>> "500 Access not allowed: [access as amanda not allowed from
>> [EMAIL PROTECTED] amandahostsauth failed"
>> 
>> What am I doing wrong?

BM> Hello Henning,
BM> on your amanda server, you have to put a line
BM> localhost.localdomain root
BM> into your .amandahosts file.

localhost-question.
second time within 4 hours.

This should REALLY go into the docs soon, as people don't even browse
the archive. Or am I too naive to assume they would read the docs?
-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:[EMAIL PROTECTED]

Re: Problem with amrecover

[Bram Metsch]

On Tue, 24 Feb 2004 15:09:52 +0100
[EMAIL PROTECTED] wrote:

> Hi amanda-users,
> 
> I'm trying to do an "amrecover" as root (because amanda tells me to do so as
> root... ) to recover files on the amanda-server itself, but I just get the
> following error-message:
> 
> "500 Access not allowed: [access as amanda not allowed from
> [EMAIL PROTECTED] amandahostsauth failed"
> 
> What am I doing wrong?
> 
> Best regards
> Henning
> 
> 

Hello Henning,

on your amanda server, you have to put a line

localhost.localdomain root

into your .amandahosts file.



Bram.


pgp0.pgp
Description: PGP signature

Problem with amrecover

[Henning . Grosskurth]

Hi amanda-users,

I'm trying to do an "amrecover" as root (because amanda tells me to do so as
root... ) to recover files on the amanda-server itself, but I just get the
following error-message:

"500 Access not allowed: [access as amanda not allowed from
[EMAIL PROTECTED] amandahostsauth failed"

What am I doing wrong?

Best regards
Henning

Re: problem with amrecover

[Paul Bijnens]

Andreas Otto wrote:


07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0368.htm,v 
Symptom of tar version 1.13.  Bad, very bad.
You need tar.1.13.19 at least, or better yet 1.13.25.
Get it from:
ftp://alpha.gnu.org/gnu/tar/tar-1.13.25.tar.gz

You can fix your indexes by stripping off the leading digits, up to
the first dot:
(untested, use at your own risk)

gunzip *.gz
perl -i.bak -e 's!^\d+/\.!!' *
gzip *
rm *.bak.gz   # after verification of the results :-)
--
Paul Bijnens, XplanationTel  +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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

problem with amrecover

[Andreas Otto]

Hi,

  just the plain data .

1.SunOS  5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-5_10

[EMAIL PROTECTED]:_export_home> pwd
  /export/home/amanda/Daily/index//_export_home
3. just an example 
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0368.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0369.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0370.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0371.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0372.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0373.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0374.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0375.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0376.htm,v
4. and now the problem 
amrecover> pwd
/export/home/aotto/.REPOSITORY
amrecover> ls
2003-10-10 TTWOS.CVS/
question? why does I not see the "TacClient" directory



mfg

  aotto

Re: Problem with amrecover

[Bartho Saaiman]

Hi Nicki and others that replied.

Eventually found the problem after running strace amrecover which 
indicated that it was refused connection to port 10082 (amandaidx). On 
closer inspection I found that amandaidx (/etc/xinetd.d/amandaidx) was 
actually disabled and this led to my problems.

Moral of the story check your configs again and again. :)

Nicki Messerschmidt wrote:
Bartho Saaiman wrote:

I am trying to restore from a tape using amrecover. If I use
amrecover DailyBackup it says:
> AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
> amrecover: cannot connect to localhost: Connection refused
This sound like your inetd isn't started. Otherwise you would get a
message like "Access from [EMAIL PROTECTED] not allowed"... Or did you
play with your firewall/hosts.(allow|deny) files?
Cheers
Nicki
--
# Bartho Saaiman
# Network Administrator
# Stellenbosch Automotive Engineering
# Tel :: 27 21 882 8820 x 215
# Cell :: 27 82 551 2703
# Email :: bartho @ cae.co.za

Re: Problem with amrecover

[Nicki Messerschmidt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bartho Saaiman wrote:
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
This sound like your inetd isn't started. Otherwise you would get a
message like "Access from [EMAIL PROTECTED] not allowed"... Or did you
play with your firewall/hosts.(allow|deny) files?


Cheers
Nicki

- -- 
Linksystem Muenchen GmbH  [EMAIL PROTECTED]
Schloerstrasse 10   http://www.link-m.de
80634 Muenchen  Tel. 089 / 890 518-0
We make the Net work.   Fax 089 / 890 518-77

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use 
Comment: Keys at: https://www.link-m.de/pgp

iQA/AwUBPoRdres1nPm17iBDEQKWtwCfceUV74VlFWPnTY5Qdttas0se3V0AoIT7
QZ5aDKzsyqejy+zte4irYKwg
=qcaD
-END PGP SIGNATURE-

Re: Problem with amrecover

[Stephen Carville]

Are backup and localhost different machines? 

On Thursday 27 March 2003 10:17 pm, Bartho Saaiman wrote:
> Hi All :)
> 
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
> 
> If I use the -s backup and/or -t backup I also get the same:
>  > AMRECOVER Version 2.4.2p2. Contacting server on backup ...
>  > amrecover: cannot connect to backup: Connection refused
> 
> I previously had a similar problem and rectified this by editing the
> /var/lib/amanda/.amandahosts and added localhost root to the file. 
Tried 
> this as I am running amrecover as root but still could not fix it.
> 
> Any suggestions on what I am missing??
> 
> -- 
> # Bartho Saaiman
> # Network Administrator
> # Stellenbosch Automotive Engineering
> # Tel :: 27 21 882 8820 x 215
> # Email :: bartho @ cae.co.za
> 
> 

-- 
Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
===
The difference between robbery and taxes is simple:   The first is 
someone threatening to hurt you if you do not give them your money.   
The second is legal.

Re: Problem with amrecover

[Laas Toom]

If i am not mistaken, then .amandahosts must contain all of the
users & machines that need access to that machine. So edit the
.amandahosts file on the BACKUP server and add lines to allow you to
access from the host recover-host with user root:

recover-host root
recover-host.domain root
192.168.0.xx root

(added all of the possible ways just to be sure that you get what you want
(it depends on amanda and machines conf, which of the lines gets to be
used, so i have all of them in my .amandahosts file)


Laas Toom

On Fri, 28 Mar 2003, Bartho Saaiman wrote:

> Hi All :)
>
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
>
> If I use the -s backup and/or -t backup I also get the same:
>  > AMRECOVER Version 2.4.2p2. Contacting server on backup ...
>  > amrecover: cannot connect to backup: Connection refused
>
> I previously had a similar problem and rectified this by editing the
> /var/lib/amanda/.amandahosts and added localhost root to the file. Tried
> this as I am running amrecover as root but still could not fix it.
>
> Any suggestions on what I am missing??
>
> --
> # Bartho Saaiman
> # Network Administrator
> # Stellenbosch Automotive Engineering
> # Tel :: 27 21 882 8820 x 215
> # Email :: bartho @ cae.co.za
>

Problem with amrecover

[Bartho Saaiman]

Hi All :)

I am trying to restore from a tape using amrecover. If I use
amrecover DailyBackup it says:
> AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
> amrecover: cannot connect to localhost: Connection refused
If I use the -s backup and/or -t backup I also get the same:
> AMRECOVER Version 2.4.2p2. Contacting server on backup ...
> amrecover: cannot connect to backup: Connection refused
I previously had a similar problem and rectified this by editing the
/var/lib/amanda/.amandahosts and added localhost root to the file. Tried 
this as I am running amrecover as root but still could not fix it.

Any suggestions on what I am missing??

--
# Bartho Saaiman
# Network Administrator
# Stellenbosch Automotive Engineering
# Tel :: 27 21 882 8820 x 215
# Email :: bartho @ cae.co.za

Re: Problem with amrecover

[Chris Dahn]

On Thursday 20 March 2003 01:50 pm, bao wrote:
> Jon, I have done some search for Linux file size. It says:
> For ext2/3 and kernel 2.4.x, file size: ~ 4TB, filesystem size: ~ 1TB.
> Obviously, it can't be the kernel that imposes this limit. Morever, I
> was able to get a dump, using tar, of size > 9 GB. If the OS has a limit
> of 2GB, I wouldn't have gotten this far.
>
> I have a feeling that while searching for the specified file to recover,
> it somehow exhausts system mem with a size of 9 GB, in only one tar
> file. Now that is just a guess, because I don't know how tar searches
> for file in its archive.
>
> Anyone ever tried anything that big? in just on file?? and been
> successfullly recover it ???

  I have restored tar files > 9GB, but that was on a reiserfs filesystem, and 
my system has 1GB of RAM.

  I think I see your problem (someone please correct me if I just read this 
wrong):

>From your original message:
> argv[0] = "amrestore"
> argv[1] = "-p"
> argv[2] = "-h"
> argv[3] = "/home/general/testSet1"
> argv[4] = "^barracuda$"
> argv[5] = "^/junk$"
> argv[6] = "20030305"
> amrestore: error reading file header: Is a directory
> amidxtaped: time 0.006: amrestore terminated normally with status: 2
> amidxtaped: time 0.006: rewinding tape ...
> amidxtaped: time 30.105: tape_rewind: rewinding tape: 
> /home/general/testSet1: Inappropriate ioctl for device

  You didn't give the right arguments to amrestore, You specified your two 
flags "-p -h", but then gave a diskname. The next argument to amrestore must 
be either the tapedevice (e.g., /dev/nst0) or a holding file. You'll notice 
that it said, "amrestore: error reading file header: Is a directory". This is 
because it is trying to read the file header from a directory 
(/home/general/testSet1), rather than a tape. Later it says, 
"/home/general/testSet1: Inappropriate ioctl for device", because it is then 
trying to rewind the directory. Clearly this is innapropriate. :)

  Hope this helps you out.

-- 
 
|Christopher Dahn  | Software Engineering Research Group,|
|3141 Chestnut St. |   Feel the SERG!|
|Attn: CS Dept., CAT 186   | http://serg.cs.drexel.edu/  |
|Philadephia, PA  19104 -- --
|Office (PA): XXX.XXX. | OpenPGP public key:  |
|Office (NJ): XXX.XXX. | http://search.keyserver.net/ |
|Fax: XXX.XXX. |  |
 -

Re: Problem with amrecover

[bao]

Jon LaBadie wrote:
On Wed, Mar 19, 2003 at 02:18:21PM -0800, bao wrote:

As a followup to my previous mail.

I have repeatedly tried amrecover with different disks in my config. The 
small disk (with original 760 MB, after backup ~380 MB) seems to let me 
recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always 
hangs or reboots the server itself. No compression is used, just tar, in 
the config.

Does amanda impose a limit on disk size???


Amanda does not, but many OS's do.  A common file size limit is 2GB.

Jon, I have done some search for Linux file size. It says:
For ext2/3 and kernel 2.4.x, file size: ~ 4TB, filesystem size: ~ 1TB.
Obviously, it can't be the kernel that imposes this limit. Morever, I 
was able to get a dump, using tar, of size > 9 GB. If the OS has a limit 
of 2GB, I wouldn't have gotten this far.

I have a feeling that while searching for the specified file to recover, 
it somehow exhausts system mem with a size of 9 GB, in only one tar 
file. Now that is just a guess, because I don't know how tar searches 
for file in its archive.

Anyone ever tried anything that big? in just on file?? and been 
successfullly recover it ???

Re: Problem with amrecover

[Rainer Wiener]

Joshua Baker-LePain schrieb:
Is the kernel to old?


Well, given that current is 2.4.20...  It's also not a release kernel 
(note the pre).  I know nothing about Debian, but I'd strongly recommend 
upgrading at least to a released 2.2 series kernel (it's actually still 
maintained -- 2.2.25 just came out to fix the recent ptrace vulnerability) 
or to a more recent Debian release with a 2.4 series kernel.

Good luck.

After I update to the kernel 2.4.20 the recover works. Thanks to all 
that helps.

cu
Rainer
--
skilldeal - Ihr Partner für IT-Projekte
Rainer Wiener
skilldeal AG
Gitschiner Str. 94
D-10969 Berlin
Tel: +49 (0) 30  61 6558 -65/ -60
Fax: +49 (0) 30  61 6558 -66
E-Mail: [EMAIL PROTECTED]
Internet: http://www.skilldeal.com

Re: Problem with amrecover

[Jon LaBadie]

On Wed, Mar 19, 2003 at 02:18:21PM -0800, bao wrote:
> As a followup to my previous mail.
> 
> I have repeatedly tried amrecover with different disks in my config. The 
> small disk (with original 760 MB, after backup ~380 MB) seems to let me 
> recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always 
> hangs or reboots the server itself. No compression is used, just tar, in 
> the config.
> 
> Does amanda impose a limit on disk size???

Amanda does not, but many OS's do.  A common file size limit is 2GB.


-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Problem with amrecover

[bao]

As a followup to my previous mail.

I have repeatedly tried amrecover with different disks in my config. The 
small disk (with original 760 MB, after backup ~380 MB) seems to let me 
recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always 
hangs or reboots the server itself. No compression is used, just tar, in 
the config.

Does amanda impose a limit on disk size???
If so, I guess I have to split the disk into small chunks, which is 
completely undesirable.

bao wrote:
Hi list,

I'm experiencing the same problem.

My linux dist. is RH 8.0 kernel 2.4.18-19.8.0.
tar 1.13.25-8.
amdump was ok. amverify OK.
But when I ran amrecover, everything went fine until the extract step.
amanda seems to freeze.
Here's the result of amidxtaped and amrecover, respectively:

amidxtaped: debug 1 pid 1552 ruid 501 euid 501: start at Wed Mar 19 
10:52:38 2003
amidxtaped: version 2.4.4
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host snook user root local 
user general
amidxtaped: time 0.000: amandahosts security check passed
amidxtaped: time 0.000: > CONFIG=WeeklySet
amidxtaped: time 0.000: > LABEL=WeeklySet1
amidxtaped: time 0.000: > FSF=2
amidxtaped: time 0.000: > HEADER
amidxtaped: time 0.000: > DEVICE=file:/Backup/general/WeeklySet1
amidxtaped: time 0.000: > HOST=^snook$
amidxtaped: time 0.000: > DISK=^/Shared$
amidxtaped: time 0.000: > DATESTAMP=20030319
amidxtaped: time 0.000: > END
amidxtaped: time 0.001: amrestore_nargs=0
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /Backup/usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "file:/Backup/general/WeeklySet1"
argv[4] = "^snook$"
argv[5] = "^/Shared$"
argv[6] = "20030319"
amrestore:   0: skipping start of tape: date 20030319 label WeeklySet1
amrestore:   1: skipping snook._Mail.20030319.0
amrestore:   2: restoring snook._Shared.20030319.0
Error 32 (Broken pipe) offset -835747840+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amidxtaped: time 209.145: amrestore terminated normally with status: 2
amidxtaped: time 209.146: rewinding tape ...
amidxtaped: time 209.146: done
amidxtaped: time 209.146: pid 1552 finish time Wed Mar 19 10:56:07 2003

-

amrecover: debug 1 pid 1526 ruid 0 euid 0: start at Wed Mar 19 10:49:14 
2003
amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10082
amrecover: stream_client_privileged: our side is 0.0.0.0.928
guess_disk: 11: "/tmp/amanda"
guess_disk: 0: 1: "/": "rootfs"
guess_disk: local_disk = 1, fsname = "rootfs"
guess_disk: 1: 1: "/": "/dev/root"
guess_disk: 1: 5: "/proc": "/proc"
guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs"
guess_disk: 1: 5: "/boot": "/dev/hda1"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 1: "/": "/dev/hda2"
guess_disk: 1: 5: "/proc": "none"
guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs"
guess_disk: 1: 5: "/boot": "/dev/hda1"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 1: "/": "LABEL=/"
guess_disk: 1: 5: "/boot": "LABEL=/boot"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 5: "/proc": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 4: "swap": "/dev/hda3"
guess_disk: 1: 11: "/mnt/floppy": "/dev/fd0"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 10: "/mnt/cdrom": "/dev/cdrom"
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/."
...
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/bao/"
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/boot.out"
...
amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10083
amrecover: stream_client_privileged: our side is 0.0.0.0.620
amrecover: try_socksize: receive buffer size is 65536
Exec'ing /bin/gtar with arguments:
tar
-xpGvf
-
./bao/gsv42w32.exe
./bao/gs704w32.exe
./bao/WinPcap.exe
./bao/ipchains
./bao/imtool.c



Pleae tell me what's happened with amanda

Re: Problem with amrecover

[bao]

Hi list,

I'm experiencing the same problem.

My linux dist. is RH 8.0 kernel 2.4.18-19.8.0.
tar 1.13.25-8.
amdump was ok. amverify OK.
But when I ran amrecover, everything went fine until the extract step.
amanda seems to freeze.
Here's the result of amidxtaped and amrecover, respectively:

amidxtaped: debug 1 pid 1552 ruid 501 euid 501: start at Wed Mar 19 
10:52:38 2003
amidxtaped: version 2.4.4
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host snook user root local 
user general
amidxtaped: time 0.000: amandahosts security check passed
amidxtaped: time 0.000: > CONFIG=WeeklySet
amidxtaped: time 0.000: > LABEL=WeeklySet1
amidxtaped: time 0.000: > FSF=2
amidxtaped: time 0.000: > HEADER
amidxtaped: time 0.000: > DEVICE=file:/Backup/general/WeeklySet1
amidxtaped: time 0.000: > HOST=^snook$
amidxtaped: time 0.000: > DISK=^/Shared$
amidxtaped: time 0.000: > DATESTAMP=20030319
amidxtaped: time 0.000: > END
amidxtaped: time 0.001: amrestore_nargs=0
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /Backup/usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "file:/Backup/general/WeeklySet1"
argv[4] = "^snook$"
argv[5] = "^/Shared$"
argv[6] = "20030319"
amrestore:   0: skipping start of tape: date 20030319 label WeeklySet1
amrestore:   1: skipping snook._Mail.20030319.0
amrestore:   2: restoring snook._Shared.20030319.0
Error 32 (Broken pipe) offset -835747840+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amidxtaped: time 209.145: amrestore terminated normally with status: 2
amidxtaped: time 209.146: rewinding tape ...
amidxtaped: time 209.146: done
amidxtaped: time 209.146: pid 1552 finish time Wed Mar 19 10:56:07 2003

-

amrecover: debug 1 pid 1526 ruid 0 euid 0: start at Wed Mar 19 10:49:14 2003
amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10082
amrecover: stream_client_privileged: our side is 0.0.0.0.928
guess_disk: 11: "/tmp/amanda"
guess_disk: 0: 1: "/": "rootfs"
guess_disk: local_disk = 1, fsname = "rootfs"
guess_disk: 1: 1: "/": "/dev/root"
guess_disk: 1: 5: "/proc": "/proc"
guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs"
guess_disk: 1: 5: "/boot": "/dev/hda1"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 1: "/": "/dev/hda2"
guess_disk: 1: 5: "/proc": "none"
guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs"
guess_disk: 1: 5: "/boot": "/dev/hda1"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 1: "/": "LABEL=/"
guess_disk: 1: 5: "/boot": "LABEL=/boot"
guess_disk: 1: 8: "/dev/pts": "none"
guess_disk: 1: 5: "/proc": "none"
guess_disk: 1: 8: "/dev/shm": "none"
guess_disk: 1: 4: "swap": "/dev/hda3"
guess_disk: 1: 11: "/mnt/floppy": "/dev/fd0"
guess_disk: 1: 7: "/Backup": "/dev/hdb"
guess_disk: 1: 10: "/mnt/cdrom": "/dev/cdrom"
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/."
...
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/bao/"
add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/boot.out"
...
amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10083
amrecover: stream_client_privileged: our side is 0.0.0.0.620
amrecover: try_socksize: receive buffer size is 65536
Exec'ing /bin/gtar with arguments:
tar
-xpGvf
-
./bao/gsv42w32.exe
./bao/gs704w32.exe
./bao/WinPcap.exe
./bao/ipchains
./bao/imtool.c


Pleae tell me what's happened with amanda

[Fwd: Re: Problem with amrecover]

[Rainer Wiener]

--
skilldeal - Ihr Partner für IT-Projekte
Rainer Wiener
skilldeal AG
Gitschiner Str. 94
D-10969 Berlin
Tel: +49 (0) 30  61 6558 -65/ -60
Fax: +49 (0) 30  61 6558 -66
E-Mail: [EMAIL PROTECTED]
Internet: http://www.skilldeal.com
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose or take any action based on
this message or any information herein. If you have received this in
error, please advise the sender immediately by reply e-mail and delete
this message. Thank you for your cooperation.
--- Begin Message ---
Joshua Baker-LePain schrieb:
On Tue, 18 Mar 2003 at 4:17pm, Rainer Wiener wrote


	argv[0] = "amrestore"
	argv[1] = "-h"
	argv[2] = "-p"
	argv[3] = "/dev/nst0"
	argv[4] = "ha-node01.berlin.skilldeal.com"
	argv[5] = "^hda2$"
	argv[6] = "20030317"
	amrestore:   0: skipping start of tape: date 20030317 label 		 
SkillDealBackupFull01
	amrestore:   1: skipping 		 
ha-node02.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   2: skipping 		ha-node01.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   5: skipping 	amanda.`erlin.siilldeal.com.hda1.20030317.0
	amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
	amrestore:   7: skipping ha-node01.berlin.skilldeal.com.hda1.20030317.0
	amrestore: strange amanda header: "AMANDA: DILE 00030317 
ha-node01.berlin.skilleal.com hda6 lev 0 comp .gz program /bin/tar"
	amidxtaped: amrestore terminated normally with status: 0
	Rewinding tape: done
	amidxtaped: pid 31832 finish time Tue Mar 18 14:52:30 2003


So this looks like there was no backup of hda2 from ha-node01 on that 
tape.  Should there have been?
Yes, in the email from amanda stand:

ha-node01.be hda20  633280 228192  36.0 256:33  14.8   4:35 830.7



	argv[0] = "amrestore"
	argv[1] = "-h"
	argv[2] = "-p"
	argv[3] = "/dev/nst0"
	argv[4] = "ha-node01.berlin.skilldeal.com"
	argv[5] = "^hda1$"
	argv[6] = "20030317"
	amrestore:   0: skipping start of tape: date 20030317 label 		 
SkillDealBackupFull01
	amrestore:   1: skipping ha-node02.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   2: skipping ha-node01.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   5: skipping amanda.`erlin.siilldeal.com.hda1.20030317.0
	amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
	amrestore:   7: restoring ha-node01.berlin.skilldeal.com.hda1.20030317.0
	 incomplete distance tree

gzip: stdin: invalid compressed data--format violated
Error 32 (Broken pipe) offset 131072+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amrestore: skipping ahead to start of next file, please wait...
amidxtaped: amrestore terminated normally with status: 2
Rewinding tape: done
amidxtaped: pid 31876 finish time Tue Mar 18 15:12:39 2003


And that looks like either a corrupted file on tape, a bad gzip, or 
hardware problems.

What Linux distro are you running, and what version of tar is there?  If 
there's a 2.2.17 kernel laying around, it's gotta' be old...
I use Debian 3.0 (woody)

Linux amanda 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i586 unknown
tar (GNU tar) 1.13.25
Is the kernel to old?

cu
Rainer
--
skilldeal - Ihr Partner für IT-Projekte
Rainer Wiener
skilldeal AG
Gitschiner Str. 94
D-10969 Berlin
Tel: +49 (0) 30  61 6558 -65/ -60
Fax: +49 (0) 30  61 6558 -66
E-Mail: [EMAIL PROTECTED]
Internet: http://www.skilldeal.com
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose or take any action based on
this message or any information herein. If you have received this in
error, please advise the sender immediately by reply e-mail and delete
this message. Thank you for your cooperation.
--- End Message ---

Re: Problem with amrecover

[Jean-Louis Martineau]

On Tue, Mar 18, 2003 at 04:17:54PM +0100, Rainer Wiener wrote:
>   ha-node01.berlin.skilldeal.com.hda1.20030317.0
>   amrestore: strange amanda header: "AMANDA: DILE 00030317 

It should be: AMANDA: FILE 00030317 ...
  ^

I suspect a memory error on your tape server.

Jean-Louis
-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834

Re: Problem with amrecover

[Joshua Baker-LePain]

On Tue, 18 Mar 2003 at 4:17pm, Rainer Wiener wrote

>   argv[0] = "amrestore"
>   argv[1] = "-h"
>   argv[2] = "-p"
>   argv[3] = "/dev/nst0"
>   argv[4] = "ha-node01.berlin.skilldeal.com"
>   argv[5] = "^hda2$"
>   argv[6] = "20030317"
>   amrestore:   0: skipping start of tape: date 20030317 label  
> SkillDealBackupFull01
>   amrestore:   1: skipping 
> ha-node02.berlin.skilldeal.com.nb1.20030317.0
>   amrestore:   2: skipping
> ha-node01.berlin.skilldeal.com.nb1.20030317.0
>   amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
>   amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
>   amrestore:   5: skippingamanda.`erlin.siilldeal.com.hda1.20030317.0
>   amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
>   amrestore:   7: skipping ha-node01.berlin.skilldeal.com.hda1.20030317.0
>   amrestore: strange amanda header: "AMANDA: DILE 00030317 
> ha-node01.berlin.skilleal.com hda6 lev 0 comp .gz program /bin/tar"
>   amidxtaped: amrestore terminated normally with status: 0
>   Rewinding tape: done
>   amidxtaped: pid 31832 finish time Tue Mar 18 14:52:30 2003

So this looks like there was no backup of hda2 from ha-node01 on that 
tape.  Should there have been?

>   argv[0] = "amrestore"
>   argv[1] = "-h"
>   argv[2] = "-p"
>   argv[3] = "/dev/nst0"
>   argv[4] = "ha-node01.berlin.skilldeal.com"
>   argv[5] = "^hda1$"
>   argv[6] = "20030317"
>   amrestore:   0: skipping start of tape: date 20030317 label  
> SkillDealBackupFull01
>   amrestore:   1: skipping ha-node02.berlin.skilldeal.com.nb1.20030317.0
>   amrestore:   2: skipping ha-node01.berlin.skilldeal.com.nb1.20030317.0
>   amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
>   amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
>   amrestore:   5: skipping amanda.`erlin.siilldeal.com.hda1.20030317.0
>   amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
>   amrestore:   7: restoring ha-node01.berlin.skilldeal.com.hda1.20030317.0
>incomplete distance tree
> 
>   gzip: stdin: invalid compressed data--format violated
>   Error 32 (Broken pipe) offset 131072+32768, wrote 0
>   amrestore: pipe reader has quit in middle of file.
>   amrestore: skipping ahead to start of next file, please wait...
>   amidxtaped: amrestore terminated normally with status: 2
>   Rewinding tape: done
>   amidxtaped: pid 31876 finish time Tue Mar 18 15:12:39 2003

And that looks like either a corrupted file on tape, a bad gzip, or 
hardware problems.

What Linux distro are you running, and what version of tar is there?  If 
there's a 2.2.17 kernel laying around, it's gotta' be old...

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Problem with amrecover

[Rainer Wiener]

Hi,

I try to recover files from a backup that I made a few minutes ago. Now 
I get this error:

Load tape SkillDealBackupFull01 now
Continue? [Y/n]: y
EOF, check amidxtaped.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n]: y
In the amidxtaped.debug stand:

	amidxtaped: debug 1 pid 31832 ruid 34 euid 34 start time Tue Mar 	18 
14:51:46 2003
	amidxtaped: version 2.4.2p2
	> SECURITY USER root
	bsd security: remote host localhost user root local user backup
	amandahosts security check passed
	> 6
	amrestore_nargs=6
	> -h
	> -p
	> /dev/nst0
	> ha-node01.berlin.skilldeal.com
	> ^hda2$
	> 20030317
	Ready to execv amrestore with:
	path = /usr/sbin/amrestore
	argv[0] = "amrestore"
	argv[1] = "-h"
	argv[2] = "-p"
	argv[3] = "/dev/nst0"
	argv[4] = "ha-node01.berlin.skilldeal.com"
	argv[5] = "^hda2$"
	argv[6] = "20030317"
	amrestore:   0: skipping start of tape: date 20030317 label 		 
SkillDealBackupFull01
	amrestore:   1: skipping 		 
ha-node02.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   2: skipping 		ha-node01.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   5: skipping 	amanda.`erlin.siilldeal.com.hda1.20030317.0
	amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
	amrestore:   7: skipping ha-node01.berlin.skilldeal.com.hda1.20030317.0
	amrestore: strange amanda header: "AMANDA: DILE 00030317 
ha-node01.berlin.skilleal.com hda6 lev 0 comp .gz program /bin/tar"
	amidxtaped: amrestore terminated normally with status: 0
	Rewinding tape: done
	amidxtaped: pid 31832 finish time Tue Mar 18 14:52:30 2003

If I try an other file I got this:

	The following tapes are needed: SkillDealBackupFull01

Restoring files into directory /root/test
Continue? [Y/n]: y
Load tape SkillDealBackupFull01 now
Continue? [Y/n]: y
tar: Skipping to next header
tar: ./vmlinuz-2.2.17: Not found in archive
tar: Error exit delayed from previous errors
extract_list - child returned non-zero status: 2
Continue? [Y/n]: n
amrecover> quit
200 Good bye.
amanda:~/test# logout
Connection to amanda closed.
In the amidxtaped.debug stand:

	amidxtaped: pid 31832 finish time Tue Mar 18 14:52:30 2003
	amanda:/tmp/amanda# less amidxtaped.20030318151159.debug
	amidxtaped: debug 1 pid 31876 ruid 34 euid 34 start time Tue Mar 	18 
15:11:59 2003
	amidxtaped: version 2.4.2p2
	> SECURITY USER root
	bsd security: remote host localhost user root local user backup
	amandahosts security check passed
	> 6
	amrestore_nargs=6
	> -h
	> -p
	> /dev/nst0
	> ha-node01.berlin.skilldeal.com
	> ^hda1$
	> 20030317
	Ready to execv amrestore with:
	path = /usr/sbin/amrestore
	argv[0] = "amrestore"
	argv[1] = "-h"
	argv[2] = "-p"
	argv[3] = "/dev/nst0"
	argv[4] = "ha-node01.berlin.skilldeal.com"
	argv[5] = "^hda1$"
	argv[6] = "20030317"
	amrestore:   0: skipping start of tape: date 20030317 label 		 
SkillDealBackupFull01
	amrestore:   1: skipping ha-node02.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   2: skipping ha-node01.berlin.skilldeal.com.nb1.20030317.0
	amrestore:   3: skipping ha-node01.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   4: skipping ha-node02.berlin.skilldeal.com.nb0.20030317.0
	amrestore:   5: skipping amanda.`erlin.siilldeal.com.hda1.20030317.0
	amrestore:   6: skipping ha-node02.berlin.skilldeal.com.hda1.20030317.0
	amrestore:   7: restoring ha-node01.berlin.skilldeal.com.hda1.20030317.0
	 incomplete distance tree

gzip: stdin: invalid compressed data--format violated
Error 32 (Broken pipe) offset 131072+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amrestore: skipping ahead to start of next file, please wait...
amidxtaped: amrestore terminated normally with status: 2
Rewinding tape: done
amidxtaped: pid 31876 finish time Tue Mar 18 15:12:39 2003
Thanks for all information.

cu
Rainer
--
skilldeal - Ihr Partner für IT-Projekte
Rainer Wiener
skilldeal AG
Gitschiner Str. 94
D-10969 Berlin
Tel: +49 (0) 30  61 6558 -65/ -60
Fax: +49 (0) 30  61 6558 -66
E-Mail: [EMAIL PROTECTED]
Internet: http://www.skilldeal.com

Re: problem with amrecover

[Stephen D. Lane]

I'm guessing here, but it looks like the file name doesn't have a leading
slash in the archive, so you shouldn't put one in your 'add' command.  Try

> amrecover> add lib
 ^ no slash here

and see what happens.

Good luck!


--Steve Lane   /"\
  Doudna Lab   \ /  ASCII Ribbon Campaign
  U. C. BerkeleyX Against HTML Email
   / \



On Tue, Mar 11, 2003 at 06:33:04PM +0100, liam pace wrote:
> Hi,
> 
> when I try to recover files with am recover, I get a strange messages saying
> that the directory / file I'm trying to restore is not in archive..
---cut---
> the error I get is:
> 
> amrecover> ls
> 2003-03-11 .
> 2003-03-11 .autofsck
> 2003-03-11 bin/
> 2003-03-11 boot/
> 2003-03-11 bru/
> 2003-03-11 dev/
> 2003-03-11 etc/
> 2003-03-11 home/
> 2003-03-11 initrd/
> 2003-03-11 lib/
> 2003-03-11 lost+found/
> 2003-03-11 misc/
> 2003-03-11 mnt/
> 2003-03-11 opt/
> 2003-03-11 proc/
> 2003-03-11 root/
> 2003-03-11 sbin/
> 2003-03-11 tmp/
> 2003-03-11 usr/
> 2003-03-11 var/
> 2003-03-11 www/
> amrecover> add /lib
> File /lib doesn't exist in directory

problem with amrecover

[liam pace]

Hi,

when I try to recover files with am recover, I get a strange messages saying
that the directory / file I'm trying to restore is not in archive..


---
I'm using the following dump type in amanda.conf:

define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority high
index
compress none
dumpcycle 0
}

I manage to see the index file in
/usr/local/etc/amanda/Daily2/index/hostnameXXX




the command I issue is

amrecover Daily2




the error I get is:

amrecover> ls
2003-03-11 .
2003-03-11 .autofsck
2003-03-11 bin/
2003-03-11 boot/
2003-03-11 bru/
2003-03-11 dev/
2003-03-11 etc/
2003-03-11 home/
2003-03-11 initrd/
2003-03-11 lib/
2003-03-11 lost+found/
2003-03-11 misc/
2003-03-11 mnt/
2003-03-11 opt/
2003-03-11 proc/
2003-03-11 root/
2003-03-11 sbin/
2003-03-11 tmp/
2003-03-11 usr/
2003-03-11 var/
2003-03-11 www/
amrecover> add /lib
File /lib doesn't exist in directory
amrecover> add lib/
Added dir /lib at date 2003-03-11
amrecover> extract

Extracting files using tape drive /dev/rmt/1n on host amanda.
The following tapes are needed: DLY2_E

Restoring files into directory /usr/local/etc/amanda/Daily2
Continue [?/Y/n]? y

Extracting files using tape drive /dev/rmt/1n on host amanda.
Load tape DLY2_E now
Continue [?/Y/n/t]? y
tar: ./lib: Not found in archive
tar: Error exit delayed from previous errors
extract_list - child returned non-zero status: 2
Continue [?/Y/n]? y
amrecover> quit




can anyone help please???

regards,

liam pace

Re: Problem with amrecover

[Joshua Baker-LePain]

On Thu, 19 Dec 2002 at 11:08am, John Oliver wrote

> On Thu, Dec 19, 2002 at 02:06:27PM -0500, Joshua Baker-LePain wrote:
> > Since you must run amrecover as root, .amandahosts needs an entry for that 
> > as well as the entry for amanda for amdumps.  You can leave them both in 
> > there, so no need to edit the file every time.
> 
> So I can:
> 
> localhost root
> localhost amanda
> backup root
> backup amanda
> backup.indyme.local root
> backup.indyme.local amanda

Yep.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Problem with amrecover

[Ben Simpson]

You have to do everthing as the amanda user.   But If you want to 
restore something you have to be root.  So you have to have access to 
the client as root.


Ben

John Oliver wrote:

On Wed, Dec 18, 2002 at 07:39:48PM -0600, C. Bensend wrote:
 

Hey John,

	Notice that the error message didn't say:

[access as amanda not allowed from root@backup]

or

[access as amanda not allowed from [EMAIL PROTECTED]] ?

	I'd put my bet on you needing a line for localhost in your
.amandahosts file as well.
   


That's it!  Thanks! :-)

I find myself wondering, though... am I going to have to edit this file
every time I want to back up and restore?  The docs say to have the
amanda username in ./amadahosts, not root.  What's the story there?

 


--
Ben Simpson, MCSE
Systems Engineer
Voice and Fax Number: 1-877-718-7627 x401

Silex Technologies
http://www.silextech.com

Re: Problem with amrecover

[John Oliver]

On Thu, Dec 19, 2002 at 02:06:27PM -0500, Joshua Baker-LePain wrote:
> Since you must run amrecover as root, .amandahosts needs an entry for that 
> as well as the entry for amanda for amdumps.  You can leave them both in 
> there, so no need to edit the file every time.

So I can:

localhost root
localhost amanda
backup root
backup amanda
backup.indyme.local root
backup.indyme.local amanda

Or would it be more like:

localhost amanda root

?

-- 
John Oliver, CCNAhttp://www.john-oliver.net/
Linux/UNIX/network consulting http://www.john-oliver.net/resume/
***   sendmail, Apache, ftp, DNS, spam filtering ***
Colocation, T1s, web/email/ftp hosting  

Re: Problem with amrecover

[Joshua Baker-LePain]

On Thu, 19 Dec 2002 at 10:27am, John Oliver wrote

> On Wed, Dec 18, 2002 at 07:39:48PM -0600, C. Bensend wrote:
> > Hey John,
> > 
> > Notice that the error message didn't say:
> > 
> > [access as amanda not allowed from root@backup]
> > 
> > or
> > 
> > [access as amanda not allowed from [EMAIL PROTECTED]] ?
> > 
> > I'd put my bet on you needing a line for localhost in your
> > .amandahosts file as well.
> 
> That's it!  Thanks! :-)
> 
> I find myself wondering, though... am I going to have to edit this file
> every time I want to back up and restore?  The docs say to have the
> amanda username in ./amadahosts, not root.  What's the story there?

Since you must run amrecover as root, .amandahosts needs an entry for that 
as well as the entry for amanda for amdumps.  You can leave them both in 
there, so no need to edit the file every time.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Problem with amrecover

[John Oliver]

On Wed, Dec 18, 2002 at 07:39:48PM -0600, C. Bensend wrote:
> Hey John,
> 
>   Notice that the error message didn't say:
> 
> [access as amanda not allowed from root@backup]
> 
> or
> 
> [access as amanda not allowed from [EMAIL PROTECTED]] ?
> 
>   I'd put my bet on you needing a line for localhost in your
> .amandahosts file as well.

That's it!  Thanks! :-)

I find myself wondering, though... am I going to have to edit this file
every time I want to back up and restore?  The docs say to have the
amanda username in ./amadahosts, not root.  What's the story there?

-- 
John Oliver, CCNAhttp://www.john-oliver.net/
Linux/UNIX/network consulting http://www.john-oliver.net/resume/
***   sendmail, Apache, ftp, DNS, spam filtering ***
Colocation, T1s, web/email/ftp hosting  

Re: Problem with amrecover

[C. Bensend]

On Wed, Dec 18, 2002 at 04:49:28PM -0800, John Oliver wrote:
> [root@backup DailySet1]# amrecover
> AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
> 220 backup AMANDA index server (2.4.2p2) ready.
> 500 Access not allowed: [access as amanda not allowed from
> root@localhost] amandahostsauth failed
> 
> [root@backup DailySet1]# uname -a
> Linux backup.indyme.local 2.4.18-14 #1 Wed Sep 4 12:13:11 EDT 2002 i686
> athlon i386 GNU/Linux
> [root@backup DailySet1]# cat /var/lib/amanda/.amandahosts
> backup root
> backup.indyme.local root

Hey John,

Notice that the error message didn't say:

[access as amanda not allowed from root@backup]

or

[access as amanda not allowed from [EMAIL PROTECTED]] ?

I'd put my bet on you needing a line for localhost in your
.amandahosts file as well.

HTH!

Benny


~~
"Discharge of a nuclear weapon shall be deemed a warlike act,
even if accidental."   -- My homeowners insurance policy

Problem with amrecover

[John Oliver]

[root@backup DailySet1]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 backup AMANDA index server (2.4.2p2) ready.
500 Access not allowed: [access as amanda not allowed from
root@localhost] amandahostsauth failed

[root@backup DailySet1]# uname -a
Linux backup.indyme.local 2.4.18-14 #1 Wed Sep 4 12:13:11 EDT 2002 i686
athlon i386 GNU/Linux
[root@backup DailySet1]# cat /var/lib/amanda/.amandahosts
backup root
backup.indyme.local root

What's the beef?

-- 
John Oliver, CCNAhttp://www.john-oliver.net/
Linux/UNIX/network consulting http://www.john-oliver.net/resume/
***   sendmail, Apache, ftp, DNS, spam filtering ***
Colocation, T1s, web/email/ftp hosting  

Re: Problem with amrecover + chg-scsi

[Patrick J. LoPresti]

"Patrick J. LoPresti" <[EMAIL PROTECTED]> writes:

> The problem here is pretty obvious: amidxtaped is using the tapedev of
> "0" as the tape device, instead of the true device specified in the
> changerfile as chg-scsi expects.

I found a solution: The "-d" option to amrecover lets me override
tapedev.  This is a little clunky, perhaps, but better than running
amrestore by hand.

I guess I should try more stuff before bothering the mailing list.  My
apologies for the noise.

 - Pat

Problem with amrecover + chg-scsi

[Patrick J. LoPresti]

I am using Amanda 2.4.2p2 with a 96 slot, 4 drive tape library (Sun
StorEdge L3500).  My operating system is Red Hat Linux 7.2, although I
doubt it matters.

In the documentation file TAPE.CHANGERS, I read this section:

Now there is another way, to get the chg-scsi a little bit more
flexible.  If you use only one digit in the `tapedev' parameter,
the chg-scsi expects that changerfile points to a real
configuration file, not only a counting file.

[etc.]

This sounded like exactly what I want, so I am using it.  That is, in
my various amanda.conf files, I have lines like these:

tpchanger "chg-scsi"
tapedev "1"
changerfile "/etc/amanda/chg-scsi.conf"

...and then the real configuration for the tape device appears in some
section of /etc/amanda/chg-scsi.conf.  (The particular feature I like
is limiting Amanda to using only certain slots for a configuration.  I
would not want Amanda to scan all 96 slots looking for something.)

This works great for doing backups.  But today I decided to test a
restoral using amrecover.  This failed at "extract", with the
following lines at the tail of the amidxtaped.debug file:

Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "0"
argv[4] = "kingtut"
argv[5] = "^/dev/sda1$"
argv[6] = "20020415"
amrestore: could not open tape 0: No such file or directory
amidxtaped: amrestore terminated normally with status: 2
amidxtaped: could not stat 0
could not stat 0
amidxtaped: pid 2220 finish time Tue Apr 23 14:44:58 2002

The problem here is pretty obvious: amidxtaped is using the tapedev of
"0" as the tape device, instead of the true device specified in the
changerfile as chg-scsi expects.

I am curious whether other people have seen this problem, and if
anyone can suggest a solution.

Thanks!

 - Pat

Re: eof problem with amrecover

[John R. Jackson]

>I keep getting the following error when I try to recover a file with 
>amrecover:
>...
>tar: Unexpected EOF on archive file
>...
>amrestore:   0: skipping start of tape: date 20010315 label WeeklySet112
>amrestore:   1: skipping beauty._etc.20010315.0
>amrestore:   2: restoring beauty._var_spool_mail.20010315.0
>amrestore: read error: Input/output error

So what's your question?  You got a tape read error.  That's life.

You can try all the usual things:

  * Clean the drive.

  * Retension the tape.

  * Try a different drive.

  * Check the cables, connectors, boards, etc.

>Bill Campbell

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

eof problem with amrecover

[Bill Campbell]

I keep getting the following error when I try to recover a file with 
amrecover:


 tcsh> /usr/local/sbin/amrecover -C WeeklySet1 -d /dev/nst1 -s redbaron.physics.s
c.edu
AMRECOVER Version 2.4.2p1. Contacting server on redbaron.physics.sc.edu ...
220 redbaron AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore date to today (2001-03-16)
200 Working date set to 2001-03-16.
200 Config set to WeeklySet1.
501 No index records for host: beauty.psc.sc.edu. Invalid?
Trying beauty.psc.sc.edu ...
501 No index records for host: beauty.psc.sc.edu. Invalid?
Trying beauty ...
200 Dump host set to beauty.
Can't determine disk and mount point from $CWD
amrecover> setdisk /var/spool/mail
Warning: no log files found for tape WeeklySet111 written0-00-00
Warning: could not open holding dir /jekyl17/amanda: No such file or directory
200 Disk set to /var/spool/mail.
amrecover> ls
2001-03-15 .
2001-03-15 adamt
2001-03-15 amanda
2001-03-15 copty
2001-03-15 kothari
2001-03-15 nussinov
2001-03-15 singh
2001-03-15 sudheer
2001-03-15 yumiceva
amrecover> add adamt
Added /adamt
amrecover> settape redbaron.physics.sc.edu:/dev/nst1
Using tape /dev/nst1 from server redbaron.physics.sc.edu.
amrecover> extract
 
Extracting files using tape drive /dev/nst1 on host redbaron.physics.sc.edu.
The following tapes are needed: WeeklySet112
 
Restoring files into directory /tmp/amanda
Continue? [Y/n]: Y
 
Load tape WeeklySet112 now
Continue? [Y/n]: Y
./adamt
tar: Unexpected EOF on archive file
extract_list - child returned non-zero status: 3
Continue? [Y/n]: Y
amrecover>
--

The amidxtape.debug file is

--
amidxtaped: debug 1 pid 5970 ruid 422 euid 422 start time Fri Mar 16 11:32:12 20
01
amidxtaped: version 2.4.2
> SECURITY USER root
bsd security: remote host beauty.psc.sc.edu user root local user amanda
amandahosts security check passed
> 6
amrestore_nargs=6
> -p
> /dev/nst1
> beauty
> ^/var/spool/mail$
> 20010315
Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/dev/nst1"
argv[4] = "beauty"
argv[5] = "^/var/spool/mail$"
argv[6] = "20010315"
amrestore:   0: skipping start of tape: date 20010315 label WeeklySet112
amrestore:   1: skipping beauty._etc.20010315.0
amrestore:   2: restoring beauty._var_spool_mail.20010315.0
amrestore: read error: Input/output error
amidxtaped: amrestore terminated normally with status: 2
Rewinding tape: done
amidxtaped: pid 5970 finish time Fri Mar 16 11:33:44 2001
---

and the amindexd.debug file is

---
amindexd: debug 1 pid 5966 ruid 422 euid 422 start time Fri Mar 16 11:31:04 2001
amindexd: version 2.4.2
< 220 redbaron AMANDA index server (2.4.2) ready.
> SECURITY USER root
bsd security: remote host beauty.psc.sc.edu user root local user amanda
amandahosts security check passed
< 200 Access OK
> DATE 2001-03-16
< 200 Working date set to 2001-03-16.
> SCNF WeeklySet1
< 200 Config set to WeeklySet1.
> HOST beauty.psc.sc.edu
< 501 No index records for host: beauty.psc.sc.edu. Invalid?
> HOST beauty.psc.sc.edu
< 501 No index records for host: beauty.psc.sc.edu. Invalid?
> HOST beauty
< 200 Dump host set to beauty.
> DISK /
< 501 No index records for disk: /. Invalid?
> DISK root_domain#root
< 501 No index records for disk: root_domain#root. Invalid?
> DISK /var/spool/mail
- 2001-03-15 0 WeeklySet112 2
- 2001-02-23 0 WeeklySet110 2
- 2001-02-20 0 WeeklySet109 2
< 200 Disk set to /var/spool/mail.
Uncompress command: /bin/gzip -dc 
'/usr/adm/amanda/index/beauty/_var_spool_mail/20010315_0.gz' 2>/dev/null | sort > 
'/usr/adm/amanda/index/beauty/_var_spool_mail/20010315_0'
f /usr/adm/amanda/index/beauty/_var_spool_mail/20010315_0
< 200 "/" is a valid directory
> OISD /
f /usr/adm/amanda/index/beauty/_var_spool_mail/20010315_0
< 200 "/" is a valid directory
> OLSD /
< 200- Opaque list of /
< 201- 2001-03-15 0 WeeklySet112 /
< 201- 2001-03-15 0 WeeklySet112 /adamt
< 201- 2001-03-15 0 WeeklySet112 /amanda
< 201- 2001-03-15 0 WeeklySet112 /copty
< 201- 2001-03-15 0 WeeklySet112 /kothari
< 201- 2001-03-15 0 WeeklySet112 /nussinov
< 201- 2001-03-15 0 WeeklySet112 /root
< 201- 2001-03-15 0 WeeklySet112 /singh
< 201- 2001-03-15 0 WeeklySet112 /sudheer
< 201- 2001-03-15 0 WeeklySet112 /yumiceva
< 200  Opaque list of / 
---

We have had a problem with ffs not working so we compiled with the broken ffs option 
but are still getting the same error message.  Any ideas?

Bill Campbell
email:  [EMAIL PROTECTED]
homepage:  http://hep.physics.sc.edu/~billc/