#!/usr/bin/perl
use warnings;
use strict;
use Net::SSH2;

my $ssh2 = Net::SSH2->new();
$ssh2->connect('localhost') or die "Unable to connect Host $@ \n";
$ssh2->auth_password('z','ztester') or die "Unable to login $@ \n";

#get a large file like a 100Meg wav file
my $dir = '/home/whoever';
my $remote1 = $dir.'/1.wav';
use IO::File;
my $local1 = IO::File->new("> 2.wav"); #it needs a blessed reference
$ssh2->scp_get($remote1, $local1);

__END__

[download]

Hello Zentara,
I have not tried using Net::SSH2, but interested in learning what considerations one should go through when deciding to use SSH2 vs. SFTP. (as I am still very new to using Perl and open source... I find very hard to navigate)

Hi, Net::SSH2 was designed to replace the old sftp and ssh module. You can ask the SSH experts on the maillist at ssh-sftp-perl maillist for all the details. The switch started about 10 years ago, and at the time the most important reason was to eliminate the numerous math library dependencies , like Math::Pari which was an installation hassle, and often resulted in sftp dropping back to very slow pure Perl math processing. It also brought all of the various ssh utilities, like sftp, scp, ssh under one module. I've found it easy to install and use, as it only requires libssh2 to be installed with it's development headers.

---

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

1. A code fragment showing what you're doing might be helpful
2. You don't list the SSH command/version that you're using
3. The latest version of Net::Sftp::Foreign is 1.74, and it looks like it should work with 5.8.8
4. Are both client and server Solaris 5.9?
5. I'm not sure what you're referring to by 'SFTP v 1.35'. Your client is your perl program. Is this the server version? There are lots of different servers around. Most also create log files
6. Can you use the sftp client on the command line to reliably transfer the file?
7. tcpdump/wireshark of a hanging transfer can at least tell you what's crapping out at the tcp level

fnord

fnord / Illuminatus,

2. "ssh -V" shows: Sun_SSH_1.1.1, SSH protocols 1.5/2.0, OpenSSL

3. Good to know!!

4. DataONTAP (NetApp OS)

5. I initially looked at the version of the SFTP.pm, so I just put it in here. Prolly extra info...

6. Yes, and one thing I forgot to mention is if I re-run the job, the sftp will go through. It also worked completely fine when ran daily on our test server. But also the same symptom on our dev box... (almost seems like it's only the first connection of the day, or maybe within 24hrs of last connection but it sounds ridiculous and I have no proof...)

7. I wouldn't know how to do that, or if I can. Since, I'm in a corporation and peons don't have access to anything, much less production. I'm just not sure. I mean, for us, in order to install a new Perl module it's 2 layers removed and we HOPE we get a knowledgeable SA...

my $ssherr = File::Temp->new or die "File::Temp->new failed";

open my $stderr_save, '>&STDERR' or die "unable to dump STDERR";
open STDERR, '>&'.fileno($ssherr);

my $sftp = Net::SFTP::Foreign->new(
host => $properties{RemoteHostName},
user => $rmtUser, password => $rmtPass
, timeout => 10, more=> '-v'
, queue_size => 16);

open STDERR, '>&'.fileno($stderr_save);

if ($sftp->error) {
   print "sftp error: ".$sftp->error."\n";
   seek($ssherr, 0, 0);
   while (<$ssherr>) {
      print "captured stderr: $_";
   }
   $endprogram = 1;
}

close $ssherr;

if ($endprogram) { exit($endprogram); }

if (!$sftp->setcwd($properties{RemoteDirPath})) {
   print "File Transfer - unable to change directory: " 
   . $sftp->error;
   exit(1);
}
if (!$sftp->get($properties{RemoteFileName}, "$fileTo")) {
   print "File Transfer - get failed: " . $sftp->error;
   exit(1);
}
[download]

BTW, which SSH client are you using, the one from Solaris or OpenSSH one and which version? I would try changing it.

Net::SFTP::Foreign supports timeouts and resuming transfers. You can combine these features as a workaround until we find what is going wrong.

Hi Salva,

Getting a dump from a failed run will be tricky. As it seems to only fail the first run of the day. I will try to get it.

"ssh -V" shows: Sun_SSH_1.1.1, SSH protocols 1.5/2.0, OpenSSL
I'm not sure what you mean by changing it or that I have any power to(?)

PS. Just want to say kudos because I can see you actively answer user questions.

As it seems to only fail the first run of the day

Then, you must investigate what happens at that time of the day that is different than when it runs properly.

It may be a problem related to the network, some firewall being rebooted every day at some time early on the morning or whatever. If you can run tcpdump on the machine, you may be able to discover what is happening with the connection at the TCP level.

I'm not sure what you mean by changing it or that I have any power to(?)

If you can, install OpenSSH on the machine and tell Net::SFTP::Foreign to use it instead of the SSH client from Solaris, just to see if it makes a difference.

Hello, not sure how to email you (can you PM me your email address?). Thanks!

CPAN authors can usually be reached via CPANID@cpan.org. In my case, salva@cpan.org.

which is... last unless $len = $data->read($buf, $blksize);

Maybe it's a clue?

Yes, investigate what happens in your network every day at that time!!!