Hi Martin

I think we already have a Jira about that. Let me find it.

I will reproduce and fix that.

Thanks,
Regards
JB

On Wed, Jan 24, 2024 at 2:25 PM Martin Lichtin via user
<user@karaf.apache.org> wrote:
>
> Hi all, I noticed a change in SSH server session close behavior, as I
> upgraded from 4.3.10 to 4.4.5.
> Doing calls such as
>
>     ssh -p 8101 karaf@localhost feature:list
>
> still works fine. However with 4.4.5, the ssh client now sporadically
> reports
>
>     Connection to localhost closed by remote host.
>
> The difference seems in the session shutdown.
>
> In the "good" case it is:
>
> debug2: channel 0: rcvd eof
> debug2: channel 0: output open -> drain
> debug2: channel 0: obuf empty
> debug2: channel 0: chan_shutdown_write (i0 o1 sock -1 wfd 5 efd 6 [write])
> debug2: channel 0: output drain -> closed
> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
> debug2: channel 0: rcvd close
> debug2: channel 0: chan_shutdown_read (i0 o3 sock -1 wfd 4 efd 6 [write])
> debug2: channel 0: input open -> 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
> Transferred: sent 2064, received 28800 bytes, in 0.1 seconds
> Bytes per second: sent 23511.4, received 328065.6
> debug1: Exit status 0
>
> In the "bad" case it is:
>
> debug2: channel 0: rcvd eof
> debug2: channel 0: output open -> drain
> debug2: channel 0: obuf empty
> debug2: channel 0: chan_shutdown_write (i0 o1 sock -1 wfd 5 efd 6 [write])
> debug2: channel 0: output drain -> closed
> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
> debug1: channel 0: free: client-session, nchannels 1
> Connection to localhost closed by remote host.
> Transferred: sent 2048, received 28768 bytes, in 0.0 seconds
> Bytes per second: sent 41302.3, received 580168.6
> debug1: Exit status 0
>
> Seems a timing issue, interacting with the new SSHD code?
>
> - Martin
>

Reply via email to