[X2Go-Dev] Bug#475: Bug#475: Also seen on Centos 6.5 with Windows 7 client

[Alan Fitch]

On 25/07/14 20:38, Mike Gabriel wrote:
> Hi Alan,
>
> On  Fr 25 Jul 2014 00:44:29 CEST, Alan Peter Fitch wrote:
>
>> I've seen this on Centos 6.5 with the Windows 7 x2go client, both 4.0.2.0.
>>
>> I tried downgrading the client all the way back to 3.11 with no effect.
>>
>> One interesting point - a colleague running x2goclient on Ubuntu 12 LTS
>> (client version was 3.99) did *not* experience the problem.
>>
>> In my environment it makes x2go unusable, so I'm now investigating xpra
>> to get the resume/suspend functionality.
> Can you detect where exactly the sesion startup hangs?
Hi Mike,

  I'll have to try some tests at work on Monday (I'm trying to use it
where I work).

There are a couple other of other factors. We run various Electronic
Design Automation (EDA) tools.
The access is as follows

1. use x2goclient to access a server running Centos 6.5 and Open Grid
Scheduler (OGS).
2. Launch a terminal on the OGS, e.g.
   qrsh -q name.q xterm
The cluster machines are also running Centos 6.5. qrsh is forwarding X
from the cluster machines using ssh X forwarding (it's not actually
launching rsh, it's using ssh).

3. Launch the tool.

For some tools (e.g. Altera Quartus, Xilinx Vivado) the x2goagent usage
climbs to about 10% CPU as the graphics update.
For Mentor Questasim, the CPU usage climbs to between 70 and 90%, and it
takes ages (5 minutes?)  for the graphics to refresh and stabilise.
During that period, all the windows (the xterm and the EDA tool) are
greyed out and don't refresh.

I've tried running strace and there were millions of calls to a system
file call. I will send you an excerpt of the log on Monday. I think I
attached strace to the process ID of the x2goagent, but I will check
that on Monday.

I will also trying running directly on the server, just to check if the
ssh -X forwarding to the cluster is significant or not.

The thing that really surprised me was that if you use x2goclient from
Ubuntu 12 LTS, everything is fine. It was only access from a Windows 7
x2goclient that was affected.

regards
Alan

>
> My guess is that you have an everlasting x2gostartagent process on the  
> X2Go Server machine that loops endlessly while detecting a free TCP/IP  
> port for binding its forwarding tunnel endpoints to.
>
> We have to rely on a little testing here. Thanks.
>
> Mike


-- 
Alan Fitch