Has anyone managed to get the x2go server working on CentOS 6.7?
I started testing x2go from EPEL under 6.6, and it worked well. Then I didn't use it in 6 months plus, eventually upgraded the machine to 6.7, and it's no longer working. Both Windows and Linux clients error out with "Connection failed. 0: Event not found."
A Linux client run with the debug option reports:
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:963> Password authentication
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:654> user auth OK
x2go-DEBUG-../x2goclient-4.0.3.2/onmainwindow.cpp:2797> SSH connection established. x2go-DEBUG-../x2goclient-4.0.3.2/onmainwindow.cpp:3060> Continue normal x2go session x2go-DEBUG-../x2goclient-4.0.3.2/sshprocess.cpp:189> executing remote command via SshProcess object (0): "export HOSTNAME && x2golistsessions"
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1434> creating new channel
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1438> new channel:0x7efd94013740
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1469> executing remote: "sh -c 'echo X2GODATABEGIN:a469c6c6-254d-431e-94ac-b30785359dbc; PATH=/usr/local/bin:/usr/bin:/bin export HOSTNAME && x2golistsessions; echo X2GODATAEND:a469c6c6-254d-431e-94ac-b30785359dbc;'"
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1492> new exec channel created
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1596> EOF ON CHANNEL 0x7efd94013740 (SshProcess: 0)
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1664> eof sent
x2go-DEBUG-../x2goclient-4.0.3.2/sshmasterconnection.cpp:1668> channel closed
x2go-DEBUG-../x2goclient-4.0.3.2/sshprocess.cpp:444> have only stderr, something must be wrong
x2go-DEBUG-../x2goclient-4.0.3.2/sshprocess.cpp:449> ssh finished: false - "0: Event not found. " (0).
x2go-DEBUG-../x2goclient-4.0.3.2/onmainwindow.cpp:3404> "0: Event not found. "
This is potentially similar to http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=800, which hasn't been updated since March.
On Thu, Sep 24, 2015 at 10:50:08AM +0100, isdtor wrote:
Has anyone managed to get the x2go server working on CentOS 6.7?
Worked out of the box for me. Actually, I probably had it on 6.6 and then upgraded, but no issues since then. I have a fairly simple setup.
http://srobb.net/nxreplace.html (I don't know if that will help at all though).
http://srobb.net/nxreplace.html (I don't know if that will help at all though).
No joy, unfortunately. Even reinstalling x2go from scratch doesn't help.
On Thu, Sep 24, 2015 at 8:31 AM, isdtor isdtor@gmail.com wrote:
http://srobb.net/nxreplace.html (I don't know if that will help at all though).
No joy, unfortunately. Even reinstalling x2go from scratch doesn't help.
It did work out of the box for me, too. If I remember correctly, I installed x2goserver on a CentOS 6.6 system and then updated it to 6.7.
The errors you posted were from the client. Assuming you can ssh into the remote machine without a problem, do you see error messages there on the server?
Akemi
The errors you posted were from the client. Assuming you can ssh into the remote machine without a problem, do you see error messages there on the server?
Thanks, Akemi, you have hit the nail on the head!
The spurious error message was caused by a statement in .cshrc that created output, a stray unescaped exclamation mark in an alias definition. And that with me preaching to my users for years about cleaning up their init files ...
I feel stupid now. But not contagious, thankfully.
On Thu, Sep 24, 2015 at 9:13 AM, isdtor isdtor@gmail.com wrote:
The errors you posted were from the client. Assuming you can ssh into the remote machine without a problem, do you see error messages there on the server?
Thanks, Akemi, you have hit the nail on the head!
The spurious error message was caused by a statement in .cshrc that created output, a stray unescaped exclamation mark in an alias definition. And that with me preaching to my users for years about cleaning up their init files ...
Glad to hear you've identified the cause. By the way I love that "stray unescaped exclamation mark in an alias definition" ;-)
Akemi
On 09/24/2015 11:13 AM, isdtor wrote:
The errors you posted were from the client. Assuming you can ssh into the remote machine without a problem, do you see error messages there on the server?
Thanks, Akemi, you have hit the nail on the head!
The spurious error message was caused by a statement in .cshrc that created output, a stray unescaped exclamation mark in an alias definition. And that with me preaching to my users for years about cleaning up their init files ...
I feel stupid now. But not contagious, thankfully.
Don't worry .. she does that to me all the time too :)
toracat is way too smart ..
-
Akemi Yagi -
isdtor -
Johnny Hughes -
Scott Robbins