X2Go Bug report logs - #656
Fwd: Windows X2GoClient hangs when launching x2gostartagent

Full log

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

Received: (at 656) by bugs.x2go.org; 29 Oct 2014 14:17:10 +0000
From mike.gabriel@das-netzwerkteam.de  Wed Oct 29 15:17:08 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,URIBL_BLOCKED
	autolearn=ham version=3.3.2
Received: from freya.das-netzwerkteam.de (freya.das-netzwerkteam.de [88.198.48.199])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 720055DB48
	for <656@bugs.x2go.org>; Wed, 29 Oct 2014 15:17:08 +0100 (CET)
Received: from grimnir.das-netzwerkteam.de (grimnir.das-netzwerkteam.de [78.46.204.98])
	by freya.das-netzwerkteam.de (Postfix) with ESMTPS id CC4693B25;
	Wed, 29 Oct 2014 15:17:07 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id DFD303BAB4;
	Wed, 29 Oct 2014 15:17:06 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at grimnir.das-netzwerkteam.de
Received: from grimnir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (grimnir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KzXkzad2wHNT; Wed, 29 Oct 2014 15:17:06 +0100 (CET)
Received: from grimnir.das-netzwerkteam.de (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTPS id 87A263BA87;
	Wed, 29 Oct 2014 15:17:06 +0100 (CET)
Received: from listrac.informatik.uni-kiel.de
 (listrac.informatik.uni-kiel.de [134.245.252.114]) by
 mail.das-netzwerkteam.de (Horde Framework) with HTTP; Wed, 29 Oct 2014
 14:17:06 +0000
Date: Wed, 29 Oct 2014 14:17:06 +0000
Message-ID: <20141029141706.Horde.z8yYZEN59UUjc8UL50EdXg6@mail.das-netzwerkteam.de>
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
To: Kyle Cottongim <cottonke@gmail.com>
Cc: 656@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#656: Fwd: Windows X2GoClient hangs when
 launching x2gostartagent
References: <CAPxkJXKdd89R=TdjaZtrgr2ZDpE4WABG96gXyf3PdCaBfi3PNg@mail.gmail.com>
 <CAPxkJXL=z6kBJy4PdM4yypTjqPs42aqmki9OHkYHqxxBw5XGNA@mail.gmail.com>
 <20141029093932.Horde.QzW4YecVJXaLTQxWF36nrQ1@mail.das-netzwerkteam.de>
 <CAPxkJXJ3Y1G2+PQt5KN9BE6QQCNw7zXqR7r4YEJSMP-wGqF7Ag@mail.gmail.com>
In-Reply-To: <CAPxkJXJ3Y1G2+PQt5KN9BE6QQCNw7zXqR7r4YEJSMP-wGqF7Ag@mail.gmail.com>
User-Agent: Internet Messaging Program (IMP) H5 (6.2.2)
Accept-Language: en,de
Organization: DAS-NETZWERKTEAM
X-Originating-IP: 134.245.252.114
X-Remote-Browser: Mozilla/5.0 (X11; Linux i686; rv:33.0) Gecko/20100101
 Firefox/33.0 Iceweasel/33.0
Content-Type: multipart/signed; boundary="=_UycnbYTE--lfP5nvdOX7MA8";
 protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0

[Message part 1 (text/plain, inline)]

Hi Kyle,

On  Mi 29 Okt 2014 14:30:54 CET, Kyle Cottongim wrote:

> Hello Mike,
>
> On Wed, Oct 29, 2014 at 4:39 AM, Mike Gabriel <
> mike.gabriel@das-netzwerkteam.de> wrote:
>
>> Hi Kyle,
>>
>> On  So 26 Okt 2014 00:04:16 CEST, Kyle Cottongim wrote:
>>
>>  Package: X2GoClient
>>> Version: 4.0.3.0
>>>
>>> When launching a session from within the X2GoClient, the process will hang
>>> after the following call:
>>>
>>> x2go-DEBUG-onmainwindow.cpp:3900> Executing remote command:
>>> "x2gostartagent
>>> 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME both"
>>>
>>> This does not happen all the time, but generally happens after loss of
>>> network connection or after logging out instead of just closing the
>>> X2GoClient window. A complete restart of the client machine will solve the
>>> issue.
>>>
>>
>> Could you cross-check the debug output of X2Go Server, possibly add some
>> more log message to /usr/bin/x2gostartagent, so that we can narrow down,
>> where the "hang" actually occurs?
>>
>> Does x2gostartagent get executed at all, or is X2Go Client aready stalling
>> before executing that command.
>>
>> Or is x2gostartagent hanging somewhere on the way? (Extra log messages
>> placed in x2gostartagent will be helpful then).
>>
>> Regards,
>> Mike
>
>
> ​During this launch attempt, it seems the client is getting a bit further
> along than before, but still not to the point of launching something​. Here
> is how far things are getting now:
>
> x2go-DEBUG-onmainwindow.cpp:2778> SSH connection established.
> x2go-DEBUG-onmainwindow.cpp:3038> Continue normal x2go session
> x2go-DEBUG-onmainwindow.cpp:3382> ""
> x2go-DEBUG-onmainwindow.cpp:3769> Fullscreen: false
> x2go-DEBUG-onmainwindow.cpp:9257> got localhost
> x2go-DEBUG-onmainwindow.cpp:9279> Port is free: 6000
> x2go-DEBUG-onmainwindow.cpp:9345> using internal X: true
> x2go-DEBUG-onmainwindow.cpp:9368> WxH:"1440"x"900"
> x2go-DEBUG-onmainwindow.cpp:9373> "-multiwindow -notrayicon -clipboard"
> x2go-DEBUG-onmainwindow.cpp:9410> Running "C:/Program Files
> (x86)/x2goclient\vcxsrv\vcxsrv.exe" "-multiwindow -notrayicon -clipboard :0"
> x2go-DEBUG-onmainwindow.cpp:3900> Executing remote command: "x2gostartagent
> 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME both"
> x2go-DEBUG-onmainwindow.cpp:9257> got localhost
> x2go-DEBUG-onmainwindow.cpp:9285> Port already used: 6000
> x2go-DEBUG-onmainwindow.cpp:9439> X is started.
> x2go-DEBUG-onmainwindow.cpp:9790> All winservers are started.
>
> With some debug within the x2gostartagent I can tell that it is executing
> this script and now seems to be getting past this point. I have turned the
> logging level of the server to debug and here is the output I am seeing
> during a connection attempt:
>
> Oct 29 08:02:33 oddjob /usr/bin/x2golistsessions[12799]: x2golistsessions
> has been called with no option
> Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: x2gostartagent called with
> options: 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME
> both
> Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: client announced itself as
> ,,131.199.103.76''
> Oct 29 08:02:34 oddjob /usr/bin/x2gosessionlimit[12835]: x2gosessionlimit
> has been called
> Oct 29 08:02:34 oddjob /usr/bin/x2golistsessions[12838]: x2golistsessions
> has been called with options: --all-servers
>
> I added some more debug messages to x2golistsessions and am seeing that
> this script seems to finish execution (I reach deubg statements just before
> closing syslog).
>
> Another note is that even after restart of the client and server PCs, this
> is not working. Also, If I keep my client open for a long time after it
> "hangs", it will sometimes eventually bring up the remote session. The time
> it takes for it to do this is on the order of magnitude of many hours.
>
> Thanks,
> Kyle

Can you provide the output of

  x2golistsessions --all-servers

while X2Go Client is trying to launch the session?

Make sure to obfuscate non-public data from listsession's output  
(username, host IPs, etc.).

Also, please tell me your X2Go Server version.

  $ x2goversion

Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.