Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Rex CPAN distribution.

Report information
The Basics
Id: 81970
Status: resolved
Priority: 0/
Queue: Rex

People
Owner: Nobody in particular
Requestors: justsomehacker [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Issue with POD for Rex.pm
Date: Thu, 13 Dec 2012 22:39:39 -0800
To: bug-Rex [...] rt.cpan.org
From: Justin Hacker <justsomehacker [...] gmail.com>
When I fill-in my own values for the 'use Rex as a library' example on http://search.cpan.org/~jfried/Rex-0.31.5/lib/Rex.pm -- something similar to the following: use Rex; use Rex::Commands::Run; use Rex::Commands::Fs; Rex::connect( server => "myawsinstance", user => "root", # password => "(not needed)", private_key => "/path/to/my/private/key/file.pem", public_key => "/path/to/my/public/key/file.pub", ); if (is_file("/foo/bar")) { print "Do something...\n"; } my $output = run("uptime"); I get errors similar to this: $ ./example.pl [2012-12-13 21:42:26] INFO - Connecting to awsinstance:22 (root) [2012-12-13 21:42:26] INFO - Connected to awsinstance, trying to authenticate. Use of uninitialized value $auth_type in string eq at /usr/share/perl5/Rex/Interface/Connection/SSH.pm line 80. Use of uninitialized value $auth_type in string eq at /usr/share/perl5/Rex/Interface/Connection/SSH.pm line 84. Use of uninitialized value in subroutine entry at /usr/lib/perl5/Net/SSH2.pm line 351. Use of uninitialized value in subroutine entry at /usr/lib/perl5/Net/SSH2.pm line 351. [2012-12-13 21:42:28] WARN - Wrong username or password. Or wrong key. Wrong username or password. Or wrong key. at /usr/share/perl5/Rex.pm line 280. I believe this is a documentation issue, as other simple Rex examples work fine. Note: I've installed (R)?ex 0.34.1 & I'm running Perl v5.14.2 on Ubuntu Precise. Wouldn't have otherwise filed a bug for this, but 3 of my postings to the Rex google group were immediately deleted. Regards, Justin
Fixed in 0.34.2