Berry,
Did you try turning debug on for sshd? I find you get a lot more
information debugging from the server side than the client (and this makes
sense for security reasons).
On a SLES system, in the file /etc/sysconfig/ssh, I add a '-d' to :
SSHD_OPTS="-d"
Then "service restart sshd". You should immediately see debug info on the
console.
Hope this helps
-Mike M
On Thu, May 26, 2016 at 7:14 AM, van Sleeuwen, Berry <
[email protected]> wrote:
> Hi Rick,
>
> I can logon on the VM console so I expect the shell and various profiles
> should be ok.
>
> It's (almost) the same when I logon through ssh with another userid.
>
> Password:
> debug2: input_userauth_info_req
> debug2: input_userauth_info_req: num_prompts 0
> debug1: Authentication succeeded (keyboard-interactive).
> Authenticated to x.x.x.x ([x.x.x.x]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> debug1: Requesting [email protected]
> debug1: Entering interactive session.
> Write failed: Broken pipe
>
> Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
> Berry van Sleeuwen
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
> Rick Troth
> Sent: Thursday, May 26, 2016 12:36 PM
> To: [email protected]
> Subject: Re: Unable to login with ssh
>
> Bad shell? (exits right away)
>
> Can you sign on with a different ID?
>
> Check your .profile, .bashrc, and their equiv under /etc.
>
> Try the virtual console if you can't do these "checks" from another ID.
>
> I might also suggest looking into the ciphers available (which *have*
> changed recently), but since it shows "last login" that's probably not the
> problem.
>
> -- R; <><
>
>
> On May 26, 2016 5:07 AM, "van Sleeuwen, Berry" <[email protected]
> >
> wrote:
>
> > Hi All,
> >
> > I try to login to a SLES10 linux guest. It looks like the login is
> > correct but right after that the session is closed. I have tried to
> > ssh from another linux guest, with trace options. But it is still
> > unclear to me why the session is aborted. I have tried to find some
> > clues in various locations but a lot of those solutions are either not
> > applicable or do not help to solve the issue.
> >
> > Why would this session be closed and how can I fix this?
> >
> > <BVS: Removed the start of the trace, check of various keys and
> > cyphers>
> > Password:
> > debug3: packet_send2: adding 32 (len 20 padlen 12 extra_pad 64)
> > debug2: input_userauth_info_req
> > debug2: input_userauth_info_req: num_prompts 0
> > debug3: packet_send2: adding 48 (len 10 padlen 6 extra_pad 64)
> > debug1: Authentication succeeded (keyboard-interactive).
> > Authenticated to x.x.x.x ([y.y.y.y]:22).
> >
> > <BVS: So looks like I am granted access >
> > <BVS: removed environment records…>
> > <BVS: the following 6 records are similar to a successful login, after
> > that the session close starts>
> >
> > debug2: channel 0: open confirm rwindow 0 rmax 32768
> > debug2: channel_input_status_confirm: type 99 id 0
> > debug2: PTY allocation request accepted on channel 0
> > debug2: channel 0: rcvd adjust 2097152
> > debug2: channel_input_status_confirm: type 99 id 0
> > debug2: shell request accepted on channel 0
> > debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
> > debug1: client_input_channel_req: channel 0 rtype [email protected]
> > reply 0
> > debug2: channel 0: rcvd eow
> > debug2: channel 0: close_read
> > debug2: channel 0: input open -> closed
> > debug2: channel 0: rcvd eof
> > debug2: channel 0: output open -> drain
> > debug2: channel 0: rcvd close
> > debug3: channel 0: will not send data after close Last login: Thu May
> > 26 10:37:40 2016 from xxx.xxx.xxx.xxx
> >
> > <BVS: The last login was the previous time I tried. So indeed the
> > login is accepted and logged.)
> >
> > debug3: channel 0: will not send data after close
> > debug2: channel 0: obuf empty
> > debug2: channel 0: close_write
> > debug2: channel 0: output drain -> closed
> > debug2: channel 0: almost dead
> > debug2: channel 0: gc: notify user
> > debug2: channel 0: gc: user detached
> > debug2: channel 0: send close
> > debug2: channel 0: is dead
> > debug2: channel 0: garbage collecting
> > debug1: channel 0: free: client-session, nchannels 1
> > debug3: channel 0: status: The following connections are open:
> > #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)
> >
> > Connection to y.y.y.y closed.
> > Transferred: sent 3096, received 2392 bytes, in 0.0 seconds Bytes per
> > second: sent 2010460.6, received 1553301.6
> > debug1: Exit status -1
> >
> >
> > Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
> > Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven • +31 (0)6
> > 22564276 [cid:[email protected]]
> > [cid:[email protected]]
> >
> >
> > This e-mail and the documents attached are confidential and intended
> > solely for the addressee; it may also be privileged. If you receive this
> > e-mail in error, please notify the sender immediately and destroy it. As
> > its integrity cannot be secured on the Internet, Atos’ liability cannot
> be
> > triggered for the message content. Although the sender endeavours to
> > maintain a computer virus-free network, the sender does not warrant that
> > this transmission is virus-free and will not be liable for any damages
> > resulting from any virus transmitted. On all offers and agreements under
> > which Atos Nederland B.V. supplies goods and/or services of whatever
> > nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply.
> > The Terms of Delivery shall be promptly submitted to you on your request.
> >
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail in error, please notify the sender immediately and destroy it. As
> its integrity cannot be secured on the Internet, Atos’ liability cannot be
> triggered for the message content. Although the sender endeavours to
> maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted. On all offers and agreements under
> which Atos Nederland B.V. supplies goods and/or services of whatever
> nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply.
> The Terms of Delivery shall be promptly submitted to you on your request.
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
