X2Go Bug report logs - #1557
Windows client crashes when connecting to RHEL8

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Hans Peter Verne <h.p.verne@geo.uio.no>

Date: Thu, 5 Aug 2021 14:45:02 UTC

Severity: normal

Found in version 4.1.2.2

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1557; Package x2goclient. (Thu, 05 Aug 2021 14:45:02 GMT) (full text, mbox, link).


Acknowledgement sent to Hans Peter Verne <h.p.verne@geo.uio.no>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Thu, 05 Aug 2021 14:45:02 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Hans Peter Verne <h.p.verne@geo.uio.no>
To: submit@bugs.x2go.org
Cc: Hans Peter Verne <h.p.verne@geo.uio.no>
Subject: Windows client crashes when connecting to RHEL8
Date: Thu, 5 Aug 2021 16:43:50 +0200
[Message part 1 (text/plain, inline)]
Package: x2goclient
Version: 4.1.2.2

Hello, devs!

I'm afraid this is not a very precise bug report.  Any assistance in
how to investigate this is appreciated.

We're running x2goclient 4.1.2.2 on Windows-10 machines, this has served
us well up to now.  With our new RedHat Enterprise Server 8.4 in production,
we see the client crashing very often.

When the client crashes, it does so shortly after trying to log in to a
new or existing session.  The clients "show details" window pane is activated, 
but the client dies before anything can be seen there.

On the server, just these entries in the system logs appears:

Aug 05 14:42:56 mimi.uio.no sshd[2421324]: Connection from 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101 port 22
Aug 05 14:42:59 mimi.uio.no sshd[2421324]: Connection reset by 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 [preauth]

If I disable IPv6:

Aug 05 14:45:30 mimi.uio.no sshd[2421601]: Connection from 193.157.161.44 port 57619 on 129.240.118.101 port 22
Aug 05 14:45:33 mimi.uio.no sshd[2421601]: Connection reset by 193.157.161.44 port 57619 [preauth]

Note the absence of the "Fail password for ..." log entry.  It looks like
it never gets to even try authenticating.

There is no problem logging in with putty from the same client machine,
both with IPv6 and IPv4.  Neither have I had this problem (at least
not so frequent) with the Linux client.

The server is running sshd and x2goserver from the RHEL8/EPEL repos,
packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively.

I eventually tried to run sshd -ddd on the server and catch the output.  
The typescripts are attached (slightly edited): one where the client crashed;
and one where it didn't (but couldn't authenticate, bad password).  I'm no
expert on ssh, but it seems like the difference appears after the key exchange
("KEX done"), when the instance that crashed never reaches the bit with 
userauth-request.

I also tried "setenforce 0" on the server, i.e. disable SELinux, but the
client still crashed.

As it is, I can't clearly provide a procedure to reproduce the problem,
as it doesn't always happen. 

If more information is required, or there are suggested steps to take,
please let me know.


Thanks in advance, and best regards,
-- 
Hans Peter Verne  --  IT-drift Geofag.

In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a court
in West Berlin overturned the 1933 verdict, and posthumously changed Van der
Lubbe's sentence to eight years in prison.  -- "Reichstag fire" on Wikipedia.
[sshd.debug-x2go_access-denied (text/plain, attachment)]
[sshd.debug-x2go_crash (text/plain, attachment)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1557; Package x2goclient. (Wed, 25 Aug 2021 13:25:01 GMT) (full text, mbox, link).


Acknowledgement sent to Adam Dorsey - NOAA Affiliate <adam.dorsey@noaa.gov>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Wed, 25 Aug 2021 13:25:01 GMT) (full text, mbox, link).


Message #10 received at 1557@bugs.x2go.org (full text, mbox, reply):

From: Adam Dorsey - NOAA Affiliate <adam.dorsey@noaa.gov>
To: 1557@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#1557: Windows client crashes when connecting to RHEL8
Date: Wed, 25 Aug 2021 09:19:50 -0400
[Message part 1 (text/plain, inline)]
Hans,
I wonder if this is the same issue that is described in bug report #1520 (
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1520).  Can you try the
workaround from that bug report?

Thanks,
Adam

On Wed, Aug 25, 2021 at 6:03 AM Hans Peter Verne <h.p.verne@geo.uio.no>
wrote:

> Package: x2goclient
> Version: 4.1.2.2
>
> Hello, devs!
>
> I'm afraid this is not a very precise bug report.  Any assistance in
> how to investigate this is appreciated.
>
> We're running x2goclient 4.1.2.2 on Windows-10 machines, this has served
> us well up to now.  With our new RedHat Enterprise Server 8.4 in
> production,
> we see the client crashing very often.
>
> When the client crashes, it does so shortly after trying to log in to a
> new or existing session.  The clients "show details" window pane is
> activated,
> but the client dies before anything can be seen there.
>
> On the server, just these entries in the system logs appears:
>
> Aug 05 14:42:56 mimi.uio.no sshd[2421324]: Connection from
> 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101
> port 22
> Aug 05 14:42:59 mimi.uio.no sshd[2421324]: Connection reset by
> 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 [preauth]
>
> If I disable IPv6:
>
> Aug 05 14:45:30 mimi.uio.no sshd[2421601]: Connection from 193.157.161.44
> port 57619 on 129.240.118.101 port 22
> Aug 05 14:45:33 mimi.uio.no sshd[2421601]: Connection reset by
> 193.157.161.44 port 57619 [preauth]
>
> Note the absence of the "Fail password for ..." log entry.  It looks like
> it never gets to even try authenticating.
>
> There is no problem logging in with putty from the same client machine,
> both with IPv6 and IPv4.  Neither have I had this problem (at least
> not so frequent) with the Linux client.
>
> The server is running sshd and x2goserver from the RHEL8/EPEL repos,
> packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively.
>
> I eventually tried to run sshd -ddd on the server and catch the output.
> The typescripts are attached (slightly edited): one where the client
> crashed;
> and one where it didn't (but couldn't authenticate, bad password).  I'm no
> expert on ssh, but it seems like the difference appears after the key
> exchange
> ("KEX done"), when the instance that crashed never reaches the bit with
> userauth-request.
>
> I also tried "setenforce 0" on the server, i.e. disable SELinux, but the
> client still crashed.
>
> As it is, I can't clearly provide a procedure to reproduce the problem,
> as it doesn't always happen.
>
> If more information is required, or there are suggested steps to take,
> please let me know.
>
>
> Thanks in advance, and best regards,
> --
> Hans Peter Verne  --  IT-drift Geofag.
>
> In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a
> court
> in West Berlin overturned the 1933 verdict, and posthumously changed Van
> der
> Lubbe's sentence to eight years in prison.  -- "Reichstag fire" on
> Wikipedia.
> _______________________________________________
> x2go-dev mailing list
> x2go-dev@lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-dev
>


-- 
Adam Dorsey
NOAA RDHPCS Systems Administrator Site Lead
CSRA / RedLine Performance Solutions, LLC

NOAA NESCC
1000 Galliher Drive, Suite 333, Fairmont, WV 26554
office: (304) 367-2882
cell: (304) 685-9345
adam.dorsey@noaa.gov
[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Sun Dec 4 09:36:21 2022; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.