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

Full log

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

Received: (at 1557) by bugs.x2go.org; 25 Aug 2021 13:20:14 +0000
From adam.dorsey@noaa.gov  Wed Aug 25 15:20:05 2021
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FROM_GOV_DKIM_AU,HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,URIBL_BLOCKED autolearn=ham
	autolearn_force=no version=3.4.2
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id D632C5DC3C
	for <1557@bugs.x2go.org>; Wed, 25 Aug 2021 15:20:03 +0200 (CEST)
Received: by mail-qt1-x82c.google.com with SMTP id t32so4506326qtc.3
        for <1557@bugs.x2go.org>; Wed, 25 Aug 2021 06:20:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=noaa.gov; s=google;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=t80XNBr1UE7YqBAiGbrYy2B286nETHFQSbTN4hp5/vU=;
        b=l2RYD2s7qDhxx1iKDl/uy0CkxjQjpfnNKWc1WbrzWb+QHpIpe8xnk75iZgwdWO0xfd
         h414WFxFAwJsC5iMGwJi52Nca+kGbMVA9DADx700LtWoSNolqAzG9MvKQDrKwWeaF00+
         tZfwAIsl295RxE1V0LBZWbEh+z8Q6JOp/osalQd8blwDQ/p0yRVoIEk2+b2Hgtd4GNHE
         UmPBX4eAYrMwiS87owixRi5juPf8axfCquOnjzuRD6sCzMx35cvB13DYP10D+957K0dF
         pXPRdzxKPHtQ9yTzpa1DuhMCbemPjJAtC6PF4abZYRlToncKmjh54TLeZAdPEYz9C2Nq
         hQ8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=t80XNBr1UE7YqBAiGbrYy2B286nETHFQSbTN4hp5/vU=;
        b=oqk3uy0aR/iFZWNt1FElGVv+n5GtcoDATV9VATtJPCPsWnrVkfqlrsBUB49xd83vKw
         a7yAuw9q/MKcxfXJSDZziJXgw1W6zMDvAIWJxpofDNQjkUAnctEE41+qAbKYOrip9J0H
         v17kb5uXe/lgMzq4GVwUIpSPMEVVvtnoYcF4CVno03BKQ9QhD15tU7NdYXTt7iaapLSZ
         /qnVOi6yT6rB53fLhcCLTdNMyCBAiUGlpfIXJGneonCNoRSgeKXgdTmtt8TPJGRBXHp/
         FQRMAZawQ3K71p41ABf7u4+8XhO0gBBl/znsfD17TB9yahGFXpszEvldlZa6S2/W6psK
         A0dw==
X-Gm-Message-State: AOAM533JU1fBI31LEQR58hOOUo+L+G/pL0msYQLXDY5LZrbVn6pTduq9
	0YwtijcvWY+41qP+Ckvg/3VCMtMp6j74qDT+29j7/6DPtI1K4Q==
X-Google-Smtp-Source: ABdhPJzLaS8i+lFVkq8C5HTYvj3Rmf+BS04oXIY5bDgzh68NQj0+o1XU0QZCt2U+4kxK3hLfcDPOxx+LpjPpAWTC9Mw=
X-Received: by 2002:ac8:424c:: with SMTP id r12mr30632881qtm.183.1629897601765;
 Wed, 25 Aug 2021 06:20:01 -0700 (PDT)
MIME-Version: 1.0
References: <372b7f8e-8d40-8fc7-6789-cab8db717cf4@geo.uio.no>
In-Reply-To: <372b7f8e-8d40-8fc7-6789-cab8db717cf4@geo.uio.no>
From: Adam Dorsey - NOAA Affiliate <adam.dorsey@noaa.gov>
Date: Wed, 25 Aug 2021 09:19:50 -0400
Message-ID: <CACRHCWHU6S_MCQSvn-FuHVWh76w8qyHq0OQCZbwAYc5Y8XtBWg@mail.gmail.com>
Subject: Re: [X2Go-Dev] Bug#1557: Windows client crashes when connecting to RHEL8
To: 1557@bugs.x2go.org
Content-Type: multipart/alternative; boundary="00000000000093157505ca621b1d"

[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.