Hello everybody,
I've running X2Go (v4.0.1.20) on CentoOS6 and it works quite well.
Last week I was out of office and I kept a session running on the "server". When I came back, I was not able to connect to session again. The client stucks after starting the connection, after >1/2h I killed the client. When I try to connect afterwards, I have to suspend the session 1st, then I can connect, but the client stucks again.
On the server /var/log/messages is blown up by lot of this messages: Nov 17 09:18:32 lmesim138 /usr/bin/x2gosuspend-session: session with ID lmegast5-50-1507636342_stDGNOME_dp32 has been suspended successfully Nov 17 09:18:32 lmesim138 /usr/bin/x2gosuspend-session: session with ID lmegast5-50-1507636342_stDGNOME_dp32 has been suspended successfully Nov 17 09:18:42 lmesim138 /usr/bin/x2gosuspend-session: session with ID lmegast5-50-1507636342_stDGNOME_dp32 has been suspended successfully
This message is added even if no client is trying to connect or disconnect.
Taking a look on the open files (lsof) shows that the session log file in /tmp has been deleted meanwhile: /tmp/.x2go-lmegast5/C-lmegast5-50-1507636342_stDGNOME_dp32/session.log (deleted) (background: "old" files in /tmp are deleted automatically after 3 weeks of beeing not used/touched)
I assume thats the reason why I cannot connect to the session again.
Do you have an idea how I might make the session working again or overcome the problem in general? (I sometimes have simulations running for a longer time and the result/evaluation will be done and shown within this session)
Best regards, Markus