RE: amrecover fails with TypeError in method 'debug'...

2012-04-30 Thread Kervin L. Pierre
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 




Device type s3 is not known

2012-04-30 Thread Kervin L. Pierre
After building from trunk to fix a few other issues, I started configuring 
Amazon S3 support.  

But amlabel reported...
Device type s3 is not known

Similar to this issue...
https://forums.zmanda.com/archive/index.php/t-2581.html

To fix this I did...

make distclean
yum install libcurl-devel perl-WWW-Curl
./configure --enable-s3-device
make

I believe part of the underlying issue is that the autoconf tests do not seem 
to warn about missing headers like libcurl, etc.

Best regards,
Kervin


Adevsoft Inc
Business Software Development
http://adevsoft.com/