Mario, Thanks for the threads, but they don't /seem/ to point to the issue. I will look more closely at them, however, as I thought I had this issue resolved with the deletion of the x2go sessions on the server side and then the re-creation of the database, but this seems to only fix it temporarily. The problem then starts all over again. Any help is appreciated. I will continue to dig.
On 03/09/2018 09:54 AM, Mario Theodoridis wrote: > On 09/03/18 16:30, Steven Spencer wrote: >> I may have found my own answer when I finally got to see the session >> detail below. It led me to a post describing how the session data on >> a server can get corrupted. My only question: how can 14 servers in >> different locations get corrupted all at the same time? Here's what >> I've run to fix 2 of the 14 servers so far: >> >> $ sudo rm -f /var/lib/x2go/x2go_sessions >> $ sudo x2godbadmin --createdb >> Hopefully, I won't need to post about this issue again and maybe this >> information will be helpful to someone else. > Steven, > > i'm not sure these issues relate to you, but have you consulted the > recent list archives? > http://lists.x2go.org/pipermail/x2go-user/2018-March/date.html > > Maybe something like > https://github.com/ArcticaProject/nx-libs/issues/671#issuecomment-370715419 > addresses your issues, too. > > -- > Mit freundlichen Grüßen/Kind regards > > Mario Theodoridis > > > _______________________________________________ > x2go-user mailing list > [email protected] > https://lists.x2go.org/listinfo/x2go-user -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010
_______________________________________________ x2go-user mailing list [email protected] https://lists.x2go.org/listinfo/x2go-user
