Dear all,
I have been using X2Go client in the current environment for quite a while now without issues. Seemingly all of sudden today an outage happened where X2Go will no longer launch any applications.
The connection seems to succeed in the backend: [cid:image001.png@01D3C558.EB0F51C0]
However, the client closes the connection before anything happens. Running the client with the debug terminal shows these messages: [cid:image002.png@01D3C559.58693F10]
I've validated that I can SSH to the server using other tools and start the X11 applications from command line directly.
Any guidance or pointers to figure out why X2Go stopped working would be greatly appreciated.
Thank you, Ivan G.
Ivan Gomez Consultant Zencos Consulting<http://www.zencos.com/> igomez@zencos.com<mailto:igomez@zencos.com> mobile: (919) 576-0614
The information in this e-mail and any attached files is confidential. It is intended solely for the use of the addressee. Any unauthorized disclosure or use is prohibited. If you are not the intended recipient of the message, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. The views of the author may not necessarily reflect those of the company.
EDIT: Included environment details Apologies. Forgot to include this information in the original email
From: Ivan Gomez Sent: Monday, March 26, 2018 11:23 PM To: x2go-user@lists.x2go.org Subject: X2Go Client suddenly failing to connect
Dear all,
Environment: Server: Red Hat Enterprise Linux Server release 7.3 (Maipo) x2goagent: 3.5.0.32 x2goserver: 4.0.1.20 x2goserver-extensions: 4.0.1.20 Client: Windows 7 & Windows 10 [cid:image003.png@01D3C5AB.5F950EC0]
I have been using X2Go client in the current environment for quite a while now without issues. Seemingly all of sudden today an outage happened where X2Go will no longer launch any applications.
The connection seems to succeed in the backend: [cid:image004.png@01D3C5AB.5F950EC0]
However, the client closes the connection before anything happens. Running the client with the debug terminal shows these messages: [cid:image005.png@01D3C5AB.5F950EC0]
I've validated that I can SSH to the server using other tools and start the X11 applications from command line directly.
Any guidance or pointers to figure out why X2Go stopped working would be greatly appreciated.
Thank you, Ivan G.
Ivan Gomez Consultant Zencos Consulting<http://www.zencos.com/> igomez@zencos.com<mailto:igomez@zencos.com> mobile: (919) 576-0614
The information in this e-mail and any attached files is confidential. It is intended solely for the use of the addressee. Any unauthorized disclosure or use is prohibited. If you are not the intended recipient of the message, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. The views of the author may not necessarily reflect those of the company.
- On 03/27/2018 03:09 PM, Ivan Gomez wrote:
*Environment:*
*Server:*
Red Hat Enterprise Linux Server release 7.3 (Maipo)
x2goagent: 3.5.0.32
x2goserver: 4.0.1.20
x2goserver-extensions: 4.0.1.20
*Client:*
* *Windows 7 & Windows 10
I have been using X2Go client in the current environment for quite a while now without issues. Seemingly all of sudden today an outage happened where X2Go will no longer launch any applications.
rpm -qa | grep -iE '(nx|x2go)'
Mihai
Hi Mihai,
Here is output from rpm -qa | grep -iE '(nx|x2go)'
libNX_X11-3.5.0.32-3.el7.x86_64
libNX_Xcomposite-3.5.0.32-3.el7.x86_64
libNX_Xdamage-3.5.0.32-3.el7.x86_64
libNX_Xdmcp-3.5.0.32-3.el7.x86_64
libNX_Xext-3.5.0.32-3.el7.x86_64
libNX_Xfixes-3.5.0.32-3.el7.x86_64
libNX_Xinerama-3.5.0.32-3.el7.x86_64
libNX_Xpm-3.5.0.32-3.el7.x86_64
libNX_Xrandr-3.5.0.32-3.el7.x86_64
libNX_Xrender-3.5.0.32-3.el7.x86_64
libNX_Xtst-3.5.0.32-3.el7.x86_64
nxagent-3.5.0.32-3.el7.x86_64
nx-libs-3.5.0.32-3.el7.x86_64
x2goagent-3.5.0.32-3.el7.x86_64
x2goserver-4.0.1.20-1.el7.x86_64
One additional detail that we discovered after further troubleshooting:
We have multiple backend servers running X2go. All servers have identical output of rpm -qa | grep -iE '(nx|x2go)', but currently 2 of them present are stuck in this state where applications won't launch while a third identical sever is not showing issues.
Thanks!
Ivan
-----Original Message----- From: Mihai Moldovan [mailto:ionic@ionic.de] Sent: Tuesday, March 27, 2018 3:26 PM To: Ivan Gomez <igomez@zencos.com>; x2go-user@lists.x2go.org Subject: Re: [X2Go-User] X2Go Client suddenly failing to connect
- On 03/27/2018 03:09 PM, Ivan Gomez wrote:
*Environment:*
*Server:*
Red Hat Enterprise Linux Server release 7.3 (Maipo)
x2goagent: 3.5.0.32
x2goserver: 4.0.1.20
x2goserver-extensions: 4.0.1.20
*Client:*
*Windows 7 & Windows 10
I have been using X2Go client in the current environment for quite a
while now without issues. Seemingly all of sudden today an outage
happened where X2Go will no longer launch any applications.
rpm -qa | grep -iE '(nx|x2go)'
Mihai
One new update on this issue:
Updated x2gosever on one of the servers that was showing the issue to x2goserver-4.0.1.22-2.el7.x86_64. After the update, access through that server started working again.
Any guidance to understand the root cause would still be greatly appreciated.
Thanks, Ivan G.
From: x2go-user [mailto:x2go-user-bounces@lists.x2go.org] On Behalf Of Ivan Gomez Sent: Wednesday, March 28, 2018 8:58 AM To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] X2Go Client suddenly failing to connect
This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>
Feedback<http://aka.ms/SafetyTipsFeedback>
Hi Mihai,
Here is output from rpm -qa | grep -iE '(nx|x2go)'
libNX_X11-3.5.0.32-3.el7.x86_64
libNX_Xcomposite-3.5.0.32-3.el7.x86_64
libNX_Xdamage-3.5.0.32-3.el7.x86_64
libNX_Xdmcp-3.5.0.32-3.el7.x86_64
libNX_Xext-3.5.0.32-3.el7.x86_64
libNX_Xfixes-3.5.0.32-3.el7.x86_64
libNX_Xinerama-3.5.0.32-3.el7.x86_64
libNX_Xpm-3.5.0.32-3.el7.x86_64
libNX_Xrandr-3.5.0.32-3.el7.x86_64
libNX_Xrender-3.5.0.32-3.el7.x86_64
libNX_Xtst-3.5.0.32-3.el7.x86_64
nxagent-3.5.0.32-3.el7.x86_64
nx-libs-3.5.0.32-3.el7.x86_64
x2goagent-3.5.0.32-3.el7.x86_64
x2goserver-4.0.1.20-1.el7.x86_64
One additional detail that we discovered after further troubleshooting:
We have multiple backend servers running X2go. All servers have identical output of rpm -qa | grep -iE '(nx|x2go)', but currently 2 of them present are stuck in this state where applications won't launch while a third identical sever is not showing issues.
Thanks!
Ivan
-----Original Message----- From: Mihai Moldovan [mailto:ionic@ionic.de] Sent: Tuesday, March 27, 2018 3:26 PM To: Ivan Gomez <igomez@zencos.com<mailto:igomez@zencos.com>>; x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2Go Client suddenly failing to connect
- On 03/27/2018 03:09 PM, Ivan Gomez wrote:
*Environment:*
*Server:*
Red Hat Enterprise Linux Server release 7.3 (Maipo)
x2goagent: 3.5.0.32
x2goserver: 4.0.1.20
x2goserver-extensions: 4.0.1.20
*Client:*
*Windows 7 & Windows 10
I have been using X2Go client in the current environment for quite a
while now without issues. Seemingly all of sudden today an outage
happened where X2Go will no longer launch any applications.
rpm -qa | grep -iE '(nx|x2go)'
Mihai
- On 03/28/2018 02:58 PM, Ivan Gomez wrote:
libNX_X11-3.5.0.32-3.el7.x86_64 libNX_Xcomposite-3.5.0.32-3.el7.x86_64 libNX_Xdamage-3.5.0.32-3.el7.x86_64 libNX_Xdmcp-3.5.0.32-3.el7.x86_64 libNX_Xext-3.5.0.32-3.el7.x86_64 libNX_Xfixes-3.5.0.32-3.el7.x86_64 libNX_Xinerama-3.5.0.32-3.el7.x86_64 libNX_Xpm-3.5.0.32-3.el7.x86_64 libNX_Xrandr-3.5.0.32-3.el7.x86_64 libNX_Xrender-3.5.0.32-3.el7.x86_64 libNX_Xtst-3.5.0.32-3.el7.x86_64 nxagent-3.5.0.32-3.el7.x86_64 nx-libs-3.5.0.32-3.el7.x86_64 x2goagent-3.5.0.32-3.el7.x86_64 x2goserver-4.0.1.20-1.el7.x86_64
That's the old, more or less unsupported version and additionally provided by EPEL, not by our repositories.
One new update on this issue: Updated x2gosever on one of the servers that was showing the issue to x2goserver-4.0.1.22-2.el7.x86_64. After the update, access through that server started working again. Any guidance to understand the root cause would still be greatly appreciated.
I'm afraid I can't offer a lot of help here.
You could look into ~/.x2go/C-<session-id>/session.log to see what the server-side process logged out.
At some point it must have failed to run correctly, otherwise the client-side nxproxy would have been able to connect successfully.
Debugging such issues is always difficult.
Mihai
Hi Mihai,
That's the old, more or less unsupported version and additionally provided by EPEL, not by our repositories.
Interesting. Thank you for pointing that out. I would like to correct this to run with a supported stack then.
Apologies if I'm missing something obvious, but is there documentation that shows how to install from your repositories on RHEL 7?
I installed x2goserver following the instructions from the wiki<https://wiki.x2go.org/doku.php/doc:installation:x2goserver>:
RHEL 7
Add the EPEL repository:
EPEL Installation Intructions<https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F>
Check that you have activated the "optional" channel:
sudo subscription-manager repos --list
If the optional channel for your base channel is not active, activate it.
sudo subscription-manager repos --enable=rhel-7-server-optional-rpms
Or use the RHNS web interface to activate the channel "RHEL Server Optional"
Then
sudo yum install x2goserver x2goserver-xsession
Looking through my yum history confirms what you said about the software coming from EPEL:
Transaction ID : 23
Begin time : Wed Oct 11 16:16:03 2017
Begin rpmdb : 732:22a7d0c0c35d36230fbfc3bd93be2adab6d0679c
End time : 16:16:09 2017 (6 seconds)
End rpmdb : 768:eb5810a8c8048bd3c405c89d5589f03c7aa209a9
User : root <root>
Return-Code : Success
Command Line : install x2goserver -y
Transaction performed with:
Installed rpm-4.11.3-21.el7.x86_64 @rhel-7-server-rpms/7.3
Installed subscription-manager-1.17.15-1.el7.x86_64 @rhel-7-server-rpms/7.3
Installed yum-3.4.3-150.el7.noarch @rhel-7-server-rpms/7.3Packages Altered:
Dep-Install bc-1.06.95-13.el7.x86_64 @rhel-7-server-rpms
Dep-Install fuse-sshfs-2.5-1.el7.x86_64 @epel
Dep-Install libNX_X11-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xcomposite-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xdamage-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xdmcp-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xext-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xfixes-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xinerama-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xpm-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xrandr-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xrender-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libNX_Xtst-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libXcomp-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libXcompext-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libXcompshad-3.5.0.32-3.el7.x86_64 @epel
Dep-Install libXfont-1.5.2-1.el7.x86_64 @rhel-7-server-rpms
Dep-Install nx-libs-3.5.0.32-3.el7.x86_64 @epel
Dep-Install nxagent-3.5.0.32-3.el7.x86_64 @epel
Dep-Install perl-Capture-Tiny-0.24-1.el7.noarch @rhel-7-server-optional-rpms
Dep-Install perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 @rhel-7-server-rpms
Dep-Install perl-Compress-Raw-Zlib-1:2.061-4.el7.x86_64 @rhel-7-server-rpms
Dep-Install perl-Config-Simple-4.59-15.el7.noarch @rhel-7-server-optional-rpms
Dep-Install perl-DBD-SQLite-1.39-3.el7.x86_64 @rhel-7-server-rpms
Dep-Install perl-DBI-1.627-4.el7.x86_64 @rhel-7-server-rpms
Dep-Install perl-File-BaseDir-0.03-14.el7.noarch @epel
Dep-Install perl-File-Which-1.09-12.el7.noarch @rhel-7-server-optional-rpms
Dep-Install perl-IO-Compress-2.061-2.el7.noarch @rhel-7-server-rpms
Dep-Install perl-Net-Daemon-0.48-5.el7.noarch @rhel-7-server-rpms
Dep-Install perl-PlRPC-0.2020-14.el7.noarch @rhel-7-server-rpms
Dep-Install perl-Sys-Syslog-0.33-3.el7.x86_64 @rhel-7-server-rpms
Dep-Install pwgen-2.07-1.el7.x86_64 @epel
Dep-Install x2goagent-3.5.0.32-3.el7.x86_64 @epel
Install x2goserver-4.0.1.20-1.el7.x86_64 @epel
Dep-Install xorg-x11-font-utils-1:7.5-20.el7.x86_64 @rhel-7-server-rpms
Dep-Install xorg-x11-fonts-misc-7.5-9.el7.noarch @rhel-7-server-rpmsThanks,
Ivan G.
-----Original Message----- From: Mihai Moldovan [mailto:ionic@ionic.de] Sent: Wednesday, March 28, 2018 7:22 PM To: Ivan Gomez <igomez@zencos.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] X2Go Client suddenly failing to connect
- On 03/28/2018 02:58 PM, Ivan Gomez wrote:
libNX_X11-3.5.0.32-3.el7.x86_64
libNX_Xcomposite-3.5.0.32-3.el7.x86_64
libNX_Xdamage-3.5.0.32-3.el7.x86_64
libNX_Xdmcp-3.5.0.32-3.el7.x86_64
libNX_Xext-3.5.0.32-3.el7.x86_64
libNX_Xfixes-3.5.0.32-3.el7.x86_64
libNX_Xinerama-3.5.0.32-3.el7.x86_64
libNX_Xpm-3.5.0.32-3.el7.x86_64
libNX_Xrandr-3.5.0.32-3.el7.x86_64
libNX_Xrender-3.5.0.32-3.el7.x86_64
libNX_Xtst-3.5.0.32-3.el7.x86_64
nxagent-3.5.0.32-3.el7.x86_64
nx-libs-3.5.0.32-3.el7.x86_64
x2goagent-3.5.0.32-3.el7.x86_64
x2goserver-4.0.1.20-1.el7.x86_64
That's the old, more or less unsupported version and additionally provided by EPEL, not by our repositories.
One new update on this issue:
Updated x2gosever on one of the servers that was showing the issue to x2goserver-4.0.1.22-2.el7.x86_64. After the update, access through that server started working again.
Any guidance to understand the root cause would still be greatly appreciated.
I'm afraid I can't offer a lot of help here.
You could look into ~/.x2go/C-<session-id>/session.log to see what the server-side process logged out.
At some point it must have failed to run correctly, otherwise the client-side nxproxy would have been able to connect successfully.
Debugging such issues is always difficult.
Mihai
-
Ivan Gomez -
Mihai Moldovan