Greetings,
I sent this yesterday, but was not a member of the list, so wasn't sure if it would end up being approved and posted or not. Here's the content of that message and I apologize if this is a duplicate:
We use x2go extensively for some access to some Ubuntu based LTSP servers. Suddenly over the last two days, we get the following in the client:
"The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server."
And on the server we are trying to connect to, we see this in the logs:
/usr/bin/x2goresume-session: client [ip.address.of.client] has successfully resumed session with ID kscadmin-51-1520534328_stDMATE_dp24
/usr/bin/x2gosetkeyboard: /home/ksca0dmin/.x2go/C-kscadmin-51-1520534328_stDMATE_dp24/keyboard did not appear within 30s after agent startup
We are never able to connect. This happens even on all servers that we connect to and includes older server versions:
x2goagent: 3.5.0.33 x2goserver: 4.0.1.22 x2goserver-extensions: 4.0.1.22 x2goserver-xsession: 4.0.1.22
As well as newer ones:
x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-fmbindings: 4.1.0.0 x2goserver-printing: 4.1.0.0 x2goserver-x2goagent: 3.5.99.14 x2goserver-xsession: 4.1.0.0
Unfortunately, the clients are now updated as well trying to fix this issue, but they were failing on the older client version as well:
X2Go Client v. 4.1.1.1 (Qt - 4.8.7)
Any help would be appreciated.
Thanks,
--
Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010
New information. When the client fails, if I can catch it before it totally closes out and goes back to the login and then click on session details. I get this:
NXPROXY - Version 3.5.99.15
Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com) Copyright (c) 2008-2014 Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> Copyright (c) 2014-2016 Ulrich Sibiller <uli42@gmx.de> Copyright (c) 2014-2016 Mihai Moldovan <ionic@ionic.de> Copyright (c) 2011-2016 Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com)
NXCOMP, NX protocol compression and NX extensions to this software are copyright of the aforementioned persons and companies.
Redistribution and use of the present software is allowed according to terms specified in the file LICENSE.nxcomp which comes in the source distribution.
All rights reserved.
NOTE: This software has received contributions from various other contributors, only the core maintainers and supporters are listed as copyright holders. Please contact us, if you feel you should be listed as copyright holder, as well.
NX protocol compression is derived from DXPC project.
Copyright (c) 1995,1996 Brian Pane Copyright (c) 1996,1997 Zachary Vonler and Brian Pane Copyright (c) 1999 Kevin Vigor and Brian Pane Copyright (c) 2000,2003 Gian Filippo Pinzari and Brian Pane
All rights reserved.
See https://github.com/ArcticaProject/nx-libs for more information.
Info: Proxy running in server mode with pid '12285'. Session: Starting session at 'Fri Mar 9 08:41:51 2018'. Info: Using errors file '/home/sspencer/.x2go/S-kscadmin-51-1520534328_stDMATE_dp24/sessions'. Info: Using stats file '/home/sspencer/.x2go/S-51/stats'. Loop: WARNING! Overriding auxiliary X11 port with new value '1'. Warning: Overriding auxiliary X11 port with new value '1'. Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0. Info: Connecting to remote host 'localhost:46965'. Info: Connected to remote proxy on FD#5. Loop: PANIC! The remote NX proxy closed the connection. Error: The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Error: Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Fri Mar 9 08:41:52 2018'. Session: Session terminated at 'Fri Mar 9 08:41:52 2018'.
On 03/09/2018 08:18 AM, Steven Spencer wrote:
Greetings,
I sent this yesterday, but was not a member of the list, so wasn't sure if it would end up being approved and posted or not. Here's the content of that message and I apologize if this is a duplicate:
We use x2go extensively for some access to some Ubuntu based LTSP servers. Suddenly over the last two days, we get the following in the client:
"The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server."
And on the server we are trying to connect to, we see this in the logs:
/usr/bin/x2goresume-session: client [ip.address.of.client] has successfully resumed session with ID kscadmin-51-1520534328_stDMATE_dp24
/usr/bin/x2gosetkeyboard: /home/ksca0dmin/.x2go/C-kscadmin-51-1520534328_stDMATE_dp24/keyboard did not appear within 30s after agent startup
We are never able to connect. This happens even on all servers that we connect to and includes older server versions:
x2goagent: 3.5.0.33 x2goserver: 4.0.1.22 x2goserver-extensions: 4.0.1.22 x2goserver-xsession: 4.0.1.22
As well as newer ones:
x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-fmbindings: 4.1.0.0 x2goserver-printing: 4.1.0.0 x2goserver-x2goagent: 3.5.99.14 x2goserver-xsession: 4.1.0.0
Unfortunately, the clients are now updated as well trying to fix this issue, but they were failing on the older client version as well:
X2Go Client v. 4.1.1.1 (Qt - 4.8.7)
Any help would be appreciated.
Thanks,
-- 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 x2go-user@lists.x2go.org 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
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.
On 03/09/2018 09:16 AM, Steven Spencer wrote:
New information. When the client fails, if I can catch it before it totally closes out and goes back to the login and then click on session details. I get this:
NXPROXY - Version 3.5.99.15
Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com) Copyright (c) 2008-2014 Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> Copyright (c) 2014-2016 Ulrich Sibiller <uli42@gmx.de> Copyright (c) 2014-2016 Mihai Moldovan <ionic@ionic.de> Copyright (c) 2011-2016 Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com)
NXCOMP, NX protocol compression and NX extensions to this software are copyright of the aforementioned persons and companies.
Redistribution and use of the present software is allowed according to terms specified in the file LICENSE.nxcomp which comes in the source distribution.
All rights reserved.
NOTE: This software has received contributions from various other contributors, only the core maintainers and supporters are listed as copyright holders. Please contact us, if you feel you should be listed as copyright holder, as well.
NX protocol compression is derived from DXPC project.
Copyright (c) 1995,1996 Brian Pane Copyright (c) 1996,1997 Zachary Vonler and Brian Pane Copyright (c) 1999 Kevin Vigor and Brian Pane Copyright (c) 2000,2003 Gian Filippo Pinzari and Brian Pane
All rights reserved.
See https://github.com/ArcticaProject/nx-libs for more information.
Info: Proxy running in server mode with pid '12285'. Session: Starting session at 'Fri Mar 9 08:41:51 2018'. Info: Using errors file '/home/sspencer/.x2go/S-kscadmin-51-1520534328_stDMATE_dp24/sessions'. Info: Using stats file '/home/sspencer/.x2go/S-51/stats'. Loop: WARNING! Overriding auxiliary X11 port with new value '1'. Warning: Overriding auxiliary X11 port with new value '1'. Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0. Info: Connecting to remote host 'localhost:46965'. Info: Connected to remote proxy on FD#5. Loop: PANIC! The remote NX proxy closed the connection. Error: The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Error: Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Fri Mar 9 08:41:52 2018'. Session: Session terminated at 'Fri Mar 9 08:41:52 2018'.
On 03/09/2018 08:18 AM, Steven Spencer wrote:
Greetings,
I sent this yesterday, but was not a member of the list, so wasn't sure if it would end up being approved and posted or not. Here's the content of that message and I apologize if this is a duplicate:
We use x2go extensively for some access to some Ubuntu based LTSP servers. Suddenly over the last two days, we get the following in the client:
"The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server."
And on the server we are trying to connect to, we see this in the logs:
/usr/bin/x2goresume-session: client [ip.address.of.client] has successfully resumed session with ID kscadmin-51-1520534328_stDMATE_dp24
/usr/bin/x2gosetkeyboard: /home/ksca0dmin/.x2go/C-kscadmin-51-1520534328_stDMATE_dp24/keyboard did not appear within 30s after agent startup
We are never able to connect. This happens even on all servers that we connect to and includes older server versions:
x2goagent: 3.5.0.33 x2goserver: 4.0.1.22 x2goserver-extensions: 4.0.1.22 x2goserver-xsession: 4.0.1.22
As well as newer ones:
x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-fmbindings: 4.1.0.0 x2goserver-printing: 4.1.0.0 x2goserver-x2goagent: 3.5.99.14 x2goserver-xsession: 4.1.0.0
Unfortunately, the clients are now updated as well trying to fix this issue, but they were failing on the older client version as well:
X2Go Client v. 4.1.1.1 (Qt - 4.8.7)
Any help would be appreciated.
Thanks,
-- 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 x2go-user@lists.x2go.org 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 x2go-user@lists.x2go.org 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
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
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 x2go-user@lists.x2go.org 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
Am 09.03.2018 um 19:34 schrieb Steven Spencer:
... 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.
Seeing as your Mail has been without a reply in the last 10 days, and you posted from your employer's E-Mail address, may I suggest you ask your employer if they might want to contract us for some consulting and hands-on debugging?
<shameless plug> X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame. What makes my company special is, IMHO:
- I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me.
- As far as I know, we are the only company providing X2Go support that isn't a one-man-show. Oh, and we already have US customers.
- We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers.
Our hourly rate for consultancy work and fixing issues outside of a support contract is 125 EUR. With a support contract, you get guaranteed response times and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>
Kind Regards, Stefan Baur
-- 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
Am 09.03.2018 um 15:18 schrieb Steven Spencer:
I sent this yesterday, but was not a member of the list, so wasn't sure if it would end up being approved and posted or not. Here's the content of that message and I apologize if this is a duplicate:
Thank you for signing up. Usually, we approve messages in the course of a few days (and also whitelist the senders, so subsequent mails don't clog up the moderation queue again), but we're currently down to one volunteer (i.e. me) regularly taking care of the lists, and since I had two family members with health issues around, I was unable to act in time. Mihai was so kind to jump in and clean up the queue a few days ago.
Thank you for your patience and understanding.
Kind Regards, Stefan Baur
-- 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
-
Mario Theodoridis -
Stefan Baur -
Steven Spencer