Hi Mike,

I now use 4.0.1.16 and the problem seems to remain, with different messages in the debug log.

On the client side I still get this message:

channel 1: open failed: connect failed: Connection refused

During an unsuccesful reconnect there is a message from x2gormforward on the server side that I haven't seen before, about terminating SSHD:

Sep 27 16:53:33 servername /usr/bin/x2golistsessions[3571]: x2golistsessions has been called with no option Sep 27 16:53:34 servername /usr/lib/x2go/x2gogetagent[3598]: db_getagent called, session ID: username-50-1411739336; return value: 21707 Sep 27 16:53:34 servername /usr/lib/x2go/x2gormforward[3609]: Terminating SSHD process: 0

A succesful reconnect a few seconds later:

Sep 27 16:53:39 servername /usr/bin/x2golistsessions[3663]: x2golistsessions has been called with no option Sep 27 16:53:40 servername /usr/lib/x2go/x2gogetagent[3697]: db_getagent called, session ID: username-50-1411739336; return value: 21707 Sep 27 16:53:40 servername /usr/bin/x2golistsessions[3716]: x2golistsessions has been called with no option Sep 27 16:53:40 servername /usr/bin/x2goresume-session: old ports: 30201, 30202, 30203 Sep 27 16:53:40 servername /usr/lib/x2go/x2gogetports[3751]: db_getports called, server: servername; return value: |30201| |30202| |30203| Sep 27 16:53:40 servername /usr/lib/x2go/x2goresume[3829]: db_resume called, session ID: username-50-1411739336, client: 192.168.100.121, gr_port: 30201, sound_port: 30202, fs_port: 30203

Version info from the server:

ii libnx-x11 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 nx-X11 ii libxcomp3 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 NX X compression library ii libxcompext3 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 NX X11 protocol compression extensions library ii libxcompshad3 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 NX shadowing library ii nxagent 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 NX agent ii nxproxy 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 amd64 NX proxy ii x2goagent 2:3.5.0.27-0x2go1+git20140701.511+jessie.main.1 all X2Go agent ii x2goclient 4.0.2.1-1 amd64 X2Go Client application (Qt4) ii x2goserver 4.0.1.16-0x2go1+git20140926.935+jessie.main.1 amd64 X2Go server daemon scripts ii x2goserver-extensions 4.0.1.16-0x2go1+git20140926.935+jessie.main.1 all X2Go server daemon scripts (extensions) ii x2goserver-xsession 4.0.1.16-0x2go1+git20140926.935+jessie.main.1 all X2Go server daemon scripts (Xsession runner)

Cheers, Daniel

2014-09-15 8:20 GMT+02:00 Daniel Lindgren <bd.dali@gmail.com>:

Hi Mike,

I'm using this version: 4.0.1.15-0x2go1+git20140615.847+jessie.main.1.

Cheers, Daniel

2014-09-14 21:38 GMT+02:00 Mike Gabriel <mike.gabriel@das-netzwerkteam.de> :

...

Hi Daniel,

On So 14 Sep 2014 16:37:29 CEST, Daniel Lindgren wrote:

Hi.

...

When I try to reconnect to a X2Go session it sometimes fails, if I use x2goclient-cli I can see this error message on the client side:

channel 1: open failed: connect failed: Connection refused

I've have experienced this problem for a long time (years), but haven't reported it because I haven't found a way to reliably reproduce it.

I did some troubleshooting yesterday and may have found a clue, this was logged in the X2Go debug log (server side) at the same time that the reconnection failed:

Sep 13 18:10:03 servername /usr/bin/x2golistsessions[7748]: x2golistsessions has been called with no option Sep 13 18:10:03 servername /usr/lib/x2go/x2gogetagent[7771]: db_getagent called, session ID: username-50-1410624337; return value: 4801 Sep 13 18:10:03 servername /usr/bin/x2golistsessions[7784]: x2golistsessions has been called with no option Sep 13 18:10:03 servername /usr/bin/x2goresume-session: old ports: 30201, 30202, 30203 Sep 13 18:10:03 servername /usr/lib/x2go/x2gogetports[7817]: db_getports called, server: servername; return value: |30201| |30202| |30203| Sep 13 18:10:04 servername /usr/sbin/x2gocleansessions[4044]: username-50-1410624337: unmounting all shares Sep 13 18:10:04 servername /usr/lib/x2go/x2goresume[7896]: db_resume called, session ID: username-50-1410624337, client: 192.168.100.121, gr_port: 30201, sound_port: 30202, fs_port: 30203 Sep 13 18:10:04 servername /usr/bin/x2goumount-session[7918]: db_getdisplay called, session ID: username-50-1410624337; return value: 50 Sep 13 18:10:04 servername /usr/bin/x2goumount-session[7918]: db_getmounts called, session ID: username-50-1410624337; return value: Sep 13 18:10:04 servername /usr/lib/x2go/x2gogetagent[7996]: db_getagent called, session ID: username-50-1410624337; return value: 4801 Sep 13 18:10:05 servername /usr/lib/x2go/x2gochangestatus[8126]: db_changestatus called, session ID: username-50-1410624337, new status: Sx2gocleansessions Sep 13 18:10:05 servername /usr/bin/x2goumount-session[8134]: db_getdisplay called, session ID: username-50-1410624337; return value: 50 Sep 13 18:10:05 servername /usr/bin/x2goumount-session[8134]: db_getmounts called, session ID: username-50-1410624337; return value: Sep 13 18:10:05 servername /usr/sbin/x2gocleansessions[4044]: username-50-1410624337 was found running and has now been suspended

It looks to me like it could be a conflict between x2goresume-session and x2gocleansessions? While the session is being resumed, it gets cleaned up and suspended?

Cheers, Daniel

What X2Go Server version are you using? This is a know issue in X2Go Server <= 4.0.1.15.

I am about to release 4.0.1.16 which should solve the issue.

Mike

--

DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das- netzwerkteam.de.xfb