amrecover fails if DLE was compressed
Hi all.
I've just put amanda 2.6.1p2 and my existing (and long working) config files
onto a new machine, and tested that it worked to both backup and recover.
Then I uninstalled the 2.6.1p2 and installed amanda 3.3.2
Now I get a broken pipe in the amrecover log, exactly after I answer the
set owner/mode? question and the amrecover window hangs
until I control-C out of it.
but only if the DLE includes compression.If I turn off compression
and redo the backups, a recover will succeed. Even a recover which
involved 2 tapes.
versions:
tar (GNU tar) 1.23
gzip 1.3.12
Any idea what the problem is?
Deb
Here are the amrecover and amandad logs, since they contain errors.
I have other logs too if you need them, but I don't see any complaints in them.
===
amrecover.debug
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: pid 29473 ruid 0 euid 0
version 3.3.2: start at Tue Dec 11 13:11:11 2012
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: config_overrides: conf daily
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: pid 29473 ruid 0 euid 0
version 3.3.2: rename at Tue Dec 11 13:11:11 2012
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: security_getdriver(name=bsd)
returns 0x7fc6596bd2e0
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
security_handleinit(handle=0xfd0260, driver=0x7fc6596bd2e0 (BSD))
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: dgram_bind: setting up a
socket with family 2
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: bind_portrange2: Skip port
848: Owned by gdoi.
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: bind_portrange2: Try port
849: Available - Success
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: dgram_bind: socket 3 bound
to 0.0.0.0:849
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
dgram_send_addr(addr=0xfd02a0, dgram=0x7fc6596c9da8)
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: (sockaddr_in *)0xfd02a0 = {
2, 10080, 131.225.121.103 }
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: dgram_send_addr:
0x7fc6596c9da8-socket = 3
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
dgram_recv(dgram=0x7fc6596c9da8, timeout=0, fromaddr=0x7fc6596d9da0)
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: (sockaddr_in
*)0x7fc6596d9da0 = { 2, 10080, 131.225.121.103 }
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
dgram_recv(dgram=0x7fc6596c9da8, timeout=0, fromaddr=0x7fc6596d9da0)
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: (sockaddr_in
*)0x7fc6596d9da0 = { 2, 10080, 131.225.121.103 }
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
dgram_send_addr(addr=0xfd02a0, dgram=0x7fc6596c9da8)
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: (sockaddr_in *)0xfd02a0 = {
2, 10080, 131.225.121.103 }
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: dgram_send_addr:
0x7fc6596c9da8-socket = 3
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
security_streaminit(stream=0xfd7840, driver=0x7fc6596bd2e0 (BSD))
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: make_socket opening socket
with family 2
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: connect_port: Try port
5: available - Success
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: connected to
131.225.121.103:50006
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: our side is 0.0.0.0:5
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: try_socksize: send buffer
size is 65536
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: try_socksize: receive buffer
size is 65536
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover:
security_close(handle=0xfd0260, driver=0x7fc6596bd2e0 (BSD))
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: sending: FEATURES
9efefbff1f
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: sending: DATE 2012-12-11
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: sending: SCNF daily
Tue Dec 11 13:11:11 2012: thd-0xfc4490: amrecover: sending: HOST mynode.fqdn
Tue Dec 11 13:11:19 2012: thd-0xfc4490: amrecover: user command: 'setdate
2012-12-06'
Tue Dec 11 13:11:19 2012: thd-0xfc4490: amrecover: sending: DATE 2012-12-06
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: user command: 'setdisk /var'
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: sending: DISK /var
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: sending: OISD /
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: sending: OLSD /
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: add_dir_list_item: Adding
2012-12-06-12-56-36 0 adUXdaily-0daily-827test:3 3 /.
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: add_dir_list_item: Adding
2012-12-06-12-56-36 0 adUXdaily-0daily-827test:3 3 /account/
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: add_dir_list_item: Adding
2012-12-06-12-56-36 0 adUXdaily-0daily-827test:3 3 /adm/
Tue Dec 11 13:11:24 2012: thd-0xfc4490: amrecover: add_dir_list_item: Adding
2012-12-06-12-56-36 0 adUXdaily-0daily-827test:3 3 /cache/
Tue Dec 11 13:11:24 2012: thd-0xfc4490:
RE: amrecover fails with TypeError in method 'debug'...
Hi Greg,
I did see your last thread, that did help thanks.
Building the Alpha from Trunk, then applying the patch from...
http://forums.zmanda.com/showthread.php?3691-amrecover-segmentation-fault
...fixed the 'extract' error for me.
I got a stacktrace using Carp::longmess() at the point where $line is tainted
in amidxtaped.pl/readline() by checking with...
sub is_tainted { return ! eval { eval(# . substr(join(, @_), 0, 0)); 1 }; }
This is the stack when when the line is tainted...
[stacktrace]
Mon Apr 30 11:39:33 2012: thd-0x10765f0: amidxtaped: pid 1305 ruid 503 euid 503
version 4.0.0alpha.svn.4682: start at Mon Apr 30 11:39:33 2012
Mon Apr 30 11:39:33 2012: thd-0x10765f0: amidxtaped: $line = '1'
Mon Apr 30 11:39:33 2012: thd-0x10765f0: amidxtaped: at
/usr/local/libexec/amanda/amidxtaped line 198
main::ClientService::read_command('main::ClientService=HASH(0xbf57c8)')
called at /usr/local/libexec/amanda/amidxtaped line 186
main::ClientService::setup_streams('main::ClientService=HASH(0xbf57c8)') called
at /usr/local/libexec/amanda/amidxtaped line 145
main::ClientService::run('main::ClientService=HASH(0xbf57c8)') called
at /usr/local/libexec/amanda/amidxtaped line 1056
main::__ANON__() called at /usr/local/share/perl5/Amanda/MainLoop.pm
line 819
Amanda::MainLoop::__ANON__('Amanda::MainLoop::Source=HASH(0x17e91b0)')
called at /usr/local/share/perl5/Amanda/MainLoop.pm line 790
eval {...} called at /usr/local/share/perl5/Amanda/MainLoop.pm line 790
Amanda::MainLoop::run() called at /usr/local/libexec/amanda/amidxtaped
line 1057
main::main() called at /usr/local/libexec/amanda/amidxtaped line 1063
Mon Apr 30 11:39:33 2012: thd-0x10765f0: amidxtaped: critical (fatal):
TypeError in method 'debug', argument 1 of type 'char *'
amidxtaped: TypeError in method 'debug', argument 1 of type 'char *'
[/stacktrace]
Best regards,
Kervin
Adevsoft Inc
Business Software Development
http://adevsoft.com/
From: Greg Copeland [mailto:gtcopel...@gmail.com]
Sent: Monday, April 30, 2012 12:03 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amrecover fails with TypeError in method 'debug'...
On Sun, 2012-04-29 at 18:20 +, Kervin L. Pierre wrote:
Hi,
Look for an email from me in the archives, with subject, Re: Recovery Help
Request [RESOLVED], from April 13th, 2012.
For good measure, you might also want to look in the archives for a message
with subject, Re: amrecover failure [RESOLVED], on April 26th, 2012.
Both sets of emails, bugs, and fixes apply to 3.3.1 stable, which apparently
isn't all that stable. I sincerely hope they'll push out a 3.3.2, with the
patches applied for these known, show-stopper, bugs.
Best of luck.
Regards,
I'm following the simple recovery example from the wiki...
http://wiki.zmanda.com/index.php/GSWA/Recovering_Files
Worked though all the issues but now I'm at the 'extract' and I'm getting an
error...
amrecover - amidxtaped closed the connection
amrecover - can't talk to tape server: (null)
Further inspection of /var/log/messages gives...
amidxtaped[2784]: TypeError in method 'debug', argument 1 of type 'char *'
I've found someone had run into this issue before 'June 2011'...
http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6929sid=f2141406dc79480edd30a1200443e9a6
They mentioned patching a Perl script but I haven't found the one they're
referring to.
Does anyone have instructions on how to fix or workaround this issue?
I'm using 3.3.1 built from source on an update to date Amazon Linux install.
Best regards,
Kervin
Adevsoft Inc
Business Software Development
http://adevsoft.com/
--
Greg Copeland g...@copelandconsulting.net
Copeland Computer Consulting
amrecover fails with TypeError in method 'debug'...
Hi, I'm following the simple recovery example from the wiki... http://wiki.zmanda.com/index.php/GSWA/Recovering_Files Worked though all the issues but now I'm at the 'extract' and I'm getting an error... amrecover - amidxtaped closed the connection amrecover - can't talk to tape server: (null) Further inspection of /var/log/messages gives... amidxtaped[2784]: TypeError in method 'debug', argument 1 of type 'char *' I've found someone had run into this issue before 'June 2011'... http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6929sid=f2141406dc79480edd30a1200443e9a6 They mentioned patching a Perl script but I haven't found the one they're referring to. Does anyone have instructions on how to fix or workaround this issue? I'm using 3.3.1 built from source on an update to date Amazon Linux install. Best regards, Kervin Adevsoft Inc Business Software Development http://adevsoft.com/
Re: amrecover fails with TypeError in method 'debug'...
On Sun, 2012-04-29 at 18:20 +, Kervin L. Pierre wrote: Hi, Look for an email from me in the archives, with subject, Re: Recovery Help Request [RESOLVED], from April 13th, 2012. For good measure, you might also want to look in the archives for a message with subject, Re: amrecover failure [RESOLVED], on April 26th, 2012. Both sets of emails, bugs, and fixes apply to 3.3.1 stable, which apparently isn't all that stable. I sincerely hope they'll push out a 3.3.2, with the patches applied for these known, show-stopper, bugs. Best of luck. Regards, I'm following the simple recovery example from the wiki... http://wiki.zmanda.com/index.php/GSWA/Recovering_Files Worked though all the issues but now I'm at the 'extract' and I'm getting an error... amrecover - amidxtaped closed the connection amrecover - can't talk to tape server: (null) Further inspection of /var/log/messages gives... amidxtaped[2784]: TypeError in method 'debug', argument 1 of type 'char *' I've found someone had run into this issue before 'June 2011'... http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6929sid=f2141406dc79480edd30a1200443e9a6 They mentioned patching a Perl script but I haven't found the one they're referring to. Does anyone have instructions on how to fix or workaround this issue? I'm using 3.3.1 built from source on an update to date Amazon Linux install. Best regards, Kervin Adevsoft Inc Business Software Development http://adevsoft.com/ -- Greg Copeland g...@copelandconsulting.net Copeland Computer Consulting
Re: amrecover fails - problems loading correct tape
Oscar Ricardo Silva wrote: [amanda@amanda tmp]$ cat ./amanda/server/newbktest/amidxtaped.20110427135604.debug 1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version 2.6.1p2: start at Wed Apr 27 13:56:04 2011 1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2 You are running the 2.6.1p2, fix the xinetd configuration to run 3.2.2. Jean-Louis Anybody else run into this? I couldn't find any related items in the list archives.
Re: amrecover fails - problems loading correct tape
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not found
issues decided to try 3.2.2 (currently using 2.6.1p2). Right now
backups on the new version work fine. The backup runs, files are
created on the virtual tapes (writing backups to disk), mail is sent,
etc. The problem comes when I try to recover a file and it appears to
be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped: DEVICE=chg-disk:/amandatapes/newbktapes
1303930564.555225: amidxtaped: HOST=^networking.its.utexas.edu$
1303930564.555237: amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking labels
1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERROR error Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0 1
1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for newbktape-10
changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERROR error Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2b93
59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b93
59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b935
9c570f3] /usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use per
run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes, and my
tapetype is set for about 30Gb. I am backing up this machine, and pieces
of the one out in the shop that runs my cnc milling machine, on a 5 day
cycle, so each days runs vary from 12Gb to 25Gb. 500 megs I outgrew by
1998. ;-)
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
http://tinyurl.com/ddg5bz
http://www.cantrip.org/gatto.html
audiophile, n:
Someone who listens to the equipment instead of the music.
Re: amrecover fails - problems loading correct tape
On 04/27/2011 04:10 PM, gene heskett wrote:
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not found
issues decided to try 3.2.2 (currently using 2.6.1p2). Right now
backups on the new version work fine. The backup runs, files are
created on the virtual tapes (writing backups to disk), mail is sent,
etc. The problem comes when I try to recover a file and it appears to
be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped: DEVICE=chg-disk:/amandatapes/newbktapes
1303930564.555225: amidxtaped: HOST=^networking.its.utexas.edu$
1303930564.555237: amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking labels
1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0 1
1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for newbktape-10
changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2b93
59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b93
59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b935
9c570f3] /usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use per
run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes, and my
tapetype is set for about 30Gb. I am backing up this machine, and pieces
of the one out in the shop that runs my cnc milling machine, on a 5 day
cycle, so each days runs vary from 12Gb to 25Gb. 500 megs I outgrew by
1998. ;-)
This is just a test and I'm backing up /boot on a single system. Since
this is currently a test I didn't want to wait too long for a backup to
complete. My production backups are generally 400-500GB per night.
Oscar
Re: amrecover fails - problems loading correct tape
On 04/27/2011 03:58 PM, Jean-Louis Martineau wrote: Oscar Ricardo Silva wrote: [amanda@amanda tmp]$ cat ./amanda/server/newbktest/amidxtaped.20110427135604.debug 1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version 2.6.1p2: start at Wed Apr 27 13:56:04 2011 1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2 You are running the 2.6.1p2, fix the xinetd configuration to run 3.2.2. Jean-Louis Anybody else run into this? I couldn't find any related items in the list archives. ARGH ... and this is what happens when you build multiple versions of amanda and are not careful of links and which binary is really being called I installed the 3.2.2 version of amanda in a different directory but the restore was calling the 2.6.1p2 version. Thank you.
Re: amrecover fails - problems loading correct tape
On Wednesday, April 27, 2011 05:33:53 PM Oscar Ricardo Silva did opine:
On 04/27/2011 04:10 PM, gene heskett wrote:
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not
found issues decided to try 3.2.2 (currently using 2.6.1p2). Right
now backups on the new version work fine. The backup runs, files
are created on the virtual tapes (writing backups to disk), mail
is sent, etc. The problem comes when I try to recover a file and it
appears to be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped:
DEVICE=chg-disk:/amandatapes/newbktapes 1303930564.555225:
amidxtaped: HOST=^networking.its.utexas.edu$ 1303930564.555237:
amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking
labels 1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0
1 1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for
newbktape-10 changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2
b93 59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b
93 59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b9
35 9c570f3]
/usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use
per run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes,
and my tapetype is set for about 30Gb. I am backing up this machine,
and pieces of the one out in the shop that runs my cnc milling
machine, on a 5 day cycle, so each days runs vary from 12Gb to 25Gb.
500 megs I outgrew by 1998. ;-)
This is just a test and I'm backing up /boot on a single system. Since
this is currently a test I didn't want
amanda 3.3beta: amrecover fails because of decompression?
Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Re: amanda 3.3beta: amrecover fails because of decompression?
Do the dump are compressed on client or server? Post the amrecover and amidxtaped debug files. As a workaround, you can do the following in amrecover before the extract: set property command-options -z Jean-Louis Dennis Benndorf wrote: Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis
Re: amanda 3.3beta: amrecover fails because of decompression?
amrecover is 3.1.1, this is a compatibility issue.
Try the attached patch, You can manually patch the installed amidxtaped
script.
Jean-Louis
Dennis Benndorf wrote:
Hello Jean-Louis,
dumps are normally compressed on client-side (but there are a few exceptions).
See attached files.
Regards,
Dennis
Original-Nachricht
Datum: Tue, 19 Apr 2011 08:00:45 -0400
Von: Jean-Louis Martineau martin...@zmanda.com
An: Dennis Benndorf dennis.bennd...@gmx.de
CC: amanda-users@amanda.org
Betreff: Re: amanda 3.3beta: amrecover fails because of decompression?
Do the dump are compressed on client or server?
Post the amrecover and amidxtaped debug files.
As a workaround, you can do the following in amrecover before the extract:
set property command-options -z
Jean-Louis
Dennis Benndorf wrote:
Hello,
after updating yesterday to 3.3beta amrecover shows:
on linuxhost dumped with tar
Extracting files using tape drive changer on host dl380-54.gbv.de.
Load tape D00070 now
Continue [?/Y/n/s/d]? Y
tar: Archive is compressed. Use -z option
tar: Error is not recoverable: exiting now
Extractor child exited with status 2
and solarishost dumped with star:
Extracting files using tape drive changer on host dl380-54.gbv.de.
Load tape D00059 now
Continue [?/Y/n/s/d]? Y
Restoring files into directory /tmp
All existing files in /tmp can be deleted
Continue [?/Y/n]? Y
/opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z
option.
Extractor child exited with status -1
Is there an option on client to enable decompression?
Regards,
Dennis
diff --git a/server-src/amidxtaped.pl b/server-src/amidxtaped.pl
index dfbea94..c156a00 100644
--- a/server-src/amidxtaped.pl
+++ b/server-src/amidxtaped.pl
@@ -570,7 +570,8 @@ sub xfer_src_cb {
$header-{'clntcompprog'} = '';
}
} else {
- if ($dle-{'compress'} == $Amanda::Config::COMP_SERVER_FAST ||
+ if (!$self-{'their_features'}-has($Amanda::Feature::fe_amrecover_receive_unfiltered) ||
+ $dle-{'compress'} == $Amanda::Config::COMP_SERVER_FAST ||
$dle-{'compress'} == $Amanda::Config::COMP_SERVER_BEST) {
push @filters,
Amanda::Xfer::Filter::Process-new(
Re: amanda 3.3beta: amrecover fails because of decompression?
Hello Jean-Louis, thanks for the patch, seems to work now! Regards, Dennis Original-Nachricht Datum: Tue, 19 Apr 2011 09:39:08 -0400 Von: Jean-Louis Martineau martin...@zmanda.com An: Dennis Benndorf dennis.bennd...@gmx.de CC: amanda-users@amanda.org Betreff: Re: amanda 3.3beta: amrecover fails because of decompression? amrecover is 3.1.1, this is a compatibility issue. Try the attached patch, You can manually patch the installed amidxtaped script. Jean-Louis Dennis Benndorf wrote: Hello Jean-Louis, dumps are normally compressed on client-side (but there are a few exceptions). See attached files. Regards, Dennis Original-Nachricht Datum: Tue, 19 Apr 2011 08:00:45 -0400 Von: Jean-Louis Martineau martin...@zmanda.com An: Dennis Benndorf dennis.bennd...@gmx.de CC: amanda-users@amanda.org Betreff: Re: amanda 3.3beta: amrecover fails because of decompression? Do the dump are compressed on client or server? Post the amrecover and amidxtaped debug files. As a workaround, you can do the following in amrecover before the extract: set property command-options -z Jean-Louis Dennis Benndorf wrote: Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone
amrecover fails
Running Ubuntu server 10.10 with Amanda 3.1.0 both new installs. Tried to
amrecover
for a test from a remote machine. The machines are connected with GbE. Here
is what
happened Any tips?
amrecover extract
Extracting files using tape drive changer on host rmt170.rmtohio.com.
The following tapes are needed: Daily08
Restoring files into directory /usr/home/jkonecn
Continue [?/Y/n]?
Extracting files using tape drive changer on host rmt170.rmtohio.com.
Load tape Daily08 now
Continue [?/Y/n/s/t]?
timeout waiting for restore
increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow
amrecover: error reading header (Operation timed out), check amidxtaped.*.debug
on server
amidxtaped.*.debug is 162MB but here is the start of it if it helps...
Wed Mar 2 16:04:50 2011: amidxtaped: pid 9974 ruid 34 euid 34 version 3.1.0:
start at Wed Mar 2 16:04:50 2011
Wed Mar 2 16:04:50 2011: amidxtaped: CTL FEATURES=feff9ffeff7f
Wed Mar 2 16:04:50 2011: amidxtaped: CTL CONFIG=Daily
Wed Mar 2 16:04:50 2011: amidxtaped: CTL LABEL=Daily08:2
Wed Mar 2 16:04:50 2011: amidxtaped: CTL FSF=2
Wed Mar 2 16:04:50 2011: amidxtaped: CTL HEADER
Wed Mar 2 16:04:50 2011: amidxtaped: CTL DEVICE=changer
Wed Mar 2 16:04:50 2011: amidxtaped: CTL HOST=^r4p17$
Wed Mar 2 16:04:50 2011: amidxtaped: CTL DISK=^/usr$
Wed Mar 2 16:04:50 2011: amidxtaped: CTL DATESTAMP=20110302075132
Wed Mar 2 16:04:50 2011: amidxtaped: CTL END
Wed Mar 2 16:04:50 2011: amidxtaped: pid 9974 ruid 34 euid 34 version 3.1.0:
rename at Wed Mar 2 16:04:50 2011
Wed Mar 2 16:04:50 2011: amidxtaped: ignoring specified DISK, as it may be
badly quoted
Warning: no log files found for tape Daily03 written 2011-03-01 13:29:28
Warning: no log files found for tape Daily02 written 2011-03-01 13:16:52
Warning: no log files found for tape Daily01 written 2011-03-01 13:11:48
Wed Mar 2 16:04:50 2011: amidxtaped: warning: Use of uninitialized value $part{status} in string eq at
/usr/lib/amanda/perl/Amanda/DB/Catalog.pm line 632.
Warning: no log files found for tape Daily03 written 2011-03-01 13:29:28
Warning: no log files found for tape Daily02 written 2011-03-01 13:16:52
Warning: no log files found for tape Daily01 written 2011-03-01 13:11:48
Wed Mar 2 16:04:51 2011: amidxtaped: warning: Use of uninitialized value $part{status} in string eq at
/usr/lib/amanda/perl/Amanda/DB/Catalog.pm line 632.
Wed Mar 2 16:04:53 2011: amidxtaped: warning: Use of uninitialized value $next_label in concatenation (.) or string at
/usr/lib/amanda/perl/Amanda/Recovery/Clerk.pm line 46
7.
Wed Mar 2 16:04:53 2011: amidxtaped: warning: Use of uninitialized value $label in concatenation (.) or string at
/usr/lib/amanda/perl/Amanda/Recovery/Scan.pm line 196.
Wed Mar 2 16:04:53 2011: amidxtaped: find_volume labeled ''
Wed Mar 2 16:04:54 2011: amidxtaped: warning: Use of uninitialized value $label in string eq at
/usr/lib/amanda/perl/Amanda/Recovery/Scan.pm line 259.
Wed Mar 2 16:04:54 2011: amidxtaped: warning: Use of uninitialized value $label in string eq at
/usr/lib/amanda/perl/Amanda/Recovery/Scan.pm line 259.
Wed Mar 2 16:04:54 2011: amidxtaped: warning: Use of uninitialized value $label in string eq at
/usr/lib/amanda/perl/Amanda/Recovery/Scan.pm line 259.
Wed Mar 2 16:04:54 2011: amidxtaped: warning: Use of uninitialized value $label in string eq at
/usr/lib/amanda/perl/Amanda/Recovery/Scan.pm line 259.
3.2.0: add command in amrecover fails on trailing slash of directory names
Hello, I did testings with 3.2.0 and discovered a problem in amrecover. In previous versions, I copy/pasted directory names to the 'add' command. This fails now, because 'add' doesn't accept the '/' at the end any more. If I type it without, it works.: amrecover ls 2010-10-21-21-00-02 test/ amrecover add test/ File test/ doesn't exist in directory amrecover add test Added dir /test/ at date 2010-10-16-21-00-02 The 'cd' command still allows the slash at the end like privious version. Regards, Marc -- Marc Muehlfeld (IT-Leiter) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amrecover fails
Timothy Ball schrieb: Please add the line CLIENT-BOX root amindexd amidxtaped to /var/lib/amanda/.amandahosts on the client on my server I have an .amandahosts file that looks like this: [EMAIL PROTECTED]:~$ cat .amandahosts localhost root amindexd amidxtaped localhost amandabackup amdump localhost.localdomain root amindexd amidxtaped localhost.localdomain amandabackup amdump CLIENT-BOXroot CLIENT-BOX root amindexd amidxtaped Did you really add CLIENT-BOX to .amandahosts? Or is this the name of your client you want to backup? This has to be the hostname of the client (with FQDN if the server has a different search-domain) you want to access amanda services on the server from. Also the line CLIENT-BOXroot should be removed. There are no services defined in the third column. localhost root amindexd amidxtaped localhost amandabackup amdump localhost.localdomain root amindexd amidxtaped localhost.localdomain amandabackup amdump Also, you don't need extra lines for localhost and localhost.localdomain. It's the same. The following is enough for backup and restore from/on the server: localhost root amindexd amidxtaped localhost amandabackup amdump Regards Marc -- Marc Muehlfeld (Leitung IT) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amrecover fails
Am Dienstag, den 21.10.2008, 16:49 -0400 schrieb Timothy Ball: Hi Timothy! [EMAIL PROTECTED]:~$ cat .amandahosts localhost root amindexd amidxtaped localhost amandabackup amdump localhost.localdomain root amindexd amidxtaped localhost.localdomain amandabackup amdump CLIENT-BOXroot CLIENT-BOX root amindexd amidxtaped Can you ping CLIENT-BOX? If you can't, you should add the server name to /etc/hosts. Maybe your backup server can't resolve CLIENT-BOX. -- Regards Thomas
Re: amrecover fails
On 30 Oct at 16:58 Paul Bijnens [EMAIL PROTECTED] wrote in
message [EMAIL PROTECTED]
[snip]
[EMAIL PROTECTED] recover]# amrecover HomeDumps -s tony-lx
AMRECOVER Version 2.5.1. Contacting server on tony-lx ...
NAK: amindexd: invalid service
amindexd appears to be running; it's certainly configured as per the
documentation in xinet.d.
There appears to be no mention of this in either the wiki or the faq.
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
Since 2.5.1 you need to add the services that amandad is allowed to run
in the server_args:
service amanda {
only_from = amandasrv.example.com amandaclnt.example.com
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
Thanks vey much, Paul; that fixed it! I simply didn't associate my error
message and that change.
A supplementary question for anyone who knows: Is it possible to ger
amrestore to preserve file ownership/permissions, instead of assigning
everything to root?
Cheers, Tony
--
Tony van der Hoff| mailto:[EMAIL PROTECTED]
Buckinghamshire, England
amrecover fails
I'm a long-time Amanda user, currently 2.5.1, under Mandriva 2007, and regularly perform backups; but have not needed to recover data for some while. Now I do :( I'm sure amrecover used to work, but may not have done since I upgraded to 2.5.1. Anyway: [EMAIL PROTECTED] recover]# amrecover HomeDumps -s tony-lx AMRECOVER Version 2.5.1. Contacting server on tony-lx ... NAK: amindexd: invalid service amindexd appears to be running; it's certainly configured as per the documentation in xinet.d. There appears to be no mention of this in either the wiki or the faq. Has anyone got any suggestions on what might be wrong, and on how to overcome this problem? Cheers, Tony -- Tony van der Hoff| mailto:[EMAIL PROTECTED] Buckinghamshire, England
Re: amrecover fails
Tony van der Hoff wrote:
I'm a long-time Amanda user, currently 2.5.1, under Mandriva 2007, and
regularly perform backups; but have not needed to recover data for some
while. Now I do :(
I'm sure amrecover used to work, but may not have done since I upgraded to
2.5.1. Anyway:
[EMAIL PROTECTED] recover]# amrecover HomeDumps -s tony-lx
AMRECOVER Version 2.5.1. Contacting server on tony-lx ...
NAK: amindexd: invalid service
amindexd appears to be running; it's certainly configured as per the
documentation in xinet.d.
There appears to be no mention of this in either the wiki or the faq.
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
Since 2.5.1 you need to add the services that amandad is allowed to
run in the server_args:
service amanda
{
only_from = amandasrv.example.com amandaclnt.example.com
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
}
Has anyone got any suggestions on what might be wrong, and on how to
overcome this problem?
Re: amrecover fails with unknown error
Karsten, Did you get an amidxtaped debug fileson the server? What did it contains? Did amidxtaped configured correctly in xinetd? Any xinetd log? Jean-Louis Karsten Fuhrmann wrote: Hello List, i have a serious situation here, i can not recover anything from my backups anymore. I am using version 2.5.0p2 on FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE #0: SMP i386 amrecover always exits with 'Could not read from control socket: Unknown error: 0' Does anybody have an idea what is going on here ? This is a log file from an amrecover run [EMAIL PROTECTED] /tmp/amanda]# more amrecover.20070325205302.debug amrecover: debug 1 pid 11917 ruid 0 euid 0: start at Sun Mar 25 20:53:02 2007 amrecover: bind_portrange2: trying port=923 amrecover: stream_client_privileged: connected to 192.168.1.1.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.923 ... amrecover: bind_portrange2: trying port=991 amrecover: stream_client_privileged: connected to 192.168.1.1.10083 amrecover: stream_client_privileged: our side is 0.0.0.0.991 amrecover: try_socksize: receive buffer size is 65536 amrecover: Could not read from control socket: Unknown error: 0 amrecover: pid 11917 finish time Sun Mar 25 20:54:09 2007
Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
David Trusty wrote: Hi, I checked the logs. There is no error message, and I have no cron running either. I can duplicate the problem every time. Is it always at the same place (part 51)? Could you provide the LABEL= line from the amidxtaped.*.debug file? What is the output of `amadmin config find helix /mnt/dataa/invention`? I want to know if the part 51 should be read from the same tape or the next tape. Jean-Louis Interestingly, the amrecover says that it will need two tapes. When I put the first tape in, it reads it for a long time, gets the error I noted below, and then just gives up on asking for the second tape. Any other ideas? Thanks, David From: Ian Turner [EMAIL PROTECTED] To: David Trusty [EMAIL PROTECTED] CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive Date: Mon, 25 Sep 2006 14:27:19 -0400 The device or resource busy message comes from your operating system. Normally this error means that two programs tried to access the tape device simultaneously. I suspect one of the following: 1) A hardware problem or kernel bug. Check your kernel debug logs. 2) A cron job that accesses the tape. Check your cron log. --Ian On Friday 22 September 2006 19:21, David Trusty wrote: Hi, I am trying to restore a file which is on a backup which used tape spanning. I am running version 2.5.1. The backup says it completed successfully, but I get the errors below from amrecover and imidxtaped. Any ideas? Thanks!! David amrecover output Looking for tape 104... tar: Read 8192 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Extractor child exited with status 2 debug log for amidxtaped ~~~ midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: restore read error: Device or resource busy amidxtaped: time 2988.892: restore read error: Device or resource busy amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006 -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
Date: Tue, 26 Sep 2006 07:47:48 -0400 David Trusty wrote: Hi, I checked the logs. There is no error message, and I have no cron running either. I can duplicate the problem every time. Is it always at the same place (part 51)? Yes. Could you provide the LABEL= line from the amidxtaped.*.debug file? amidxtaped: time 0.053: LABEL=104:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175;105:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56 From: Jean-Louis Martineau [EMAIL PROTECTED] To: David Trusty [EMAIL PROTECTED] CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive What is the output of `amadmin config find helix /mnt/dataa/invention`? I want to know if the part 51 should be read from the same tape or the next tape. Jean-Louis Interestingly, the amrecover says that it will need two tapes. When I put the first tape in, it reads it for a long time, gets the error I noted below, and then just gives up on asking for the second tape. Any other ideas? Thanks, David From: Ian Turner [EMAIL PROTECTED] To: David Trusty [EMAIL PROTECTED] CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive Date: Mon, 25 Sep 2006 14:27:19 -0400 The device or resource busy message comes from your operating system. Normally this error means that two programs tried to access the tape device simultaneously. I suspect one of the following: 1) A hardware problem or kernel bug. Check your kernel debug logs. 2) A cron job that accesses the tape. Check your cron log. --Ian On Friday 22 September 2006 19:21, David Trusty wrote: Hi, I am trying to restore a file which is on a backup which used tape spanning. I am running version 2.5.1. The backup says it completed successfully, but I get the errors below from amrecover and imidxtaped. Any ideas? Thanks!! David amrecover output Looking for tape 104... tar: Read 8192 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Extractor child exited with status 2 debug log for amidxtaped ~~~ midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: restore read error: Device or resource busy amidxtaped: time 2988.892: restore read error: Device or resource busy amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006 -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
Hi, I checked the logs. There is no error message, and I have no cron running either. I can duplicate the problem every time. Interestingly, the amrecover says that it will need two tapes. When I put the first tape in, it reads it for a long time, gets the error I noted below, and then just gives up on asking for the second tape. Any other ideas? Thanks, David From: Ian Turner [EMAIL PROTECTED] To: David Trusty [EMAIL PROTECTED] CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive Date: Mon, 25 Sep 2006 14:27:19 -0400 The device or resource busy message comes from your operating system. Normally this error means that two programs tried to access the tape device simultaneously. I suspect one of the following: 1) A hardware problem or kernel bug. Check your kernel debug logs. 2) A cron job that accesses the tape. Check your cron log. --Ian On Friday 22 September 2006 19:21, David Trusty wrote: Hi, I am trying to restore a file which is on a backup which used tape spanning. I am running version 2.5.1. The backup says it completed successfully, but I get the errors below from amrecover and imidxtaped. Any ideas? Thanks!! David amrecover output Looking for tape 104... tar: Read 8192 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Extractor child exited with status 2 debug log for amidxtaped ~~~ midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: restore read error: Device or resource busy amidxtaped: time 2988.892: restore read error: Device or resource busy amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006 -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Amrecover fails when using tape spanning: Unexpected EOF in archive
Hi, I am trying to restore a file which is on a backup which used tape spanning. I am running version 2.5.1. The backup says it completed successfully, but I get the errors below from amrecover and imidxtaped. Any ideas? Thanks!! David amrecover output Looking for tape 104... tar: Read 8192 bytes from - tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Extractor child exited with status 2 debug log for amidxtaped ~~~ midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar amidxtaped: restore read error: Device or resource busy amidxtaped: time 2988.892: restore read error: Device or resource busy amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006
amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service
Hi, I just installed release 2.5.1 on a SUSE 10.1 machine. I was able to do a backup fine, but when I try to run amrecover, I get this error: # amrecover Monthly AMRECOVER Version 2.5.1. Contacting server on localhost ... NAK: amindexd: invalid service The amcheck command shows no errors. Any ideas? Thanks, David
RE: amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service
David Trusty [EMAIL PROTECTED] said: I just installed release 2.5.1 on a SUSE 10.1 machine. I was able to do a backup fine, but when I try to run amrecover, I get this error: # amrecover Monthly AMRECOVER Version 2.5.1. Contacting server on localhost ... NAK: amindexd: invalid service The amcheck command shows no errors. Any ideas? In Amanda 2.5.1, amrecover uses Security API. Changes to xinetd configuration is required. Please see the following wiki page for detail: http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
Re: amrecover fails in rel 2.5.1 with NAK: amindexd: invalid service
David Trusty wrote: Hi, I just installed release 2.5.1 on a SUSE 10.1 machine. I was able to do a backup fine, but when I try to run amrecover, I get this error: # amrecover Monthly AMRECOVER Version 2.5.1. Contacting server on localhost ... NAK: amindexd: invalid service Do you have the amindexd service configured in (x)inetd? Does it show up in a 'netstat -l' ? The amcheck command shows no errors. amcheck only checks to see if backups would work, not restores, so it won't tell you if index or tape services are available. Any ideas? See above. Also, not related to your current problem, you should look in the list archives for threads on how using 'localhost' in your disklist can cause problems later on. Frank Thanks, David -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
amrecover fails with stream_client_privileged Connection refused
Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused cat amrecover.20050719094728.debug amrecover: debug 1 pid 2019 ruid 0 euid 0: start at Tue Jul 19 09:47:28 2005 amrecover: stream_client_privileged: connect to 127.0.0.1.10082 failed: Connection refused amrecover: cannot connect to localhost: Connection refused amrecover: pid 2019 finish time Tue Jul 19 09:47:28 2005
Re: amrecover fails with stream_client_privileged Connection refused
[EMAIL PROTECTED] wrote: Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the Root??? Shouldn't that be user ~amanda/.amandahosts. localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused localhost??? try amrecover -t the.amanda.server -s the.amanda.server Now it's Stefan's turn to point to the FAQ about localhost again. -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amrecover fails with stream_client_privileged Connection refused
[EMAIL PROTECTED] wrote: Hi. I'd installed amanda a short time ago. Backups are working fine, however now I'm testing the recover and I'm not able to get the server to access itself. I've changed the user in /root/.amandahosts, commented out the localhost entry as well. And played with ownershop of amandaidx. All to no avail. # amrecover CCC AMRECOVER Version 2.4.4p1. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused cat amrecover.20050719094728.debug amrecover: debug 1 pid 2019 ruid 0 euid 0: start at Tue Jul 19 09:47:28 2005 amrecover: stream_client_privileged: connect to 127.0.0.1.10082 failed: Connection refused amrecover: cannot connect to localhost: Connection refused amrecover: pid 2019 finish time Tue Jul 19 09:47:28 2005 Would you please read the FAQ and/or the docs first? www.amanda.org Thanks, Stefan. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
amrecover fails *again*
No one answered my first post. So here's a brief reminder. -- I use NTBACKUP to copy the entire 'Documents and Settings' directory on the Windows PC to a file. This file may be as large as 2 Gigabytes (almost, but not quite). Amanda copies the files OK and amverify can read all the files successfully. However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Bad file descriptor extract_list - child returned non-zero status:1 Continue? [Y/n]: amrecover - I can restore the files with native Unix utilities (mt, dd and tar) below is a step by step method of how I do this, but I would like for amrecover to be able to restore these files... Any suggestions? 1. mt -f /dev/nst0 rewind 2. cd to /scratch2/ftp_root 3. mt -f /dev/nst0 fsf 1 4. dd if=/dev/nst0 bs=32k count=1 5. repeat 3 4 until finding the header that I would like to restore. 6. once finding the correct header I do this: dd if=/dev/nst0 bs=32k | /bin/tar -xvf -
Re: amrecover fails *again*
As the message says: increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow That's the only solution, you must recompile amanda. Jean-Louis On Wed, Nov 20, 2002 at 11:28:41AM -0500, Richard B. Tilley (Brad) wrote: No one answered my first post. So here's a brief reminder. -- I use NTBACKUP to copy the entire 'Documents and Settings' directory on the Windows PC to a file. This file may be as large as 2 Gigabytes (almost, but not quite). Amanda copies the files OK and amverify can read all the files successfully. However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Bad file descriptor extract_list - child returned non-zero status:1 Continue? [Y/n]: amrecover - I can restore the files with native Unix utilities (mt, dd and tar) below is a step by step method of how I do this, but I would like for amrecover to be able to restore these files... Any suggestions? 1. mt -f /dev/nst0 rewind 2. cd to /scratch2/ftp_root 3. mt -f /dev/nst0 fsf 1 4. dd if=/dev/nst0 bs=32k count=1 5. repeat 3 4 until finding the header that I would like to restore. 6. once finding the correct header I do this: dd if=/dev/nst0 bs=32k | /bin/tar -xvf - -- 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 fails *again*
On Wed, Nov 20, 2002 at 11:28:41AM -0500, Richard B. Tilley (Brad) wrote: No one answered my first post. So here's a brief reminder. [ snip ] However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow [ snip ] ... , but I would like for amrecover to be able to restore these files... Any suggestions? Did you try what the message suggests? That is generally a good first attempt. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover fails *again*
Thanks for the smart response. I'll just stick with my manual method of restoring as I don't have time to change a src file (that I don't currently have) and recompile. Besides, my method works... it's amanda's method that doesn't work, but no one seems to care about that. Read The Fucking Manual punk. My balls are bigger than yours punk so don't bother me. Do what the error message says dog-breath before I squash you with my 64-bit souped-up, compiled the compiler ... yadah yadah yadah Now, I wonder why Open Source and Free Software aren't more main stream? On Wednesday 20 November 2002 03:27 pm, Jon LaBadie wrote: Did you try what the message suggests? That is generally a good first attempt.
Re: amrecover fails *again*
On Wednesday 20 November 2002 16:23, Richard B. Tilley (Brad) wrote: Thanks for the smart response. I'll just stick with my manual method of restoring as I don't have time to change a src file (that I don't currently have) and recompile. Besides, my method works... it's amanda's method that doesn't work, but no one seems to care about that. First off, Jon was being nice IMO, and the chances are very, very good that what he wrote will indeed fix your problem. FYI, probably 98% of the amanda users on this list DO build from source, and that source is about 5 minutes away on a 56k line, see the link that leads of Jean-Louis's page on a umontreal.ca machine, on http://www.amanda.org quite a ways down the page. He keeps the most recent snapshots all tar-balled up and ready to go. However, I've observed that probably 25% of the messages here were generated by someone who downloaded a set of rpms of amanda someplace, and they may, or may not have been, compiled with the same options one normally uses when compiling amanda. That BTW, is about a 3 minute job on this 1400mhz athlon. You can't install the rpms using your favorite gui much faster than that. Read The Fucking Manual punk. My balls are bigger than yours punk so don't bother me. Do what the error message says dog-breath before I squash you with my 64-bit souped-up, compiled the compiler ... yadah yadah yadah Oh, my. Does your mother know you use such language? If she does know, I'd wager she isn't the least bit proud of it. One should always keep in mind that old adage that says 'its not the size of the dog in the fight, its the size of the fight in the dog that counts'. Now, I wonder why Open Source and Free Software aren't more main stream? With an attitude like what you are displaying here, how did you ever get yourself convinced you should even try anything with an opensource label on it? To me, thats the 64k$ question. Opensource is an attitude, and you obviously don't have it. Opensource is a willingness to dig in and fix it if your are capable of it when its not running to your likeing. If you aren't capable of it, then at least give the instructions offered a chance to fix the problem before you come in here and bad-mouth someone who is honestly trying to help. Who knows, while walking around in the code looking for where Jon said to increase that timeout, you might actually (heaven forbid) learn something! Or have you, with a fresh sheepskin on the wall, now decided you know it all? Funny thing, a holder of a very prestigious sheepskin, and publisher of a rag pretty much delegated to the embedded scene once told me that at the end of the day, the most important sheepskin was the one you slept on. Opensource is a mailing list such as this, where you can ask questions, and get answers within hours, sometimes minutes, and certainly 6 months faster that you can from Redmond, and do it without having to pony up another $200 for the latest upgrade to their bugfarm. Opensource is the willingness to share with any and all, the fruits of the work you do simply because you're proud of your work, thereby making the whole scene a better place to live. On Wednesday 20 November 2002 03:27 pm, Jon LaBadie wrote: Did you try what the message suggests? That is generally a good first attempt. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
amrecover fails
Hello, I have some very large backup files that amanda pulls from Windows 2000 PCs. I use ntbackup to copy the entire 'Documents and Settings' directory on the Windows PC to a file. This file may be as large as 2 Gigabytes. Amanda copies the files OK and amverify can read all the files successfully. However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Bad file descriptor extract_list - child returned non-zero status:1 Continue? [Y/n]: amrecover Is there a way to correct this? I use RH 7.3 and amanda 2.4.2p2 that came with the distro. Amrecover has no problem restoring the smaller files (400 - 600 MB), it's just the largest files that fail. My tape drives are Quantum DLT 4000. Any help would be much appreciated. Thanks, Brad
amrecover fails on client
Hi, when extracting files from a backup on a client using amrecover I get the following error message: amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 Using amrecover on the server works fine. Any hints what might go wrong?!? Configuration: Server: Linux, amanda 2.4.2p1 Client: Linux, amanda 2.4.2p1 Any information missing? Just ask, I'll provide them... Thank you, Christina Rossmanith
