Just go on the X2Go server and do x2goterminate-session <session id>
For exmple, in your case :
x2goterminate-session trainer1-51-1502204631_stDXFCE_dp32
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Qianqian Fang" <fangqq@gmail.com> À: x2go-user@lists.x2go.org Envoyé: Mercredi 23 Août 2017 00:40:46 Objet: [X2Go-User] How to purge zombie sessions after a user is deleted
I am not sure if this is a bug, but it looks like x2gocleansessions keeps trying to open some previously saved session created by a deleted user. This leaves a log like the following in the /var/log/auth.log and this log continues to add in an infinite loop
Aug 22 18:17:32 taote su[6146]: - ??? root:trainer7 Aug 22 18:17:32 taote su[6147]: No passwd entry for user 'trainer7' Aug 22 18:17:32 taote su[6147]: FAILED su for trainer7 by root
if I kill the x2gocleansessions process, the log stops.
if I run
sudo /usr/sbin/x2golistsessions_root
I can see the two zombie sessions
20580|trainer1-51-1502204631_stDXFCE_dp32|51|taote|S|2017-08-08T11:03:51|...|10.15.159.9|33463|33464|2017-08-08T17:56:15|trainer1|1236642|33465| 10905|trainer7-52-1502214187_stDXFCE_dp32|52|taote|S|2017-08-08T13:43:07|...|10.15.138.221|61994|61995|2017-08-08T13:59:17|trainer7|1227086|61996|
but could not find a way to purge then. Those two user accounts (trainer1 and trainer7) were created for an event previously, but after the event, both accounts have been deleted.
A reboot does not solve the issue. As long as you run "sudo service x2goserver restart", the error log comes back and keeps repeating itself.
Can someone suggest a way to purge these zombie sessions so that I don't see the error logs again?
thanks
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you