I have a user with a frozen x2go session. In the logs I get the following message for the users session: usr/bin/x2gosetkeyboard: Waiting for /home/username/.x2go/C-username-50-1490056089_stDKDE_dp32/keyboard to appear.
I'm thinking this might be the problem, but does anyone have any experience with this? I'm thinking I may have to terminate their session, which isn't great since they were crunching data for research. The server version is: x2goagent: 3.5.0.32 x2goserver: 4.0.1.20 x2goserver-extensions: 4.0.1.20 x2goserver-fmbindings: 4.0.1.20 x2goserver-printing: 4.0.1.20 x2goserver-xsession: 4.0.1.20
This is all running on RHEL 6.8. I don't know which client version the user has.
Am 27.03.2017 um 18:55 schrieb Thackeray, Neil L:
I have a user with a frozen x2go session. In the logs I get the following message for the users session: usr/bin/x2gosetkeyboard: Waiting for /home/username/.x2go/C-username-50-1490056089_stDKDE_dp32/keyboard to appear.
I’m thinking this might be the problem, but does anyone have any experience with this?
Some wild guesses as to why that file isn't appearing:
User over disk quota? Disk full? No free inodes left?
Does
test -d /home/username/.x2go/C-username-50-1490056089_stDKDE_dp32 &&
echo yes
return a "yes"?
Also, what happens when the user selects "leave keyboard unconfigured" upon reconnecting?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
-
Stefan Baur -
Thackeray, Neil L