I haven’t used Ruby for several months and now Net::SSH gives me an
AuthenticationFailed when I try to hand it a user and password. SInce
this is the single most useful library I have for doing automation, I am
in a world of hurt. How can I fix this?
– Matt
It’s not what I know that counts.
It’s what I can remember in time to use.
I also use Net::SSH a lot in my automation and it works fine. Can you
show
us the error that you are getting and the code that causes the error?
Also,
what version of net::ssh are you using?
I haven’t used Ruby for several months and now Net::SSH gives me an
AuthenticationFailed when I try to hand it a user and password. SInce
this
is the single most useful library I have for doing automation, I am in a
world of hurt. How can I fix this?
for me in a single very simple test).
I have narrowed it down and it is failing when trying to connect to an
Oracle ILOM. The ilom is running a version of OpenSSH
– Matt
It’s not what I know that counts.
It’s what I can remember in time to use.
Although the pastebin says “invalid credentials”, authentication succeeds and
a channel is requested. Interaction with the channel fails, after everything
is already set up. Hopefully it is not an issue of exit-status vs. exit-signal
[0]. If it was, it would be up to Net::SSH to patch, but it’s quite easy to
catch. I don’t know which packet types these are, but the RFC will tell us
that easily.
Good catch, that’s what it’s doing. Now I need to figure out a
workaround. In the meantime, I did all of it by hand.
– Matt
It’s not what I know that counts.
It’s what I can remember in time to use.
Does it need a TTY allocated? Try, for example, “ssh -lroot dssmgmt18601
ls”
and see what happens, because this way, no TTY is allocated and it would
mimic
what Net::SSH is doing.
Although the pastebin says “invalid credentials”, authentication
succeeds and
a channel is requested. Interaction with the channel fails, after
everything
is already set up. Hopefully it is not an issue of exit-status vs.
exit-signal
[0]. If it was, it would be up to Net::SSH to patch, but it’s quite easy
to
catch. I don’t know which packet types these are, but the RFC will tell
us
that easily.
On Tuesday 07 October 2014, 16:01:15, Matt L. wrote:
Good catch, that’s what it’s doing.
which one of the two possible issues was it?
After giving up yesterday and doing it by hand, I was handed a bunch of
other systems to deal with this morning. SInce I had a brilliant idea
(if
I do say so myself) I gave Net::SSH::Telnet a shot. It worked!
– Matt
It’s not what I know that counts.
It’s what I can remember in time to use.
On Wednesday 08 October 2014, 14:52:56, Matt L. wrote:
I do say so myself) I gave Net::SSH::Telnet a shot. It worked!
Did you try the TTY-allocated vs. no-TTY version? Because I would like
to
investigate this bug, but I’ve got not ILOM handy. If its just the TTY
thing,
it will not really be a bug, but the exit-status vs. exit-signal part
would be
interesting.
Thanks!
--- Eric
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.