Re: how to handle login failures with Net:::SSH::Perl?

Look at Net::SSH::Perl closely. You may need to look at the code.

It's been awhile since I've worked with this module so I'm afraid I can't give you anything specific. But as I recall, this module has a different concept of a command failing than you might be expecting. Much of what you would consider an error is actually returned as a warning if at all. Kind of like the SQL "zero rows returned" debate of whether that is an error, success or warning sort of thing.

Since the module can't really determine if your command executed successfully or not, there are almost no "error" conditions. You should be able to turn on verbose logging and capture that. There may be something surprising happening there...

Comment on Re: how to handle login failures with Net:::SSH::Perl?

Replies are listed 'Best First'.
Re^2: how to handle login failures with Net:::SSH::Perl? by jfroebe (Parson) on Sep 21, 2004 at 21:47 UTC
Hi, Actually, it is on the connection itself that the cmd() is die'ing on. So there won't be any output in STDERR from the remote command. Jason L. Froebe No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1	[reply]
Re^3: how to handle login failures with Net:::SSH::Perl? by KeighleHawk (Scribe) on Sep 22, 2004 at 16:49 UTC
even so, setting verbose mode should give you more information. This was how I debugged the connection/setup problems I had when using this module in the past... Have you tried setting verbose mode? I notice the module has a debug option which is approximatly the same thing. Perhaps setting this and posting the results would be more enlightening...?	[reply]