Re: amrecover error: user root from localhost is not allowed to execute the service amindexd:
On 08/15/2014 02:32 AM, Allen Liu wrote:
Settings:
[root@lc2 amanda]# cat /var/lib/amanda/.amandahosts
lc1 root
localhost root
lc2 root
lc2 amandabackup
lc2 root amindexd amidxtaped
localhost root amindexd amidxtaped
localhost.localdomain root amindexd amidxtaped
Amanda stop reading after the first line that match the hostname and user.
It stop after 'lc2 root'
in 'man amanda-auth', you can read that a line without services do
include the amindexd and amidxtaped services.
The attached patch allow amanda to read the next line.
Jean-Louis
diff --git a/common-src/security-util.c b/common-src/security-util.c
index a82b366..360eb91 100644
--- a/common-src/security-util.c
+++ b/common-src/security-util.c
@@ -2303,7 +2303,7 @@ check_user_amandahosts(
}
else {
amfree(line);
- break;
+ continue;
}
}
Re: amrecover error: user root from localhost is not allowed to execute the service amindexd:
Well, first thing I usually see recommended is to try the actual fully qualified domain name (FQDN) rather than “localhost”. You might try that while waiting for other replies (and perhaps an explanation of why “localhost” isn’t great). Deb Baddorf Fermilab On Aug 15, 2014, at 1:32 AM, Allen Liu allenliu2...@gmail.com wrote: Hi experts, I installed following amanda pkgs on a Fedora 20. Want to use it as both server and client. Related files are included below. I can run backup (amdump) without problems. But amrecover failed.I tried both localhost and hostname (lc2). Same error. It kept telling me to add localhost root amindexd amidxtaped to /var/lib/amanda/.amandahosts on the server. Actually I have already added it. I also checked the log files, can't find any useful info. Anyone has any clue ? Did I miss anything ? Error msg: [root@lc2 amanda]# amrecover -s localhost -t localhost -C MySet4 AMRECOVER Version 3.3.3. Contacting server on localhost ... NAK: user root from localhost is not allowed to execute the service amindexd: Please add the line localhost root amindexd amidxtaped to /var/lib/amanda/.amandahosts on the server [root@lc2 amanda]# amrecover -s lc2 -t lc2 -C MySet4 AMRECOVER Version 3.3.3. Contacting server on lc2 ... NAK: user root from lc2 is not allowed to execute the service amindexd: Please add the line lc2 root amindexd amidxtaped to /var/lib/amanda/.amandahosts on the server Settings: [root@lc2 amanda]# cat /var/lib/amanda/.amandahosts lc1 root localhost root lc2 root lc2 amandabackup lc2 root amindexd amidxtaped localhost root amindexd amidxtaped localhost.localdomain root amindexd amidxtaped [root@lc2 amanda]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.6.9lc2 192.168.6.8lc1 [root@lc2 amanda]# rpm -qa|grep amanda amanda-client-3.3.3-10.fc20.x86_64 amanda-libs-3.3.3-10.fc20.x86_64 amanda-server-3.3.3-10.fc20.x86_64 amanda-3.3.3-10.fc20.x86_64 Thanks, -Allen Liu
Re: amrecover error
On Tue, 14 Feb 2012, Jean-Louis Martineau wrote: On 02/14/2012 05:51 PM, lxnf9...@gmail.com wrote: If I run it without setting the diskfile # amrecover -C msl6000 AMRECOVER Version 3.2.3. Contacting server on amanda2 ... 220 amanda2 AMANDA index server (3.2.3) ready. Setting restore date to today (2012-02-14) 200 Working date set to 2012-02-14. 501 Could not read disk file (null)! amrecover listhost 200- List hosts for config msl6000 200 No hosts for config msl6000 Add a diskfilke in the amanda.conf, it can be an empty file. I added a empty disklist file in /etc/amanda/msl6000 and that worked A bit strange to my simple mind Thanks Richard
Re: amrecover error
On 02/15/2012 09:05 AM, lxnf9...@gmail.com wrote: I added a empty disklist file in /etc/amanda/msl6000 and that worked A bit strange to my simple mind amrecover and amfetchdump do not require the dle to be in the diskfile, but a diskfile is required. Jean-Louis
Re: amrecover error
On 02/14/2012 05:17 PM, lxnf9...@gmail.com wrote: I have different diskfiles I run different days of the week /usr/sbin/amdump -o diskfile=disklist_weekly msl6000 /usr/sbin/amdump -o diskfile=disklist_daily msl6000 This works just fine But amrecover is different matter # amrecover -C msl6000 AMRECOVER Version 3.2.3. Contacting server on amanda2 ... 220 amanda2 AMANDA index server (3.2.3) ready. Setting restore date to today (2012-02-14) 200 Working date set to 2012-02-14. 501 Could not read disk file (null)! # amrecover -o diskfile=disklist_weekly -C msl6000 parse error: unknown parameter 'diskfile' amrecover: errors processing config file amrecover is a client application, setting the diskfile on the client would be useless. What am I doing wrong What's the problem if you do not set the diskfile? Jean-Louis
Re: amrecover error
On Tue, 14 Feb 2012, Jean-Louis Martineau wrote: On 02/14/2012 05:17 PM, lxnf9...@gmail.com wrote: I have different diskfiles I run different days of the week /usr/sbin/amdump -o diskfile=disklist_weekly msl6000 /usr/sbin/amdump -o diskfile=disklist_daily msl6000 This works just fine But amrecover is different matter # amrecover -C msl6000 AMRECOVER Version 3.2.3. Contacting server on amanda2 ... 220 amanda2 AMANDA index server (3.2.3) ready. Setting restore date to today (2012-02-14) 200 Working date set to 2012-02-14. 501 Could not read disk file (null)! # amrecover -o diskfile=disklist_weekly -C msl6000 parse error: unknown parameter 'diskfile' amrecover: errors processing config file amrecover is a client application, setting the diskfile on the client would be useless. What am I doing wrong What's the problem if you do not set the diskfile? Jean-Louis If I run it without setting the diskfile # amrecover -C msl6000 AMRECOVER Version 3.2.3. Contacting server on amanda2 ... 220 amanda2 AMANDA index server (3.2.3) ready. Setting restore date to today (2012-02-14) 200 Working date set to 2012-02-14. 501 Could not read disk file (null)! amrecover listhost 200- List hosts for config msl6000 200 No hosts for config msl6000 Richard
Re: amrecover error
On 02/14/2012 05:51 PM, lxnf9...@gmail.com wrote: If I run it without setting the diskfile # amrecover -C msl6000 AMRECOVER Version 3.2.3. Contacting server on amanda2 ... 220 amanda2 AMANDA index server (3.2.3) ready. Setting restore date to today (2012-02-14) 200 Working date set to 2012-02-14. 501 Could not read disk file (null)! amrecover listhost 200- List hosts for config msl6000 200 No hosts for config msl6000 Add a diskfilke in the amanda.conf, it can be an empty file. Jean-louis
RE: Amrecover error
Hi Looks a firewall of networking issue. What happenes if you do this on server? Any other clients it works on? And a look in the amanda log files for clues - normally /tmp/amanda. -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of aminukapon Sent: 24 July 2008 05:05 To: amanda-users@amanda.org Subject: Amrecover error Hello all, I need help with this problem: I tried running amrecover on the client and get the following errors [EMAIL PROTECTED]: amrecover DailySet1 AMRECOVER Version 2.5.2p1. Contacting server on fubini ... [request failed: timeout waiting for ACK] My amanda.conf looks like this # # amanda.conf - sample Amanda configuration file. # # If your configuration is called, say, DailySet1, then this file # normally goes in /etc/amanda/DailySet1/amanda.conf. # # You need to edit this file to suit your needs. See the documentation in # this file, in the man amanda man page, in the /usr/share/docs/amanda* # directories, and on the web at www.amanda.org for more information. # org Glasslab # your organization name for reports mailto [EMAIL PROTECTED] # space separated list of operators at your site dumpuser backup # the user to run dumps under inparallel 4 # maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h dumporder sssS # specify the priority order of each dumper # s - smallest size # S - biggest size # t - smallest time # T - biggest time # b - smallest bandwitdh # B - biggest bandwitdh # try BTBTBTBTBTBT if you are not holding # disk constrained taperalgo first # The algorithm used to choose which dump image to send # to the taper. # Possible values: # [first|firstfit|largest|largestfit|smallest|last] # Default: first. # first First in - first out. # firstfit The first dump image that will fit on # the current tape. # largest The largest dump image. # largestfit The largest dump image that will fit on # the current tape. # smallest The smallest dump image. # last Last in - first out. displayunit k # Possible values: k|m|g|t # Default: k. # The unit used to print many numbers. # k=kilo, m=mega, g=giga, t=tera netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2 bumppercent 20 # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300 # number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be used in a single run of amdump tpchanger chg-disk # the tape-changer glue script tapedev file:/backups/DailySet1/slots # the no-rewind tape device to be used rawtapedev @DEFAULT_RAW_TAPE_DEVICE@ #
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover Error 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed
Hi I had a look at # less amrecover.20050516105131.debug amrecover: debug 1 pid 25626 ruid 0 euid 0: start at Mon May 16 10:51:31 2005 amrecover: stream_client_privileged: connected to 192.168.1.55.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.829 amrecover.20050516105131.debug lines 1-3/3 (END) Also # less amindexd.20050516105131.debug amindexd: debug 1 pid 25627 ruid 1014 euid 1014: start at Mon May 16 10:51:31 2005 amindexd: version 2.4.4p4 amindexd: time 0.000: 220 server AMANDA index server (2.4.4p4) ready. amindexd: time 0.000: SECURITY USER root amindexd: time 0.001: bsd security: remote host server.domain.co.uk user root local user amanda amindexd: time 0.001: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 200 Good bye. amindexd: time 0.001: pid 25627 finish time Mon May 16 10:51:31 2005 I am running as root My ~amanda /.amandahost file is as follows server.domain.co.uk amanda server.domain.co.uk root /etc/hosts file 192.168.X.XX server.domain.co.uk server On Mon, 2005-05-16 at 08:25 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: amrecover Error 500 Access not allowed: [access as amanda notallowed from [EMAIL PROTECTED] amandahostsauth failed
Chuck, You need both client and server machines listed in the .amandahosts file on the server. Currently you've only got the one server listed there. talk to you soon mate Matt on 16/05/2005 16:09 Chuck Amadi said the following: Hi I had a look at # less amrecover.20050516105131.debug amrecover: debug 1 pid 25626 ruid 0 euid 0: start at Mon May 16 10:51:31 2005 amrecover: stream_client_privileged: connected to 192.168.1.55.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.829 amrecover.20050516105131.debug lines 1-3/3 (END) Also # less amindexd.20050516105131.debug amindexd: debug 1 pid 25627 ruid 1014 euid 1014: start at Mon May 16 10:51:31 2005 amindexd: version 2.4.4p4 amindexd: time 0.000: 220 server AMANDA index server (2.4.4p4) ready. amindexd: time 0.000: SECURITY USER root amindexd: time 0.001: bsd security: remote host server.domain.co.uk user root local user amanda amindexd: time 0.001: check failed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed amindexd: time 0.001: 200 Good bye. amindexd: time 0.001: pid 25627 finish time Mon May 16 10:51:31 2005 I am running as root My ~amanda /.amandahost file is as follows server.domain.co.uk amanda server.domain.co.uk root /etc/hosts file 192.168.X.XX server.domain.co.uk server On Mon, 2005-05-16 at 08:25 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 11:31am, Chuck Amadi wrote On Mon, 2005-05-16 at 06:15 -0400, Joshua Baker-LePain wrote: On Mon, 16 May 2005 at 10:38am, Chuck Amadi wrote server:/local/sw/amanda/bckup # /local/sw/amanda/bckup/sbin/amrecover -C DailySet1 -t server -s server AMRECOVER Version 2.4.4p4. Contacting server on server ... 220 server AMANDA index server (2.4.4p4) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed You need the line: server.domain.co.uk root in ~amanda/.amandahosts. I know it's had to believe but I do have that in my ~amanda /.amandahosts file Makes no difference. On the amanda server? If so, look for debug files in /tmp/amanda for more info and post those... -- *Matthew Claridge* Product Support Engineer RWA Limited Direct line: 02920 815 054 Email: [EMAIL PROTECTED] Web: www.rwa-net.co.uk
Re: amrecover error
On Tue, 16 Mar 2004 at 12:57pm, Sergio Pereira wrote when trying to recover a file using amrecover I get this error message: Continue [?/Y/n/s/t]? EOF, check amidxtaped.timestamp.debug file on bkpserver. And what are the contents of the file it's telling you to check? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover error
it's a text file with some network configuration, nothing else. I doing some tests with amrecover because I don't want to run into problems when the real recover show up. thx, sergio On Tue, 2004-03-16 at 13:06, Joshua Baker-LePain wrote: On Tue, 16 Mar 2004 at 12:57pm, Sergio Pereira wrote when trying to recover a file using amrecover I get this error message: Continue [?/Y/n/s/t]? EOF, check amidxtaped.timestamp.debug file on bkpserver. And what are the contents of the file it's telling you to check? --
Re: amrecover error
Please respond below quoted text -- it makes it easier to follow the conversation. On Tue, 16 Mar 2004 at 1:26pm, Sergio Pereira wrote On Tue, 2004-03-16 at 13:06, Joshua Baker-LePain wrote: On Tue, 16 Mar 2004 at 12:57pm, Sergio Pereira wrote when trying to recover a file using amrecover I get this error message: Continue [?/Y/n/s/t]? EOF, check amidxtaped.timestamp.debug file on bkpserver. And what are the contents of the file it's telling you to check? it's a text file with some network configuration, nothing else. I doing some tests with amrecover because I don't want to run into problems when the real recover show up. That's not what I meant. The error message tells you to look at the file amidxtaped.timestamp.debug which should be in /tmp/amanda on the host bkpserver. What are the contents of *that* file? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover error
here it is. amidxtaped: debug 1 pid 14387 ruid 1030 euid 1030: start at Tue Mar 16 13:53:41 2004 amidxtaped: version 2.4.4p2 amidxtaped: time 0.000: SECURITY USER root amidxtaped: time 0.000: bsd security: remote host backupserver user root local user amanda amidxtaped: time 0.000: amandahosts security check passed amidxtaped: time 0.000: CONFIG=daily amidxtaped: time 0.000: LABEL=daily1 amidxtaped: time 0.000: FSF=1 amidxtaped: time 0.000: HEADER amidxtaped: time 0.000: DEVICE=file:/amandatapes/daily amidxtaped: time 0.000: HOST=^backupserver$ amidxtaped: time 0.000: DISK=^/etc$ amidxtaped: time 0.000: DATESTAMP=20040316 amidxtaped: time 0.000: END amidxtaped: time 0.001: amrestore_nargs=0 amidxtaped: time 0.001: Ready to execv amrestore with: path = /usr/local/amanda/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = -l argv[4] = daily1 argv[5] = -f argv[6] = 1 argv[7] = file:/amandatapes/daily argv[8] = ^backserver$ argv[9] = ^/etc$ argv[10] = 20040316 Wrong label: 'daily6' amidxtaped: time 0.003: amrestore terminated normally with status: 1 amidxtaped: time 0.003: rewinding tape ... amidxtaped: time 0.004: done amidxtaped: time 0.004: pid 14387 finish time Tue Mar 16 13:53:41 2004 On Tue, 2004-03-16 at 13:26, Joshua Baker-LePain wrote: Please respond below quoted text -- it makes it easier to follow the conversation. On Tue, 16 Mar 2004 at 1:26pm, Sergio Pereira wrote On Tue, 2004-03-16 at 13:06, Joshua Baker-LePain wrote: On Tue, 16 Mar 2004 at 12:57pm, Sergio Pereira wrote when trying to recover a file using amrecover I get this error message: Continue [?/Y/n/s/t]? EOF, check amidxtaped.timestamp.debug file on bkpserver. And what are the contents of the file it's telling you to check? it's a text file with some network configuration, nothing else. I doing some tests with amrecover because I don't want to run into problems when the real recover show up. That's not what I meant. The error message tells you to look at the file amidxtaped.timestamp.debug which should be in /tmp/amanda on the host bkpserver. What are the contents of *that* file? --
Re: amrecover error
On Tue, 16 Mar 2004 at 1:56pm, Sergio Pereira wrote path = /usr/local/amanda/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = -l argv[4] = daily1 argv[5] = -f argv[6] = 1 argv[7] = file:/amandatapes/daily argv[8] = ^backserver$ argv[9] = ^/etc$ argv[10] = 20040316 Wrong label: 'daily6' Here's your error -- you have the wrong tape loaded. It's looking for daily6, but you have daily1 there. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover error
Hi, Madhvi Gokool schrieb: hello When running the command below on client server I get the following error - details are : - terrabkup# amrecover -C fullbkup -s sa01.terra.terrasky.mu -t sa01.terra.terrasky.mu -d /dev/nst0 AMRECOVER Version 2.4.3. Contacting server on sa01.terra.terrasky.mu ... amrecover: Unexpected end of file, check amindexd*debug on server sa01.terra.terrasky.mu Contents of amindexd.20040226113359.debug on backup server [EMAIL PROTECTED] amanda]$ more amindexd.20040226113359.debug amindexd: debug 1 pid 30290 ruid 512 euid 512: start at Thu Feb 26 11:33:59 2004 amindexd: version 2.4.3 amindexd: time 0.002: gethostbyaddr(10.10.20.40): hostname lookup failed ^^^ and this is your problem: your backupserver can not reverse-lookup your client. it took the ip-adress and asked your nameserver for the name of your client host and got a bad answer back. Fix the reverse-mapping of your client ip-adress and amrecover will be much happier. Christoph
Re: amrecover error
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger [EMAIL PROTECTED] wrote: here is the error i get when i go through the process of restoring something amrecover setdisk /testData AGAIN: /data is a seperate partition that is used as the main holding disk Scanning /data... lost+found: skipping cruft directory, perhaps you should delete it. 200 Disk set to /testData. amrecover ls 2003-09-25 . 2003-09-25 File1 2003-09-25 File2 amrecover add File1 Added /File1 amrecover extract Extracting files using tape drive 0 on host bs1. The following tapes are needed: DailySet13 Restoring files into directory /var/lib/amanda Continue [?/Y/n]? Y Extracting files using tape drive 0 on host bs1. Load tape DailySet13 now Continue [?/Y/n/t]? Y EOF, check amidxtaped.debug file on bs1. Is the tape DailySet13 in the drive? What's in amidxtaped.debug file on bs1 ? Frank amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n]? -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amrecover error
This is what is in amidxtaped.debug file:
amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25
12:15:38 2003
amidxtaped: version 2.4.3
amidxtaped: time 0.000: SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user
root local user amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: 6
amidxtaped: time 0.001: amrestore_nargs=6
amidxtaped: time 0.001: -h
amidxtaped: time 0.001: -p
amidxtaped: time 0.001: DailySet13
amidxtaped: time 0.001: ^bs1.domain.name$
amidxtaped: time 0.001: ^/testData$
amidxtaped: time 0.001: 20030925
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = DailySet13
argv[4] = ^bs1.domain.name$
argv[5] = ^/testData$
argv[6] = 20030925
amrestore: could not stat DailySet13
amidxtaped: time 0.007: amrestore terminated normally with status: 2
amidxtaped: could not stat DailySet13
amidxtaped: time 0.007: could not stat DailySet13
amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
DailySet13 tape is in the drive
and this is how a copy of my amrecover session
[EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t
bs1.domain.name -d /dev/nst0
AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
220 bs1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-09-25)
200 Working date set to 2003-09-25.
200 Config set to DailySet1.
501 No index records for host: bs1. Invalid?
Trying host bs1.domain.name ...
200 Dump host set to bs1.domain.name.
Trying disk /var ...
Trying disk hda6 ...
Can't determine disk and mount point from $CWD '/var/lib/amanda' -- I
dont understand this error here
amrecover help
valid commands are:
add path1 ... - add to extraction list (shell wildcards)
addx path1 ...- add to extraction list (regular expressions)
cd directory - change cwd on virtual file system (shell wildcards)
cdx directory - change cwd on virtual file system (regular expressions)
clear - clear extraction list
delete path1 ... - delete from extraction list (shell wildcards)
deletex path1 ... - delete from extraction list (regular expressions)
extract - extract selected files from tapes
exit
help
history - show dump history of disk
list [filename] - show extraction list, optionally writing to file
lcd directory - change cwd on local file system
ls- list directory on virtual file system
lpwd - show cwd on local file system
mode - show the method used to extract SMB shares
pwd - show cwd on virtual file system
quit
listdisk [diskdevice] - list disks
setdate {-MM-DD|--MM-DD|---DD} - set date of look
setdisk diskname [mountpoint] - select disk on dump host
sethost host - select dump host
settape [host:][device|default] - select tape server and/or device
setmode smb|tar - select the method used to extract SMB shares
amrecover setdisk /testData
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover sethost bs1.domain.name
200 Dump host set to bs1.domain.name.
amrecover settape DailySet13
Using tape DailySet13 from server bs1.domain.name.
amrecover cd /testData/
/testData
amrecover ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover add File*
Added /File1
Added /File2
amrecover extract
Extracting files using tape drive DailySet13 on host bs1.domain.name.
The following tapes are needed: DailySet13
Restoring files into directory /testData
Continue [?/Y/n]? Y
Extracting files using tape drive DailySet13 on host bs1.domain.name.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.domain.name.
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
amrecover
Frank Smith wrote:
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger [EMAIL PROTECTED] wrote:
here is the error i get when i go through the process of restoring something
amrecover setdisk /testData
AGAIN: /data is a seperate partition that is used as the main holding disk
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover add File1
Added /File1
amrecover extract
Extracting files using tape drive 0 on host bs1.
The following tapes are needed: DailySet13
Restoring files into directory /var/lib/amanda
Continue [?/Y/n]? Y
Extracting files using tape drive 0 on host bs1.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.
Is the tape DailySet13 in the drive?
What's in amidxtaped.debug file on bs1 ?
Frank
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
Re: amrecover error
On Thu, Sep 25, 2003 at 11:53:22AM -0500, chris weisiger wrote: This is what is in amidxtaped.debug file: amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 ... argv[5] = ^/testData$ argv[6] = 20030925 amrestore: could not stat DailySet13 huh, why does it try to open a file called DailySet13? and this is how a copy of my amrecover session [EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t bs1.domain.name -d /dev/nst0 AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ... 220 bs1 AMANDA index server (2.4.3) ready. 200 Access OK Setting restore date to today (2003-09-25) 200 Working date set to 2003-09-25. 200 Config set to DailySet1. 501 No index records for host: bs1. Invalid? Trying host bs1.domain.name ... 200 Dump host set to bs1.domain.name. Trying disk /var ... Trying disk hda6 ... Can't determine disk and mount point from $CWD '/var/lib/amanda' -- I dont understand this error here Default disk is the directory you are working in when you run amrecover. But that is not a DLE apparently. BTW it will recover into there, not where you think/want it to recover. I.e. it will be recovered relative to your CurrentWorkingDirectory (CDW), not relative to /. amrecover help ... settape [host:][device|default] - select tape server and/or device Note this amrecover settape DailySet13 Using tape DailySet13 from server bs1.domain.name. That is not what you did. Is DailySet13 a host? A tape device? No, it is the label of the tape in the tape device on the server host. But normally you do not know at this point what tape you will need. Amrecover will tell you that later. amrecover extract Extracting files using tape drive DailySet13 on host bs1.domain.name. Whoops, there is it trying to use a tape drive named DailySet13 rather than something like /dev/nst0 or /dev/rmt/0ln. The following tapes are needed: DailySet13 Here is where you find out what tapes are going to be needed. Restoring files into directory /testData But under $CWD as / Continue [?/Y/n]? Y Extracting files using tape drive DailySet13 on host bs1.domain.name. Load tape DailySet13 now Here is where you go to the closet and find the needed tapes. You now load it/them and make sure they are rewound. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover error
--On Thursday, September 25, 2003 11:53:22 -0500 chris weisiger [EMAIL PROTECTED]
wrote:
This is what is in amidxtaped.debug file:
amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 12:15:38 2003
amidxtaped: version 2.4.3
amidxtaped: time 0.000: SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user root local
user amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: 6
amidxtaped: time 0.001: amrestore_nargs=6
amidxtaped: time 0.001: -h
amidxtaped: time 0.001: -p
amidxtaped: time 0.001: DailySet13
amidxtaped: time 0.001: ^bs1.domain.name$
amidxtaped: time 0.001: ^/testData$
amidxtaped: time 0.001: 20030925
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = DailySet13
argv[4] = ^bs1.domain.name$
argv[5] = ^/testData$
argv[6] = 20030925
amrestore: could not stat DailySet13
amidxtaped: time 0.007: amrestore terminated normally with status: 2
amidxtaped: could not stat DailySet13
amidxtaped: time 0.007: could not stat DailySet13
amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
DailySet13 tape is in the drive
Was the tape rewound first (as it needs to be), or was it sitting
at the end after the last backup? Looks like its not able to read
the header, probably because you're not at the begining of the tape.
and this is how a copy of my amrecover session
[EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t
bs1.domain.name -d /dev/nst0
AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
220 bs1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-09-25)
200 Working date set to 2003-09-25.
200 Config set to DailySet1.
501 No index records for host: bs1. Invalid?
Trying host bs1.domain.name ...
200 Dump host set to bs1.domain.name.
Trying disk /var ...
Trying disk hda6 ...
Can't determine disk and mount point from $CWD '/var/lib/amanda' -- I dont
understand this error here
Amanda defaults the DLE to recover to be the directory you're in
when you run it, so if your cwd is /var/lib/amanda, it looks for
a DLE that contains it. If you're restoring to a different directory
(as you are, and is often a good idea, especially when testing), then
you just need to use the setdisk command to pick the DLE you want and
just ignore the warning.
Frank
amrecover help
valid commands are:
add path1 ... - add to extraction list (shell wildcards)
addx path1 ...- add to extraction list (regular expressions)
cd directory - change cwd on virtual file system (shell wildcards)
cdx directory - change cwd on virtual file system (regular expressions)
clear - clear extraction list
delete path1 ... - delete from extraction list (shell wildcards)
deletex path1 ... - delete from extraction list (regular expressions)
extract - extract selected files from tapes
exit
help
history - show dump history of disk
list [filename] - show extraction list, optionally writing to file
lcd directory - change cwd on local file system
ls- list directory on virtual file system
lpwd - show cwd on local file system
mode - show the method used to extract SMB shares
pwd - show cwd on virtual file system
quit
listdisk [diskdevice] - list disks
setdate {-MM-DD|--MM-DD|---DD} - set date of look
setdisk diskname [mountpoint] - select disk on dump host
sethost host - select dump host
settape [host:][device|default] - select tape server and/or device
setmode smb|tar - select the method used to extract SMB shares
amrecover setdisk /testData
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover sethost bs1.domain.name
200 Dump host set to bs1.domain.name.
amrecover settape DailySet13
Using tape DailySet13 from server bs1.domain.name.
amrecover cd /testData/
/testData
amrecover ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover add File*
Added /File1
Added /File2
amrecover extract
Extracting files using tape drive DailySet13 on host bs1.domain.name.
The following tapes are needed: DailySet13
Restoring files into directory /testData
Continue [?/Y/n]? Y
Extracting files using tape drive DailySet13 on host bs1.domain.name.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.domain.name.
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
amrecover
Frank Smith wrote:
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger [EMAIL PROTECTED]
wrote:
here is the error i get when i go through the process of restoring something
Re: amrecover error
so how do i rewind the tape?
Frank Smith wrote:
--On Thursday, September 25, 2003 11:53:22 -0500 chris weisiger [EMAIL PROTECTED] wrote:
This is what is in amidxtaped.debug file:
amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 12:15:38 2003
amidxtaped: version 2.4.3
amidxtaped: time 0.000: SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user root local user
amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: 6
amidxtaped: time 0.001: amrestore_nargs=6
amidxtaped: time 0.001: -h
amidxtaped: time 0.001: -p
amidxtaped: time 0.001: DailySet13
amidxtaped: time 0.001: ^bs1.domain.name$
amidxtaped: time 0.001: ^/testData$
amidxtaped: time 0.001: 20030925
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = DailySet13
argv[4] = ^bs1.domain.name$
argv[5] = ^/testData$
argv[6] = 20030925
amrestore: could not stat DailySet13
amidxtaped: time 0.007: amrestore terminated normally with status: 2
amidxtaped: could not stat DailySet13
amidxtaped: time 0.007: could not stat DailySet13
amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
DailySet13 tape is in the drive
Was the tape rewound first (as it needs to be), or was it sitting
at the end after the last backup? Looks like its not able to read
the header, probably because you're not at the begining of the tape.
and this is how a copy of my amrecover session
[EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t bs1.domain.name -d /dev/nst0
AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
220 bs1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-09-25)
200 Working date set to 2003-09-25.
200 Config set to DailySet1.
501 No index records for host: bs1. Invalid?
Trying host bs1.domain.name ...
200 Dump host set to bs1.domain.name.
Trying disk /var ...
Trying disk hda6 ...
Can't determine disk and mount point from $CWD '/var/lib/amanda' -- I dont understand this error here
Amanda defaults the DLE to recover to be the directory you're in
when you run it, so if your cwd is /var/lib/amanda, it looks for
a DLE that contains it. If you're restoring to a different directory
(as you are, and is often a good idea, especially when testing), then
you just need to use the setdisk command to pick the DLE you want and
just ignore the warning.
Frank
amrecover help
valid commands are:
add path1 ... - add to extraction list (shell wildcards)
addx path1 ...- add to extraction list (regular expressions)
cd directory - change cwd on virtual file system (shell wildcards)
cdx directory - change cwd on virtual file system (regular expressions)
clear - clear extraction list
delete path1 ... - delete from extraction list (shell wildcards)
deletex path1 ... - delete from extraction list (regular expressions)
extract - extract selected files from tapes
exit
help
history - show dump history of disk
list [filename] - show extraction list, optionally writing to file
lcd directory - change cwd on local file system
ls- list directory on virtual file system
lpwd - show cwd on local file system
mode - show the method used to extract SMB shares
pwd - show cwd on virtual file system
quit
listdisk [diskdevice] - list disks
setdate {-MM-DD|--MM-DD|---DD} - set date of look
setdisk diskname [mountpoint] - select disk on dump host
sethost host - select dump host
settape [host:][device|default] - select tape server and/or device
setmode smb|tar - select the method used to extract SMB shares
amrecover setdisk /testData
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover sethost bs1.domain.name
200 Dump host set to bs1.domain.name.
amrecover settape DailySet13
Using tape DailySet13 from server bs1.domain.name.
amrecover cd /testData/
/testData
amrecover ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover add File*
Added /File1
Added /File2
amrecover extract
Extracting files using tape drive DailySet13 on host bs1.domain.name.
The following tapes are needed: DailySet13
Restoring files into directory /testData
Continue [?/Y/n]? Y
Extracting files using tape drive DailySet13 on host bs1.domain.name.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.domain.name.
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
amrecover
Frank Smith wrote:
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger [EMAIL PROTECTED] wrote:
here is the error i get when i go through the process of restoring something
amrecover setdisk /testData
AGAIN: /data is a seperate partition that
Re: amrecover error
On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: so how do i rewind the tape? mt rewind -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: amrecover error
When i run that command i get the following: /dev/tape: No such file or directory do i have to create a symlink from /dev/sg0 to /dev/tape ?? Eric Siegerman wrote: On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: so how do i rewind the tape? mt rewind -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: amrecover error
--On Thursday, September 25, 2003 13:01:49 -0500 chris weisiger [EMAIL PROTECTED] wrote: When i run that command i get the following: /dev/tape: No such file or directory do i have to create a symlink from /dev/sg0 to /dev/tape ?? Most likely your tape drive is /dev/st0, sg0 is probably the changer device. The default device for mt on linux is /dev/tape, but you can also tell it what device to use, such as mt -f /dev/st0 rewind or you can symlink /dev/tape to whatever device it is. Yoiu can check dmesg or your boot messages to see what device your system thinks the tape drive is. BTW, I think Jon had the right idea about your amrecover problem. I overlooked that you were trying to use a tapelabel as the tape device. Frank Eric Siegerman wrote: On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: so how do i rewind the tape? mt rewind -- | | /\ | -_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amrecover error
On Sun, Jan 12, 2003 at 01:48:09PM -0500, Gene Heskett wrote: On Sunday 12 January 2003 12:44, Jean-Louis Martineau wrote: On Sun, Jan 12, 2003 at 12:04:51PM -0500, Gene Heskett wrote: amrecover extract Extracting files using tape drive 0 on host 192.168.1.3. tape drive 0 That's bad, you should set it to your tape device (eg. /dev/nst0) with the settape command or the -d command line argument. Jean-Louis That looks as if that was it, many thanks Jean-Louis. Its proceeding normally now. One Q though. Why doesn't it not get this from the amanda.conf file, as I have the latest options setup there so its even supposed to use the changer, allthough that last is a puzzle since the sample shows the drive, and not the robot? You not neceserely recover from your amanda tape host. You can restore from any tape drive connected to any host (amidxtaped must be configured). The changer will be used if: 1- your config exist on the tape server host 2- that config have a changer configured 3- amrecover_changer is set in the config 4- the tape drive is the same as amrecover_changer. amrecover_changer should be set to a tape device. The default tape driver from amrecover is set at configuration time. Jean-Louis -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly -- 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: amrecover error
On Sun, Jan 12, 2003 at 12:04:51PM -0500, Gene Heskett wrote: amrecover extract Extracting files using tape drive 0 on host 192.168.1.3. tape drive 0 That's bad, you should set it to your tape device (eg. /dev/nst0) with the settape command or the -d command line argument. 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: amrecover error
On Sunday 12 January 2003 12:44, Jean-Louis Martineau wrote: On Sun, Jan 12, 2003 at 12:04:51PM -0500, Gene Heskett wrote: amrecover extract Extracting files using tape drive 0 on host 192.168.1.3. tape drive 0 That's bad, you should set it to your tape device (eg. /dev/nst0) with the settape command or the -d command line argument. Jean-Louis That looks as if that was it, many thanks Jean-Louis. Its proceeding normally now. One Q though. Why doesn't it not get this from the amanda.conf file, as I have the latest options setup there so its even supposed to use the changer, allthough that last is a puzzle since the sample shows the drive, and not the robot? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
Re: Amrecover error -- index directory DNE?
Doug Silver writes: [root@dev amanda]# ll /var/amanda/daily/index total 21 drwxr-xr-x 20 root wheel 1024 Apr 5 11:07 ./ drwxr-x--- 5 root wheel 1536 Apr 5 07:21 ../ .. drwxr-xr-x 3 root wheel 512 Apr 5 11:07 dev/ .. The user that amindexd runs as (from inetd.conf) needs to be able to read/write the index directories. Unless that user is root or in group wheel here, they'll not be able to chdir into /var/amanda/daily/index in the first place, and depending on the permissions under dev/, may not be able to uncompress the index files when it has to. Change the ownerships/permissions so that the user your amandaidx runs under can read/write down the index tree, and you should be right. Regards, Chris
Re: Amrecover error -- index directory DNE?
On Sat, 6 Apr 2002, Chris Pascoe wrote: Doug Silver writes: [root@dev amanda]# ll /var/amanda/daily/index total 21 drwxr-xr-x 20 root wheel 1024 Apr 5 11:07 ./ drwxr-x--- 5 root wheel 1536 Apr 5 07:21 ../ .. drwxr-xr-x 3 root wheel 512 Apr 5 11:07 dev/ .. The user that amindexd runs as (from inetd.conf) needs to be able to read/write the index directories. Unless that user is root or in group wheel here, they'll not be able to chdir into /var/amanda/daily/index in the first place, and depending on the permissions under dev/, may not be able to uncompress the index files when it has to. Change the ownerships/permissions so that the user your amandaidx runs under can read/write down the index tree, and you should be right. Regards, Chris Aaah, foobar!! That was it. I'm removing myself from the wheel group for the rest of the day ... -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
RE: amrecover error did not get a reserved port
John, amrecover: did not get a reserved port: 50014 When compiled I used the flag --with-portrange=5,50100 ... Any suggestions as to what I am doing wrong? You didn't do anything wrong -- I did :-). Like a true professional I waited until I needed to do a restore before testing! So I think I probably beat you there. This is a known problem from about a year ago. Give the following patch a try. It's in the current sources. Did I miss this in the FAQs or should I add this? I didn't see it on the amanda bugs page. Regards, Jim The message has been checked for all known viruses by the Centric Telecom Virus Control Centre. (Powered by Messagelabs)
Re: amrecover error did not get a reserved port
Like a true professional I waited until I needed to do a restore before testing! ... A real pro! :-) This is a known problem from about a year ago. ... Did I miss this in the FAQs or should I add this? I didn't see it on the amanda bugs page. Well, the theory was that it wouldn't be years between Amanda releases. Sigh. Feel free to add it to the FAQ (make sure you mention 2.4.2p2 -- I don't think it was there prior to that and hopefully is gone afterward). You're right that it probably should also go on the patches page. It's just a matter of remembering to do it and finding the time. Jim John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover error did not get a reserved port
amrecover: did not get a reserved port: 50014 When compiled I used the flag --with-portrange=5,50100 ... Any suggestions as to what I am doing wrong? You didn't do anything wrong -- I did :-). This is a known problem from about a year ago. Give the following patch a try. It's in the current sources. If you want to know all the gory details, check out docs/PORT.USAGE in the latest sources. Jim Mozley John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] stream_client.diff Description: stream_client.diff
Re: amrecover: error reading tape: Connection reset by peer
- i have to launch /usr/local/sbin/amrecover -d /dev/rmt/0 instead of /usr/local/sbin/amrecover DailySet1 One point -- you should use a non-rewinding device name for anything you do with Amanda. So that should be -d /dev/rmt/0n. Also, I'm guessing, based on the device name, that you're running on Solaris. Your original report mentioned /dev/rmt/0bn. Don't use the BSD names (the ones with 'b' in them). Those process tapes in a slightly different way than the default (no 'b') System V way that Amanda (more or less) expects. Sorry for annoying. I just post my solution in hope it helps some. You haven't been annoying at all (far from it). And I, at least, really appreciate hearing that a problem got resolved, and what it took to make it work. As you said, there is always the hope that what you found will help someone else later. Lorenzo John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover error
I am using amanda2.4.2p1 version on a linux machine. ... You sure about that? The amrecover output you posted said: AMRECOVER Version 2.4.1p1. Contacting server on blue ... In any case, I think this is a known problem with amrecover and Linux. You'll need to upgrade that client to 2.4.2p2 and, if you set a portrange with ./configure, you'll also need to try the following patch. I've given this patch to three people now (including you) but have not heard back about whether it works or not (it did in my minimal testing). Note that it only applies against 2.4.2p2, no other version of Amanda. Rajesh John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] stream_client.diff
Re: amrecover error
It seems to me that assuming a default is the wrong thing to do. Many of the other am* utilities do not and in this case, it leads to quite misleading behaviour. ... Agreed, however ... Could it be fixed? The problem is backward compatibility. All those Amanda folks out there depending on the default behavior are going to be upset when what used to work starts failing, especially if they have automated methods or non-technical staff doing the work (i.e. procedural documentation has to be changed). I have a note to fix amrecover/amindexd so at least a proper error message is generated, but haven't had time to look into it yet. Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover error
Hi. When running `amrecover', I am getting the following error message: AMRECOVER Version 2.4.2. Contacting server on scooby ... ... amrecover: Unexpected server end of file What's in amindexd*debug on scooby? Did you give amrecover a valid config name on the command line? Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: amrecover: Error binding socket: Permission denied
When I ran amrecover (2.4.1p1) today to restore some NT files via Samba (2.06) it requested a tape, for the level 0 backup, and a holding area, for the incrementals. The level 0 files came off the tape without any problems, but then I received an error trying to recover the holding area files. [Stevens, Julian C] Update on this problem. The holding area is not part of the problem as I have just attempted an amrecover which required 2 tapes and got very similar results. i.e. The files were recovered from the first tape fine, but when I loaded the second tape I got: amrecover: Error binding socket: Permission denied [Stevens, Julian C] The consequences of this are now more far reaching than I first thought so I would really appreciate any suggestions there might be out there! Thanks, Julian Stevens -- BAE SYSTEMS Land Sea Systems Grange Road Christchurch Dorset BH23 4JE - Tel +44 (0)1202 404426 Fax +44 (0)1202 408308 e-mail [EMAIL PROTECTED] File: Amindexd.debugFile: Amrecover.debug
