OK, thanks.
Sending the answers again, maybe they were cut by the mailing list before.
Question: What version of x2goagent resp. nxagent are you using? dpkg -l nx-libs?
Answer: dpkg -l nx-libs: no packages found <--- this seems strange? x2goserver-x2goagent 4.1.0.3-0~1708~ubuntu1 amd64 nxagent 2:3.5.99.20-0~20190425 amd64
Question: Can you please run xrestop within such a session and check if there are numbers that are far away from those of a fresh session? Answer: Nothing out of the ordinary there I think. No processes with high memory usage.
Question: You probably cannot answer that due to your usage scenario, but anyway: does this also happen when you do not disconnect/reconnect? Answer: I don't know. I started logging the memory usage over time, so when the problem arises next time I can correlate with log events and ask the users what they have been doing at certain times etc.
Question: What are you running inside the session?fdasfafad Answer: No real pattern here for good and bad sessions. Matlab, Python/machine learning stuff, NVIDIA CUDA-accelerated machine learning programs etc. Maybe a browser here and there to look up stuff (Firefox).
— Johannes Töger
Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden
-----Original Message----- From: Ulrich Sibiller <uli42@gmx.de> Sent: Monday, January 20, 2020 15:45 To: Johannes Töger <johannes.toger@med.lu.se> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Long-running x2goagent, high memory usage
Sorry, I forgot to check, but probably not today. But can you please answer my questions in the meantime?
Basically you must replace the x2go binary with a little wrapper that use valgrind to start the original binary with the original arguments.
Uli
On Mon, Jan 20, 2020 at 2:26 PM Johannes Töger <johannes.toger@med.lu.se> wrote:
I have now set up a logging of the memory use over time. I hope this will give some data so we can understand the error. Hopefully I can correlate the memory use increase with user actions.
Ulrich, were you able to figure out if x2go can be run with valgrind?
— Johannes Töger
Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden
-----Original Message----- From: x2go-user <x2go-user-bounces@lists.x2go.org> On Behalf Of Johannes Töger Sent: Friday, January 17, 2020 16:28 To: Ulrich Sibiller <uli42@gmx.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Long-running x2goagent, high memory usage
Thanks for quick reply.
Answers to your questions below. I hope it gives some clue. Please let me know what else I can try.
What version of x2goagent resp. nxagent are you using? dpkg -l nx-libs?
dpkg -l nx-libs: no packages found <--- this seems strange? x2goserver-x2goagent 4.1.0.3-0~1708~ubuntu1 amd64 nxagent 2:3.5.99.20-0~20190425 amd64Can you please run xrestop within such a session and check if there are numbers that are far away from those of a fresh session?
Nothing out of the ordinary there I think. No processes with high memory usage.You probably cannot answer that due to your usage scenario, but anyway: does this also happen when you do not disconnect/reconnect?
I'll try to think of a way to test this.What are you running inside the session?
No real pattern here for good and bad sessions. Matlab, Python/machine learning stuff, NVIDIA CUDA-accelerated machine learning programs etc.— Johannes Töger
Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden
-----Original Message----- From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, January 17, 2020 13:25 To: Johannes Töger <johannes.toger@med.lu.se> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Long-running x2goagent, high memory usage
On Fri, Jan 17, 2020 at 11:56 AM Johannes Töger <johannes.toger@med.lu.se> wrote:
We are using x2go for a common compute server at our department. We have users both on the local LAN and connections to the other side of Europe that work really well. Being able to close the client and have computations still running in a GUI environment is great.
However, I think we have encountered a bug. Some (but not all) of the long-running x2goagent processes start taking a lot of memory, ~30 GB. This adds up quickly so that the other users can’t do their work. Below you can see how user3 and user7 have x2goagent processes with large memory use (RSS column).
How can I go about debugging this? I have quite a bit of Linux experience, but I don’t know where to start on this one since I don’t know much about how x2go works internally.
Server is on Ubuntu Server 18.04.1 LTS, (x2goserver 4.1.0.3-0~1708~ubuntu18.04.1). Clients are on Windows 10, version. 4.1.2.0.
johannes@compute-server:~$ ps -o pid,lstart,rss,user $(pgrep x2goagent)
What version of x2goagent resp. nxagent are you using? dpkg -l nx-libs?
Can you please run xrestop within such a session and check if there are numbers that are far away from those of a fresh session?
You probably cannot answer that due to your usage scenario, but anyway: does this also happen when you do not disconnect/reconnect?
What are you running inside the session?
You could run x2goagent with valgrind to identify memory leaks but I am unsure if that is working on a stock installation ( I don't do the packaging for Debian/Ubuntu so I don't know if the deliveres binaries allow for decent analysis/output). I'll check that this weekend.
Uli
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user