From cottonke@gmail.com Wed Oct 29 15:37:04 2014 Received: (at 656) by bugs.x2go.org; 29 Oct 2014 14:37:05 +0000 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,FREEMAIL_FROM, HTML_MESSAGE,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com [209.85.160.171]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id E883F5DB48 for <656@bugs.x2go.org>; Wed, 29 Oct 2014 15:37:03 +0100 (CET) Received: by mail-yk0-f171.google.com with SMTP id 20so1339460yks.2 for <656@bugs.x2go.org>; Wed, 29 Oct 2014 07:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ULIZqQpGeN/cccbyyH5oR6N10E3pg5j4zte2IQEbu1Q=; b=ynIoRZAAlslN4quVhaMKjvwiEVFj/jeaeFvkzBdHw/syoIPaRKdBQW0/rcW6rPSXF3 jdRWrlufxRQMAmFw7Yu98q+ZcmHu2iHa0oBalUORQ9Ws26dnQXm16Mlj2yCl1eqoiEML curKwBr9AD7GWPhC+20ycJ11C5o1SbJzOuKvhmEOxUa/TEurlzMzugRfckVdmgS4doVq WTmdXoLwmOoP9FvSqtHSnfAJPnn3Ap85Ymuu441jSARO+BtcnN8V5TM2VCSurUJHHd2y x68FcOf02ZZwAJsJOqMfSnkmrdzt/zMulqO6kKFimtOVQbUqHpV+KPPCwlmecXSvX8yq S3Ig== X-Received: by 10.236.66.206 with SMTP id h54mr1846818yhd.153.1414593422229; Wed, 29 Oct 2014 07:37:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.187.145 with HTTP; Wed, 29 Oct 2014 07:36:41 -0700 (PDT) In-Reply-To: <20141029141706.Horde.z8yYZEN59UUjc8UL50EdXg6@mail.das-netzwerkteam.de> References: <20141029093932.Horde.QzW4YecVJXaLTQxWF36nrQ1@mail.das-netzwerkteam.de> <20141029141706.Horde.z8yYZEN59UUjc8UL50EdXg6@mail.das-netzwerkteam.de> From: Kyle Cottongim Date: Wed, 29 Oct 2014 09:36:41 -0500 Message-ID: Subject: Re: [X2Go-Dev] Bug#656: Fwd: Windows X2GoClient hangs when launching x2gostartagent To: Mike Gabriel Cc: 656 <656@bugs.x2go.org> Content-Type: multipart/alternative; boundary=001a1133cf586f06dd050690b2f9 --001a1133cf586f06dd050690b2f9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Mike, On Wed, Oct 29, 2014 at 9:17 AM, Mike Gabriel < mike.gabriel@das-netzwerkteam.de> wrote: > 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 som= e >>> 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 >>> >> >> >> =E2=80=8BDuring this launch attempt, it seems the client is getting a bi= t further >> along than before, but still not to the point of launching something=E2= =80=8B. >> 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 executin= g >> this script and now seems to be getting past this point. I have turned t= he >> 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]: x2golistsession= s >> has been called with no option >> Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: x2gostartagent called wi= th >> options: 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOM= E >> 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]: x2gosessionlimi= t >> has been called >> Oct 29 08:02:34 oddjob /usr/bin/x2golistsessions[12838]: x2golistsession= s >> 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, th= is >> 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 > > =E2=80=8BThe output of " x2golistsessions --all-servers =E2=80=8B" is nothing ... there are no lines printed from this command.=E2= =80=8B =E2=80=8B =E2=80=8BThe output of "x2goversion" is as follows: $ x2goversion x2goagent: 3.5.0.27 x2goserver: 4.0.1.18 x2goserver-extensions: 4.0.1.16 x2goserver-xsession: 4.0.1.16 Kyle=E2=80=8B --001a1133cf586f06dd050690b2f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mike,

On Wed, Oct 29, 2014 at 9:17 AM, Mike Ga= briel <mike.gabriel@das-netzwerkteam.de> wrot= e:
Hi Kyle,


On=C2=A0 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=C2=A0 So 26 Okt 2014 00:04:16 CEST, Kyle Cottongim wrote:

=C2=A0Package: X2GoClient
Version: 4.0.3.0

When launching a session from within the X2GoClient, the process will hang<= br> 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<= br> 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<= br> before executing that command.

Or is x2gostartagent hanging somewhere on the way? (Extra log messages
placed in x2gostartagent will be helpful then).

Regards,
Mike


=E2=80=8BDuring this launch attempt, it seems the client is getting a bit f= urther
along than before, but still not to the point of launching something=E2=80= =8B. 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&= quot;
x2go-DEBUG-onmainwindow.cpp:9373> "-multiwindow -notrayicon = -clipboard"
x2go-DEBUG-onmainwindow.cpp:9410> Running "C:/Program Files<= br> (x86)/x2goclient\vcxsrv\vcxsrv.exe" "-multiwindow -notrayi= con -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<= br> 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]: x2golistses= sions
has been called with no option
Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: x2gostartagent called with<= br> 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<= br> ,,131.199.103.76''
Oct 29 08:02:34 oddjob /usr/bin/x2gosessionlimit[12835]: x2gosession= limit
has been called
Oct 29 08:02:34 oddjob /usr/bin/x2golistsessions[12838]: x2golistses= sions
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<= br> 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

=C2=A0 x2golistsessions --all-servers

while X2Go Client is trying to launch the session?

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

Also, please tell me your X2Go Server version.

=C2=A0 $ x2goversion

Mike


=E2=80=8BThe output of "
x2golistsessions --all-ser= vers
=E2=80=8B" is nothing ... t= here are no lines printed from this command.=E2=80=8B
=E2=80=8B
=C2=A0

=E2=80=8BThe output of "x2goversion" is as follows:
=
$ x2goversion
x2goagent: 3.5.0.27
x2goserver: 4.0.1.1= 8
x2goserver-extensions: 4.0.1.16
x2goserver-xsession: 4.0.1.16

Kyle=E2=80=8B

--001a1133cf586f06dd050690b2f9--