Re^2: Net::SSH2 Interactive command example

Could you show us your code. I've done a lot of development this last year using this module. I believe I used 'shell' when sending commands over the established channel. I don't recall it closing the channel but it's been awhile since I've written code with this module.

I recall having a lot of problems with STDERR and this module. Is this what you are having difficulty with? From the channel module page it says:

shell

Start a shell on the remote host; calls process("shell").

exec ( command )

Execute the command on the remote host; calls process("exec", command). Note that only one of these requests can succeed per channel (cp. "exec" in perlfunc); if you want to run a series of commands, consider using shell instead.

I recommend 'shell'. It worked well for me. Post the code and we'll check it out.

BTW, while this module is still immature IMO (not even at 1.0 I think). David has done a fantastic job and it's far better than the original NET::SSH::PERL IMO. I've been able to hit a couple hundred Unix/Linux servers in a few minutes and run inventory reports. It's very speedy and does a great job. We're now using it to create user accounts and set passwords in minutes rather than days.

Yeah it's archaic but we can't decide how to tie everything together with LDAP and I was tired of waiting for management to approve funding :-)

Comment on Re^2: Net::SSH2 Interactive command example

Replies are listed 'Best First'.
Re^3: Net::SSH2 Interactive command example by Anonymous Monk on Jun 20, 2007 at 16:13 UTC
Sorry for the delay in getting back to you. Apologies I just could not get to a computer yesterday. The Code I was using was the one taken from the perlmonks web-site. `my $chan2 = $ssh2->channel(); $chan2->shell(); print $chan2 "hostname -a\n"; print "LINE : $_" while <$chan2>; print $chan2 "tail -f /var/adm/messages"; print "LINE : $_" while <$chan2>; $chan2->close;` [download] (In fact I tried various options on that perlmonks page without success.) The only difference being the "tail -f" command I used instead of "uname" or "who". I notice when I do a "tail -50000". The channel would stay open for as long as it took to get through the 50000 lines. So there is no problem with keeping the channel open as such.I think the problem lies when it is being an interactive real-time command like "tail -f" or "snoop" when I want to keep the channel up and for some reason it takes a snap-shot,or what's in it's buffer and then closes. Any help, greatly appreciated !!!!!!!!!!!!!!!!!!!!!!!. U235sentinel have you ever come across this before?. Regards, Shooter	[reply] [d/l]
Re^4: Net::SSH2 Interactive command example by u235sentinel (Hermit) on Jun 25, 2007 at 20:01 UTC
print $chan2 "tail -f /var/adm/messages"; print "LINE : $_" while <$chan2>; $chan2->close; I'm guessing it thinks it's finished then closes the channel. I didn't realize you meant you needed it open say for hours (for example). My need for the module was to inventory (or change something ) across hundreds of Unix and Linux servers and report the results. It's quick. We can create user accounts and set the password across 500 servers in just a few minutes. Eventually they will get Vintella working and replace the user creation piece. Someday :-) Have you tried running with Net::SSH2::Debug enabled? I'm curious if it might shed a clue there. Or even printing $! if there was an error somewhere. If it runs 50,000 lines then why not until we tell it to stop. I haven't run into this myself. The code is still under a year old and not even 1.0 yet. So I'm sure there are surprises yet to be discovered :-) I'll poke around and see if I can find something that might help us understand how to do this. Cross your fingers. It might be a good idea to post this question on the net::ssh2 forum. David Robbins has popped on there to help answer questions about the module. It was mentioned to try using POLL(). Personally I never got it working properly (neither have several other developers). I'm feeling that piece of the code is still broken. Perhaps in the next libssh2 update it will be fixed.	[reply]