X2Go Bug report logs - #302
No session resume

Full log

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

Received: (at 302) by bugs.x2go.org; 14 Apr 2014 06:15:04 +0000
From Borys.Saulyak@eumetsat.int  Mon Apr 14 08:15:03 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,UNPARSEABLE_RELAY
	autolearn=ham version=3.3.2
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.140])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 9FE215DA79
	for <302@bugs.x2go.org>; Mon, 14 Apr 2014 08:15:03 +0200 (CEST)
Received: from [85.158.139.51:2038] by server-4.bemta-5.messagelabs.com id 93/DD-30750-7EC7B435; Mon, 14 Apr 2014 06:15:03 +0000
X-Env-Sender: Borys.Saulyak@eumetsat.int
X-Msg-Ref: server-3.tower-180.messagelabs.com!1397456102!28786592!1
X-Originating-IP: [193.17.11.201]
X-StarScan-Received:
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8498 invoked from network); 14 Apr 2014 06:15:03 -0000
Received: from mail5.eumetsat.int (HELO EXW05.eumetsat.int) (193.17.11.201)
  by server-3.tower-180.messagelabs.com with AES128-SHA encrypted SMTP; 14 Apr 2014 06:15:03 -0000
Received: from EXW04.eum.root.eumetsat.int (172.16.199.106) by
 exw05.eumetsat.int (172.28.0.11) with Microsoft SMTP Server (TLS) id
 8.3.327.1; Mon, 14 Apr 2014 08:14:56 +0200
Received: from EXW10.eum.root.eumetsat.int ([169.254.2.198]) by
 EXW04.eum.root.eumetsat.int ([172.16.199.106]) with mapi; Mon, 14 Apr 2014
 08:15:02 +0200
From: Borys Saulyak <Borys.Saulyak@eumetsat.int>
To: "302@bugs.x2go.org" <302@bugs.x2go.org>
Date: Mon, 14 Apr 2014 08:15:01 +0200
Subject: Additional info
Thread-Topic: Additional info
Thread-Index: AQHPV6je0qHRNhCet0egylBVO2Kdsw==
Message-ID: <A3ADF8C56ADA0F45BC34F904A6514E280151E8BBEB4E@EXW10.eum.root.eumetsat.int>
Accept-Language: en-US, en-IE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-IE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Here is some more debug info from pyhoca-cli. It seems to me that the issue is rather server-side related:


borys@XXXX:~> pyhoca-cli --server MDADFS01 -u dadfmg --password xxx -R dadfmg-55-1397455646_stDKDE_dp24
pyhoca-cli[12336] NOTICE: preparing requested X2Go session
pyhoca-cli[12336] (PyHocaCLI) NOTICE: preparing requested X2Go session
pyhoca-cli[12336] (x2gosessregistry-pylib) NOTICE: registering X2Go session Pyhoca-Client_Session...
pyhoca-cli[12336] (x2goclient-pylib) NOTICE: initializing X2Go session...
pyhoca-cli[12336] (x2gocontrolsession-pylib) NOTICE: connecting to [MDADFS01]:22
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 1 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 2 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 3 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 4 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 5 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 6 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 7 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 8 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 9 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 10 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 11 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 12 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 13 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 14 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 15 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 16 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 17 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 18 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 19 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30021 failed on attempt 20 of 20: ChannelException('Connect failed',)
pyhoca-cli[12336] (x2gofwtunnel-pylib) ERROR: incoming request to 127.0.0.1:30021 failed after 20 attempts
pyhoca-cli[12336] (x2goclient-pylib) ERROR: Forwarding tunnel request to [127.0.0.1]:30021 for session dadfmg-55-1397455646_stDKDE_dp24 (Pyhoca-Client_Session) was denied by remote X2Go/SSH server. Session startup failed.
pyhoca-cli[12336] (x2goproxy-pylib) ERROR: Bringing up NX3 proxy failed.
pyhoca-cli[12336] (PyHocaCLI) NOTICE: give the X2Go session some time to come up...

Send a report that this bug log contains spam.