It hasn't happened to me so I don't know what the people are doing before
it gets stuck, could be mate, kde, lxde, lfce, openbox, they're all on there. Next time it happens I'll trace it to see what it is doing.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 4 Mar 2018, Mihai Moldovan wrote:
Date: Sun, 4 Mar 2018 09:44:03 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: nxagent
- On 03/04/2018 01:54 AM, Robert Dinse wrote:
Yes consuming a large amount of CPU and not doing anything useful,
customer is disconnected. Connection is still possible but doesn't get rid of the stuck processes, I have to kill -9 to get rid of them.
Uhm... "stuck" is pretty ambiguous in that context - I assume that you are referring to the CPU usage, which doesn't go down to sane levels even after reconnecting, but reconnecting to the session as such is possible?
Is there any reasonable way to trigger this behavior? Like starting a MATE session, disconnecting and waiting for an hour to see the CPU usage spike? Or is it triggered by other programs running inside of the session?
I'll need something to reproduce it, server OS information would also be great.
There is https://bugs.x2go.org/1260 which sounds like the same issue, but I haven't had time to get into this yet. This issue is observable on Fedora 27, but if it's even observable on Debian or Ubuntu or other distros it would also be interesting information.
Mihai