Re: amrecover - can't talk to tape server: service amidxtaped:

2011-09-05 Thread Gour-Gadadhara Dasa
On Fri, 17 Jun 2011 15:26:21 -0400
Jean-Louis Martineau martin...@zmanda.com wrote:

 perl 5.14 is more restrictive in the syntax.
 
 I committed the attached patch to the 3.2 branch.

After returning back to (Arch)Linux from (Free)BSD I had the same issue
which was resolved by upgrading to the trunk..

Thank you for support.


Sincerely,
Gour

-- 
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810




-- 
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810




signature.asc
Description: PGP signature


Re: amrecover - can't talk to tape server: service amidxtaped:

2011-06-17 Thread Jean-Louis Martineau

Hi Toomas,

perl 5.14 is more restrictive in the syntax.

I committed the attached patch to the 3.2 branch.

Jean-Louis

Toomas Aas wrote:

Hello!

I'm installing a new Amanda server on FreeBSD 8.2, using FreeBSD ports 
which currently provide Amanda 3.2.2. I have successfully made the 
first backup, but restore fails:

--
amrecover add dnetc-freebsd8-amd64.tar.gz
Added file /home/toomas/dnetc-freebsd8-amd64.tar.gz
amrecover extract

Extracting files from holding disk on host pegasus.raad.tartu.ee.
The following files are needed: 
/holding/20110615162722/pegasus.raad.tartu.ee._usr.0


Extracting from file  
/holding/20110615162722/pegasus.raad.tartu.ee._usr.0

amrecover - can't talk to tape server: service amidxtaped:
--

And the file is not extracted. Only errors I could find are in 
amandad.debug, which are actually Perl warnings:


Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:
Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped: ** 
(process:5181): WARNING **: Use of qw(...) as parentheses is 
deprecated at 
/usr/local/lib/perl5/site_perl/5.14.0/Amanda/Recovery/Clerk.pm line 231.

Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:
Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:

Such warnings are reported multiple times about various locations in 
Clerk.pm and Planner.pm:


Clerk.pm line 231
Clerk.pm line 265
Planner.pm line 231
Planner.pm line 342
Planner.pm line 393

I modified all these occurrences, adding additional parentheses around 
the qw() construct, for example


original:

 for my $rq_param qw(dump xfer_src_cb) {

new:

 for my $rq_param (qw(dump xfer_src_cb)) {

After that, I could run recovery successfully.

As I am not a Perl programmer and don't really know what it is I did, 
I wonder if this is a safe workaround?




Index: ChangeLog
===
--- ChangeLog	(revision 4171)
+++ ChangeLog	(revision 4173)
@@ -1,3 +1,8 @@
+2011-06-17  Jean-Louis Martineau martin...@zmanda.com
+	* perl/Amanda/Changer/robot.pm, perl/Amanda/Recovery/Planner.pm,
+	  perl/Amanda/Recovery/Clerk.pm,
+	  perl/Amanda/Taper/Scribe.pm: Fix for qw syntax in perl 5.14.
+
 2011-06-13  Jean-Louis Martineau martin...@zmanda.com
 	* perl/Amanda/Taper/Worker.pm: s/messsage/message/.
 
Index: perl/Amanda/Changer/robot.pm
===
--- perl/Amanda/Changer/robot.pm	(revision 4171)
+++ perl/Amanda/Changer/robot.pm	(revision 4173)
@@ -266,7 +266,7 @@
 }
 
 # status-interval, eject-delay, unload-delay
-for my $propname qw(status-interval eject-delay unload-delay) {
+for my $propname (qw(status-interval eject-delay unload-delay)) {
 	next unless exists $config-{'properties'}-{$propname};
 	if (@{$config-{'properties'}-{$propname}-{'values'}}  1) {
 	return Amanda::Changer-make_error(fatal, undef,
Index: perl/Amanda/Recovery/Planner.pm
===
--- perl/Amanda/Recovery/Planner.pm	(revision 4171)
+++ perl/Amanda/Recovery/Planner.pm	(revision 4173)
@@ -228,7 +228,7 @@
 my $self = shift;
 my %params = @_;
 
-for my $rq_param qw(changer plan_cb dumpspecs) {
+for my $rq_param (qw(changer plan_cb dumpspecs)) {
 	croak required parameter '$rq_param' mising
 	unless exists $params{$rq_param};
 }
@@ -339,7 +339,7 @@
 my $self = shift;
 my %params = @_;
 
-for my $rq_param qw(holding_file plan_cb) {
+for my $rq_param (qw(holding_file plan_cb)) {
 	croak required parameter '$rq_param' mising
 	unless exists $params{$rq_param};
 }
@@ -390,7 +390,7 @@
 my $self = shift;
 my %params = @_;
 
-for my $rq_param qw(filelist plan_cb) {
+for my $rq_param (qw(filelist plan_cb)) {
 	croak required parameter '$rq_param' mising
 	unless exists $params{$rq_param};
 }
Index: perl/Amanda/Recovery/Clerk.pm
===
--- perl/Amanda/Recovery/Clerk.pm	(revision 4171)
+++ perl/Amanda/Recovery/Clerk.pm	(revision 4173)
@@ -228,7 +228,7 @@
 my $self = shift;
 my %params = @_;
 
-for my $rq_param qw(dump xfer_src_cb) {
+for my $rq_param (qw(dump xfer_src_cb)) {
 	croak required parameter '$rq_param' missing
 	unless exists $params{$rq_param};
 }
@@ -262,7 +262,7 @@
 my %params = @_;
 
 $self-dbg(starting recovery);
-for my $rq_param qw(xfer recovery_cb) {
+for my $rq_param (qw(xfer recovery_cb)) {
 	croak required parameter '$rq_param' missing
 	unless exists $params{$rq_param};
 }
Index: perl/Amanda/Taper/Scribe.pm
===
--- perl/Amanda/Taper/Scribe.pm	(revision 4171)
+++ perl/Amanda/Taper/Scribe.pm	(revision 4173)
@@ -442,7 +442,7 @@
 my %params = @_;
 
 my

amrecover - can't talk to tape server: service amidxtaped:

2011-06-16 Thread Toomas Aas

Hello!

I'm installing a new Amanda server on FreeBSD 8.2, using FreeBSD ports  
which currently provide Amanda 3.2.2. I have successfully made the  
first backup, but restore fails:

--
amrecover add dnetc-freebsd8-amd64.tar.gz
Added file /home/toomas/dnetc-freebsd8-amd64.tar.gz
amrecover extract

Extracting files from holding disk on host pegasus.raad.tartu.ee.
The following files are needed:  
/holding/20110615162722/pegasus.raad.tartu.ee._usr.0


Extracting from file  /holding/20110615162722/pegasus.raad.tartu.ee._usr.0
amrecover - can't talk to tape server: service amidxtaped:
--

And the file is not extracted. Only errors I could find are in  
amandad.debug, which are actually Perl warnings:


Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:
Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped: **  
(process:5181): WARNING **: Use of qw(...) as parentheses is  
deprecated at  
/usr/local/lib/perl5/site_perl/5.14.0/Amanda/Recovery/Clerk.pm line 231.

Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:
Thu Jun 16 16:04:36 2011: amandad: ERROR service amidxtaped:

Such warnings are reported multiple times about various locations in  
Clerk.pm and Planner.pm:


Clerk.pm line 231
Clerk.pm line 265
Planner.pm line 231
Planner.pm line 342
Planner.pm line 393

I modified all these occurrences, adding additional parentheses around  
the qw() construct, for example


original:

 for my $rq_param qw(dump xfer_src_cb) {

new:

 for my $rq_param (qw(dump xfer_src_cb)) {

After that, I could run recovery successfully.

As I am not a Perl programmer and don't really know what it is I did,  
I wonder if this is a safe workaround?


--
Toomas Aas


amrecover - can't talk to tape server

2002-08-16 Thread Jason Greenberg

Any idea what could cause this?  the same thing happens when connecting
from the tape server (local or remote).

amrecover add passwd
Added /passwd
amrecover extract

Extracting files using tape drive /dev/nst0 on host 192.168.100.1
The following tapes are needed: E04

Restoring files into directory /home/jg/recover-tmp
Continue? [Y/n]: y

Load tape E04 now
Continue? [Y/n]: y
cannot connect to 192.168.100.1: Connection refused
amrecover - can't talk to tape server



-- 
Jay




Re: amrecover - can't talk to tape server

2002-08-16 Thread Frank Smith

Does your inetd.conf (or equivalent) have an entry for amidxtape?  You'll need
one for amandaidx to if it is also your index server.

Frank

--On Friday, August 16, 2002 12:33:54 -0400 Jason Greenberg [EMAIL PROTECTED] wrote:

 Any idea what could cause this?  the same thing happens when connecting
 from the tape server (local or remote).

 amrecover add passwd
 Added /passwd
 amrecover extract

 Extracting files using tape drive /dev/nst0 on host 192.168.100.1
 The following tapes are needed: E04

 Restoring files into directory /home/jg/recover-tmp
 Continue? [Y/n]: y

 Load tape E04 now
 Continue? [Y/n]: y
 cannot connect to 192.168.100.1: Connection refused
 amrecover - can't talk to tape server



 --
 Jay



--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501



Re: amrecover - can't talk to tape server

2002-08-16 Thread Jason Greenberg

That does it, thanks a lot !

On Fri, 2002-08-16 at 13:01, Frank Smith wrote:
 Does your inetd.conf (or equivalent) have an entry for amidxtape?  You'll need
 one for amandaidx to if it is also your index server.
 
 Frank
 
 --On Friday, August 16, 2002 12:33:54 -0400 Jason Greenberg [EMAIL PROTECTED] wrote:
 
  Any idea what could cause this?  the same thing happens when connecting
  from the tape server (local or remote).
 
  amrecover add passwd
  Added /passwd
  amrecover extract
 
  Extracting files using tape drive /dev/nst0 on host 192.168.100.1
  The following tapes are needed: E04
 
  Restoring files into directory /home/jg/recover-tmp
  Continue? [Y/n]: y
 
  Load tape E04 now
  Continue? [Y/n]: y
  cannot connect to 192.168.100.1: Connection refused
  amrecover - can't talk to tape server
 
 
 
  --
  Jay
 
 
 
 --
 Frank Smith[EMAIL PROTECTED]
 Systems Administrator Voice: 512-374-4673
 Hoover's Online Fax: 512-374-4501
 
-- 
Jason Greenberg, CCNP
Network Administrator
Execulink, Inc.
[EMAIL PROTECTED]




amrecover - can't talk to tape server

2001-10-03 Thread Warren Flemmer

Grettings

I am getting the following error with amrecover from a client
with a masq firewall between them:
amrecover - can't talk to tape server
(this comes up after the extract command)

Both client and server are 2.4.2p2 (Server RH6.2, Client RH7.0)

amcheck and amdump are working correctly and amrecover does work
on the server.

The client was build using:
./configure --with-user=operator --with-group=disk --without-server

The server was built using:
./configure --with-user=amanda --with-group=disk

In Msg# 30749 (Jun 29, 2001  ) John R. Jackson wrote:
In addition, you'll need to set up your firewall/NAT to let both ranges
of ports through as is.
However, there is a bug in 2.4.2p2 that will cause amrecover to fail
in the above setup.  I'm working on a fix for that.
Link: http://groups.yahoo.com/group/amanda-users/message/30749

Am I up against this bug? 
Is there a fix/patch for it? 
What ports are not connecting causing this error?
Do I need to build the client with server support?
Any other ideas?

Regards