Hi,
we are using x2go as Terminal-server-Solution instead of an LTSP-server in the skolelinux edu-debian-environment. The TS-server works an the Clients are working well, but:
The RAM fills with old x2go-sessions. They are not killed by any service anytime. The used RAM grows up and the server-performance decrease. I "solved" the problem by killing all x2goagents-prozesses with cron twice a day.
The home-directories of my users fill with log-files like these : /home/pcag01/.x2go/S-es01-119-1313081349_stDKDE_dp24and they are not deleted.
My logfiles in /var/log like message or syslog grow up to a few hundred MB for example with entries like these: Sep 22 06:30:24 ltspserver01 ltspserver01 console-kit-daemon[24530]: WARNING: Record was not written to disk (File too large) Sep 22 06:30:55 ltspserver01 last message repeated 606 times
Is there anyone who understands what my server makes?
Greetings Thomas Ritter
On Sun, 2011-09-25 at 21:58 +0200, Thomas Ritter wrote:
Hi,
we are using x2go as Terminal-server-Solution instead of an LTSP-server in the skolelinux edu-debian-environment. The TS-server works an the Clients are working well, but:
The RAM fills with old x2go-sessions. They are not killed by any service anytime. The used RAM grows up and the server-performance decrease. I "solved" the problem by killing all x2goagents-prozesses with cron twice a day.
The home-directories of my users fill with log-files like these : /home/pcag01/.x2go/S-es01-119-1313081349_stDKDE_dp24 and they are not deleted.
My logfiles in /var/log like message or syslog grow up to a few hundred MB for example with entries like these: Sep 22 06:30:24 ltspserver01 ltspserver01 console-kit-daemon[24530]: WARNING: Record was not written to disk (File too large) Sep 22 06:30:55 ltspserver01 last message repeated 606 times
Is there anyone who understands what my server makes? <snip> I can confirm the problem but I've never taken the time to investigate why X2Go does that and how to address it - John
Hi Thomas,
On Mo 26 Sep 2011 11:45:42 CEST "John A. Sullivan III" wrote:
On Sun, 2011-09-25 at 21:58 +0200, Thomas Ritter wrote:
Hi,
- The RAM fills with old x2go-sessions. They are not killed by any service anytime. The used RAM grows up and the server-performance decrease.
When testing I have also observed such situations: x2goagents
remaining running while the X2go session is marked as finished in the
X2go database.
I "solved" the problem by killing all x2goagents-prozesses with cron twice a day.
It's at most a workaround... not a solution... We'll have to check
that X2go upstream-wise.
- The home-directories of my users fill with log-files like these : /home/pcag01/.x2go/S-es01-119-1313081349_stDKDE_dp24 and they are not deleted.
Over the last weekend I have added code that will (at least) remove
these session directories in case the session has finished
successfully (session meaning here: if the executed command of the
session returns with a clean exitcode).
- My logfiles in /var/log like message or syslog grow up to a few hundred MB for example with entries like these: Sep 22 06:30:24 ltspserver01 ltspserver01 console-kit-daemon[24530]: WARNING: Record was not written to disk (File too large) Sep 22 06:30:55 ltspserver01 last message repeated 606 times
Is there anyone who understands what my server makes? <snip> I can confirm the problem but I've never taken the time to investigate why X2Go does that and how to address it - John
The problem under 3)... ist that X2go specific? John, have you seen
that one, too? Under what conditions???
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Mon, 2011-09-26 at 13:13 +0200, Mike Gabriel wrote:
Hi Thomas,
On Mo 26 Sep 2011 11:45:42 CEST "John A. Sullivan III" wrote:
On Sun, 2011-09-25 at 21:58 +0200, Thomas Ritter wrote:
Hi,
- The RAM fills with old x2go-sessions. They are not killed by any service anytime. The used RAM grows up and the server-performance decrease.
When testing I have also observed such situations: x2goagents
remaining running while the X2go session is marked as finished in the
X2go database.I "solved" the problem by killing all x2goagents-prozesses with cron twice a day.
It's at most a workaround... not a solution... We'll have to check
that X2go upstream-wise.
- The home-directories of my users fill with log-files like these : /home/pcag01/.x2go/S-es01-119-1313081349_stDKDE_dp24 and they are not deleted.
Over the last weekend I have added code that will (at least) remove
these session directories in case the session has finished
successfully (session meaning here: if the executed command of the
session returns with a clean exitcode).
- My logfiles in /var/log like message or syslog grow up to a few hundred MB for example with entries like these: Sep 22 06:30:24 ltspserver01 ltspserver01 console-kit-daemon[24530]: WARNING: Record was not written to disk (File too large) Sep 22 06:30:55 ltspserver01 last message repeated 606 times
Is there anyone who understands what my server makes? <snip> I can confirm the problem but I've never taken the time to investigate why X2Go does that and how to address it - John
The problem under 3)... ist that X2go specific? John, have you seen
that one, too? Under what conditions???G<snp> I haven't seen three but I haven't looked for it. My guess it is related to running out of resources but I haven't thought it through - John
-
John A. Sullivan III -
Mike Gabriel -
Thomas Ritter