On 11/13/2017 06:50 PM, K. Reinhold Trier wrote: > last Thursday after an automatic update of the x2go-server our clients didn't > receive any more answer from the server.
Yes, X2Go Server 4.0.1.21 was buggy when used with FQDN host names. > This morning, after an other automatic update of > the x2go-software, I noticed that clients could connect again 4.0.1.22 fixed this issue. > - but after an > unacceptable delay of about 5 minutes. Here our data: > We are on Ubuntu 16.04.3 LTSUbuntu 16.04.3 LTS > When starting x2goclient on a ubuntu client, after about 5 minutes it shows > the > details: It looks like it's taking a long time to find an available DISPLAY number. Given that you're at 389 already, that's cause for concern. I don't think that you have that many sessions running. x2golistsessions_root (executed as root) only lists a few, if any, right? It looks like we have a problem in the sense that if a session fails to start up correctly, it's not evicted from the sessions database. It won't show up in x2golistsessions(_root) either, which makes this even more opaue to users. You probably started a lot of failed sessions in the past few days (well, you or your users), which accumulated in the database and were never cleaned up. To remedy this, please terminate all sessions. Afterwards, as root, execute x2godbadmin --createdb. That will re-initialize the database and get rid of stale failed sessions. Startup should be faster afterwards. If it's still not, something else that isn't easily visible is wrong. Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
