Re: [X2Go-User] x2go stops working on some Ubuntu 14.04 boxes
Qiangian, Try removing the sessions on the server side and then see what happens on the client. I had a similar issue and ended up doing the package upgrades you've already done on the server end and then updating the client as well. sudo rm -f /var/lib/x2go/x2go_sessions sudo x2godbadmin --createdb Thanks, Steve On 03/26/2018 04:11 PM, Qianqian Fang wrote: > On 03/26/2018 03:53 PM, Mihai Moldovan wrote: >> Please make sure that nx-libs 3.5.99.16 is installed on the server side. >> This sounds like a typical incarnation of the DPMS bug, fixed with >> nx-libs 3.5.99.15. > > thanks Mihai > > > I confirm that the server giving the first error, i.e. "The remote > proxy closed the connection while negotiating..." > has indeed installed an older version of libnx-x11 (3.5.0.33~710). > > after letting apt-get to upgrade the nx libraries and x2go packages, > I saw the libnx-x11 was replaced by a new package named libnx-x11-6, and > the version is now 3.5.99.16. However, now I start seeing the 2nd error > message on those machines, i.e. "connection failed". > >> However, this doesn't sound like it. Normally the DPMS bug only manifests >> after >> a pretty long time (say, an hour or 1.5h, depending on DPMS settings), but >> not >> right away after starting the session. I haven't yet seen such an error >> message >> yet. It's possible that it's caused by the session repositioning on non-first >> displays/nxagent crashing bug as fixed with nx-libs 3.5.99.16, but normally >> that >> incarnates differently (i.e., nxagent is being started successfully, but then >> dies quickly while starting the session without a client-side error message). > > here is a dump of the session.log file under the failed session: > > > |NXAGENT - Version 3.5.99.16|| > || > ||Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com)|| > |||| > ||See https://github.com/ArcticaProject/nx-libs for more information.|| > || > ||Info: Agent running with pid '17844'.|| > ||Session: Starting session at 'Mon Mar 26 16:56:11 2018'.|| > ||Error: Aborting session with 'Unable to open display > 'nx/nx,options=/tmp/.x2go-fangq/C-fangq-50-1522097770_stDXFCE_dp24/options:50''.|| > ||Session: Aborting session at 'Mon Mar 26 16:56:11 2018'.|| > ||Session: Session aborted at 'Mon Mar 26 16:56:11 2018'.|| > | > > > strangely, the x2go window reports something differently, it says (see > attached screenshot) > > |"PANIC!" Failure negotiating the session in stage 7|| > ||...|| > ||Wrong version or invalid session authentication cookie.|| > |||| > | > > are these two error messages caused by a single issue or multiple? > > I've already restarted x2gosever, but no dice. any other files that I > need to reset/clear? > > thanks > > Qianqian > >> >> >> Mihai >> > > > > ___ > 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
Re: [X2Go-User] open another customizing Port Forward thought the SSH Connection to the x2go Server
On 03/19/2018 09:37 AM, Stefan Baur wrote: > Am 19.03.2018 um 15:28 schrieb Steven Spencer: >> Thomas, >> >> We always do our port-forwarding for x2go via a firewall appliance, but >> you can do this pretty easily by implementing a firewall on the Linux >> box and doing your port-forwarding from there. On the client side, you >> simply specify the port for ssh (maybe 222 or 223 or something) and then >> redirect that port on the server's firewall to the actual ssh port (22). >> >> You can do a quick Google search on port-forwarding with IPTables or ufw >> to get a feel for how this is done. > I think you totally misunderstood what Thomas is asking for. > He doesn't want to forward/change the ssh port X2Go uses to connect to > the server, but rather an equivalent to > > ssh -L1234:some.host:3456 user@x2goserver > > Kind Regards, > Stefan Baur I apologize. That's what happens when you read too quickly. :/ > > > ___ > 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
Re: [X2Go-User] open another customizing Port Forward thought the SSH Connection to the x2go Server
On 03/16/2018 08:24 AM, Feustel, Thomas wrote: > > Hi, > > Is it possible to open an induvial port forward from the client > machine to the x2go server? > > I need this for a windows software to connect to the Linux server. > > > > My first approach wars to use on the client a ssh_config, but the > client creates the connection directly from the x2go client > application with some ssh libs. > > So ok, the next approach wars to use the ssh_config on the Linux > site, because for the printer and the file connection, the server > open a ssh connection to a ssh-Daemon on the Client site. But the ssh > connection use the option “ClearAllForwardings”, so the forwards on a > config-file are not working. > > > > So someone have an idea for this topic? > > > > Greetings > > > > > > ___ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user Thomas, We always do our port-forwarding for x2go via a firewall appliance, but you can do this pretty easily by implementing a firewall on the Linux box and doing your port-forwarding from there. On the client side, you simply specify the port for ssh (maybe 222 or 223 or something) and then redirect that port on the server's firewall to the actual ssh port (22). You can do a quick Google search on port-forwarding with IPTables or ufw to get a feel for how this is done. 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
[X2Go-User] x2go problems
Greetings, 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
Re: [X2Go-User] x2go problems - Ubuntu 16.04 - before and after new version upgrade
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 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] x2go problems - Ubuntu 16.04 - before and after new version upgrade
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.shney...@phoca-gmbh.de> > Copyright (c) 2014-2016 Ulrich Sibiller <ul...@gmx.de> > Copyright (c) 2014-2016 Mihai Moldovan <io...@ionic.de> > Copyright (c) 2011-2016 Mike Gabriel <mike.gabr...@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 >>
Re: [X2Go-User] x2go problems - Ubuntu 16.04 - before and after new version upgrade
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.shney...@phoca-gmbh.de> Copyright (c) 2014-2016 Ulrich Sibiller <ul...@gmx.de> Copyright (c) 2014-2016 Mihai Moldovan <io...@ionic.de> Copyright (c) 2011-2016 Mike Gabriel <mike.gabr...@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
[X2Go-User] x2go problems - Ubuntu 16.04 - before and after new version upgrade
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
