Am 31.10.18 um 20:16 schrieb David Barron:
Stefan, I've made a few discoveries since I sent the email.
First, I was not aware that x2golistsessions only shows the sessions for the person running it. When I run it as me I do see my suspended sessions, so that's good.
If you want an overview over all sessions on the server, then run:
x2golistsessions_root
(as the name indicates, this requires a root account)
Second all the X2GoServers are using the same session database. PostgreSQL is running on the login server and the 3 servers where the applications run all access the same data.
And the home directories are shared between all the servers.
Still, even though the sessions as suspended they are not being started. To be sure, I've cleaned them all out using x2goterminatesession, then started a new session and suspended it. But when I try to execute the same session I am getting a new one, not the suspended one.
Are you seeing the suspended session as well as the running one in the session list?
Any other thoughts?
Yes, is the problem also present when you try to use the broker via SSH instead of HTTP?
Did you run x2gobroker-keygen on the broker server?
Did you invoke x2go-pubkeyauthorizer with the proper parameters on all required machines? If so, you should have the same authorized_keys file in /var/lib/x2gobroker/.ssh/ on the three servers as well as on the broker.
Have you added the users via x2godbadmin --adduser USERNAME_GOES_HERE
-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