Hi,
last Thursday after an automatic update of the x2go-server our clients didn't receive any more answer from the server. We had to switch to vnc to get our workstations connected again. This morning, after an other automatic update of the x2go-software, I noticed that clients could connect again - 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:
NXPROXY - Version 3.5.0
Info: Proxy running in client mode with pid '25793'.
Session: Starting session at 'Mon Nov 13 18:28:30 2017'.
Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0.
Info: Connecting to remote host 'localhost:42485'.
Info: Connection to remote proxy 'localhost:42485' established.
Info: Connection with remote proxy completed.
Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using cache parameters 4/4096KB/8192KB/8192KB.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_24'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: No suitable cache file found.
Info: Forwarding X11 connections to display ':0'.
Session: Session started at 'Mon Nov 13 18:28:31 2017'.
Info: Established X server connection.
Info: Using shared memory parameters 0/0K
Now the client windows opens. To give more information about our installation: dpkg -l|grep x2go yields: ii cups-x2go 3.0.1.3-1 all Virtual X2Go printer for CUPS ii x2goagent 2:3.5.0.33-0~710~ubuntu16.04.1 all X2Go agent ii x2goclient 4.1.1.0-0~1679~ubuntu16.04.1 amd64 X2Go Client application (Qt4) ii x2golxdebindings 1.0.2.4-0~70~ubuntu16.04.1 all LXDE bindings for X2Go ii x2gomatebindings 0.0.1.5-0~203~ubuntu16.04.1 amd64 X2Go MATE bindings and MIME types ii x2goserver 4.0.1.22-0~1197~ubuntu16.04.1 amd64 X2Go server daemon scripts ii x2goserver-extensions 4.0.1.22-0~1197~ubuntu16.04.1 all X2Go server daemon scripts (extensions) ii x2goserver-printing 4.0.1.22-0~1197~ubuntu16.04.1 all X2Go server daemon scripts (printing) ii x2goserver-xsession 4.0.1.22-0~1197~ubuntu16.04.1 all X2Go server daemon scripts (Xsession runner)
I extracted the relevant entries in syslog during that process. They are:
Nov 13 12:12:35 goho /usr/bin/x2goumount-session[37611]: successfully unmounted "/tmp/.x2go-name/media/disk/_home_reinhold_MiniUbuntu" Nov 13 12:12:35 goho /usr/bin/x2goumount-session[37611]: successfully unmounted "/tmp/.x2go-name/media/disk/_home_reinhold_Dokumente" Nov 13 12:12:36 goho /usr/bin/x2goumount-session[37611]: ERROR: failed to unmount "/tmp/.x2go-name/spool/C-name-389-1510571109_stDICEWM_dp24" Nov 13 12:16:21 goho /usr/sbin/x2gocleansessions[3351]: name-389-1510571780_stDICEWM_dp24: state file for this session does not exist: /tmp/.x2go-name/C-name-389-1510571780_stDICEWM_dp24/state Nov 13 12:16:21 goho /usr/bin/x2gostartagent: successfully started X2Go agent session with ID name-389-1510571780_stDICEWM_dp24 Nov 13 12:16:25 goho /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="icewm-session" Nov 13 12:16:25 goho /usr/bin/x2goruncommand: dbus wrapper available as /usr/bin/dbus-run-session Nov 13 12:16:31 goho /usr/bin/x2gosetkeyboard: Setting X keyboard according to /home/name/.x2go/C-name-389-1510571780_stDICEWM_dp24/keyboard Nov 13 12:21:15 goho /usr/bin/x2goumount-session[27991]: ERROR: failed to unmount "/tmp/.x2go-name/spool/C-name-389-1510571780_stDICEWM_dp24"
And looking for the processes with ps -ef|grep x2go at the beginning:
name 38975 38936 0 12:13 ? 00:00:00 bash -l -c echo "X2GODATABEGIN:0b144655-d1b7-4fdf-9dd8-a3b6483c2c32"; export PATH= ... name 38976 38975 0 12:13 ? 00:00:00 /bin/bash /usr/bin/x2gostartagent 1800x1100 adsl 16m-jpeg-9 unix-kde-depth_24 de auto 1 D ICEWM both
And then, some minutes later:
name 20337 1 0 12:16 ? 00:00:00
/usr/lib/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp
-nolisten tcp -dpi 96 -D -auth /home/name/.Xauthority -geometry ...
name 20547 38936 0 12:16 ? 00:00:00 bash -l -c echo
"X2GODATABEGIN:f57debe6-7893-4214-8344-eb59d431ddaa"; export PATH= ...
name 20548 20547 5 12:16 ? 00:00:00 /usr/bin/perl
/usr/bin/x2gomountdirs dir name-389-1510571780_stDICEWM_dp24 reinhold ...
name 20569 1 0 12:16 ? 00:00:00 ssh -x -a
-oClearAllForwardings=yes -oServerAliveInterval=300
-oIdentityFile=/home/name/.x2go/ssh/key.VE6405 -oUserKnownHostsFile= ...
name 20571 1 0 12:16 ? 00:00:00 /bin/bash
/usr/bin/x2goruncommand 389 20337 name-389-1510571780_stDICEWM_dp24
43965 icewm-session nosnd D
name 20600 20337 0 12:16 ? 00:00:00
/usr/lib/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp
-nolisten tcp -dpi 96 -D -auth /home/name/.Xauthority -geometry ...
name 20688 20571 0 12:16 ? 00:00:00 /bin/bash
/usr/bin/x2gosetkeyboard
name 20769 20571 0 12:16 ? 00:00:00 /usr/bin/dbus-run-session
/etc/x2go/Xsession
name 20771 20769 0 12:16 ? 00:00:00 /bin/sh /etc/x2go/Xsession
name 20805 20771 0 12:16 ? 00:00:00 xrdb -merge
/etc/x2go/Xresources/x11-common
name 20814 1 0 12:16 ? 00:00:00 sshfs -o
idmap=user,uid=1181,gid=100,default_permissions,ServerAliveInterval=300,IdentityFile=/home/name/.x2go/ssh/key.VE6405,UserKnownHostsFile=
...
name 20878 20548 0 12:16 ? 00:00:00 sh -c timeout 30 sshfs
-o idmap=user,uid=id -u,gid=id -g,default_permissions,ServerAliveInterval=300,IdentityFile=/home/name/.x2go/ssh/key.VE6405,UserKnownHostsFile=
...
name 20881 20878 0 12:16 ? 00:00:00 timeout 30 sshfs -o
idmap=user,uid=1181,gid=100,default_permissions,ServerAliveInterval=300,IdentityFile=/home/name/.x2go/ssh/key.VE6405,UserKnownHostsFile=
...
name 20882 20881 0 12:16 ? 00:00:00 sshfs -o
idmap=user,uid=1181,gid=100,default_permissions,ServerAliveInterval=300,IdentityFile=/home/name/.x2go/ssh/key.VE6405,UserKnownHostsFile=
...
name 20886 1 0 12:16 ? 00:00:00 ssh -x -a
-oClearAllForwardings=yes -oServerAliveInterval=300
-oIdentityFile=/home/name/.x2go/ssh/key.VE6405 -oUserKnownHostsFile= ...
Is there somebody who could help us getting back to working x2go-installation?
Best regards
Reinhold
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
-
K. Reinhold Trier -
Mihai Moldovan