[X2Go-User] x2goclient Mate 17.04 can't connect to CentOS 6.8

John Stoffel john at stoffel.org
Wed Apr 26 00:17:02 CEST 2017


Hi guys,
I'm running a CentOS 6.8 x86_64 system using the following versions of
x2go:

   > rpm -qa |grep x2go
   x2goclient-4.0.1.4-1.el6.x86_64
   x2goserver-4.0.1.20-1.el6.x86_64
   x2golxdebindings-debuginfo-1.0.2.4-1.1.x86_64
   x2goserver-xsession-4.0.1.20-1.el6.x86_64
   python-x2go-0.5.0.3-1.el6.noarch
   x2goagent-3.5.0.32-3.1.x86_64
   x2gognomebindings-2.0.2.1-2.1.x86_64

My home system is a Linux Mint Serena 18.1 MATE x86_64 system.  It's
having problems connecting to the CentOS system.

So I use this CentOS system as both the x2go server, and as the
client, so I can work from either home or work with the same session.
But now from my home system (Linux Mint Serena 18.1 x86_64), I can't
get a running session, it just hangs.  Running x2goclient --debug I
get the following:

    x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 3: "x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 wan 16m-jpeg-9 us auto 1 both"
    x2go-DEBUG-../src/sshprocess.cpp:204> this=SshProcess(0x264ec60)  Running masterCon->addChannelConnection(this, ' "47d7a6d9-893d-45ed-b62c-4fe558416916" ', ' "bash -l -c 'echo "X2GODATABEGIN:47d7a6d9-893d-45ed-b62c-4fe558416916"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 w" ');
    x2go-DEBUG-../src/sshmasterconnection.cpp:1325> Locking SSH channel connection MUTEX.
    x2go-DEBUG-../src/sshmasterconnection.cpp:1327> Passing new channel conenction object to channelConnections.
    x2go-DEBUG-../src/sshmasterconnection.cpp:1329> Unlocking SSH channel connection MUTEX.
    x2go-DEBUG-../src/sshmasterconnection.cpp:1517> Creating new channel.

    x2go-DEBUG-../src/sshmasterconnection.cpp:1521> New channel:0x7fc7f4012790

    x2go-DEBUG-../src/sshmasterconnection.cpp:1552> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:47d7a6d9-893d-45ed-b62c-4fe558416916"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 wan 16m-jpeg-9 us auto 1 both; echo "X2GODATAEND:47d7a6d9-893d-45ed-b62c-4fe558416916";'"

    x2go-DEBUG-../src/sshmasterconnection.cpp:1575> New exec channel created.


And it just seems to hang here.  On the server, I see the following in /var/log/messages:

    Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:22 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:27 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
    Apr 25 18:09:41 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully

And on the x2goserver system, in the session.log file I see:

    [root at sekrit C-stoffj-50-1490735175_stDGNOME_dp24]# tail session.log
    Session: Suspending session at 'Tue Apr 25 18:11:31 2017'.
    Session: Session suspended at 'Tue Apr 25 18:11:31 2017'.
    Session: Resuming session at 'Tue Apr 25 18:11:31 2017'.
    Warning: Option file doesn't contain a port specification.
    Info: Proxy running in server mode with pid '14478'.
    Info: Waiting for connection from any host on port '4050'.
    Info: Aborting the procedure due to signal '1'.
    Session: Display failure detected at 'Tue Apr 25 18:11:37 2017'.
    Session: Suspending session at 'Tue Apr 25 18:11:37 2017'.
    Session: Session suspended at 'Tue Apr 25 18:11:37 2017'.


so I'm wondering what has happened here?  I'm trying to update my CentOS system to the latest packages, but it's probably not going to help since I don't see any x2go packages in the update.

Is there anything else I can do to help debug this?

Thanks,
John


More information about the x2go-user mailing list