Hello Ulrich

The directories in /tmp get created automatically every thime I attempt a session (and before you ask, they are owned by my user and group)

The links in my home are also fine:

lrwxrwxrwx.  1 danielk computer   59 Oct 16 17:39 C-danielk-50-1539704304_stRTERMINAL_dp24 -> /tmp/.x2go-danielk/C-danielk-50-1539704304_stRTERMINAL_dp24

ls -al /tmp/.x2go-danielk/C-danielk-50-1539703799_stRTERMINAL_dp24

total 24

drwx------.  2 danielk computer 4096 Oct 16 17:30 .

drwxr-xr-x. 11 danielk computer 4096 Oct 16 17:55 ..

-rw-r--r--.  1 danielk computer  516 Oct 16 17:30 options

-rw-------.  1 danielk computer  825 Oct 16 17:30 session.log

-rw-r--r--.  1 danielk computer   12 Oct 16 17:30 sshd.pid

-rw-r--r--.  1 danielk computer    8 Oct 16 17:30 state

That was my first thought, but alas.

On 10/16/2018 06:24 PM, Ulrich Sibiller wrote:

Have you tried creating /tmp/.x2go-danielk? Is there a dangling link in ~danielk/.x2go/? On Tue, Oct 16, 2018 at 6:11 PM Daniel Kollmer <danielk@nikhef.nl> wrote:

...

Hello

After some user's session got broken due to a client/server incompatibility, the user deleted all their session data and then told me they can not log in at all anymore. At first I could not see any problem (everything worked as expected for me), but when I deleted my own /tmp/.x2go-danielk directory, I started having the exact same problem.

The error I get is:

Agent output: "Failed to start X2Go Agent session with ID danielk-50-1539704304_stRTERMINAL_dp24. X2Go Agent terminated unexpectedly. Aborting session startup. The complete relevant last part of the debug log is pasted below.

The session.log for this session contains the error

Error: Aborting session with 'Unable to open display 'nx/nx,options=/tmp/.x2go-danielk/C-danielk-50-1539704304_stRTERMINAL_dp24/options:50''.

Do you have any idea how I can get this working again. It appears to me that something is not functioning accordingly with the session management, because the session state file remains in state STARTING and if I try logging in again then I get asked whether I want to terminate or suspend the running session (can't resume)

Thanks for any help.

Additional information about the system:

X2Go Client 4.1.1.1

x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-x2goagent: 3.5.99.16 x2goserver-xsession: 4.1.0.0

CentOS Linux release 7.5.1804

Home directories are mounted on NFS

The problem exists for different Windows and Linux clients tested (Windows 7, Windows 10, CentOS, Ubuntu)

The complete relevant last part of the debug log is:

x2go-DEBUG-../src/sshmasterconnection.cpp:1884> Unlocking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:2072> Creating new channel.

x2go-DEBUG-../src/sshmasterconnection.cpp:2089> New channel:0x7fee0c00c780

x2go-DEBUG-../src/sshmasterconnection.cpp:2174> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:d9eae36c-6aa2-4fd4-9dfc-e700aaaea1d0"; export PATH="/usr/local/bin:/usr/bin:/bin";export TERM="dumb"; x2golistsessions; echo "X2GODATAEND:d9eae36c-6aa2-4fd4-9dfc-e700aaaea1d0";'"

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

x2go-DEBUG-../src/sshmasterconnection.cpp:2301> EOF on channel 0x7fee0c00c780; SshProcess object: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:2369> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:2373> Channel closed. x2go-DEBUG-../src/sshprocess.cpp:526> SSH finished: raw output (stdout): "X2GODATABEGIN:d9eae36c-6aa2-4fd4-9dfc-e700aaaea1d0 X2GODATAEND:d9eae36c-6aa2-4fd4-9dfc-e700aaaea1d0 " x2go-DEBUG-../src/sshprocess.cpp:537> SSH finished: true - "" (0). x2go-DEBUG-../src/onmainwindow.cpp:3982> "" x2go-DEBUG-../src/onmainwindow.cpp:4556> Executing remote command: "X2GODPI=96 X2GO_XINERAMA=no x2gostartagent 800x600 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 R TERMINAL both" x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 1: "X2GODPI=96 X2GO_XINERAMA=no x2gostartagent 800x600 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 R TERMINAL both" x2go-DEBUG-../src/sshprocess.cpp:213> this=SshProcess(0x285a6d0) Running masterCon->addChannelConnection(this, ' "57b6188d-1487-4c88-9c6b-53043bddee5e" ', ' "bash -l -c 'echo "X2GODATABEGIN:57b6188d-1487-4c88-9c6b-53043bddee5e"; export PATH="/usr/local/bin:/usr/bin:/bin";export TERM="dumb"; X2GODPI=96 X2GO_XINERAMA=no x2gostartagent 800x600 adsl 16m-jpeg-9" '); x2go-DEBUG-../src/sshmasterconnection.cpp:1880> Locking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1882> Passing new channel connection object to channelConnections. x2go-DEBUG-../src/sshmasterconnection.cpp:1884> Unlocking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:2072> Creating new channel.

x2go-DEBUG-../src/sshmasterconnection.cpp:2089> New channel:0x7fee0c00c780

x2go-DEBUG-../src/sshmasterconnection.cpp:2174> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:57b6188d-1487-4c88-9c6b-53043bddee5e"; export PATH="/usr/local/bin:/usr/bin:/bin";export TERM="dumb"; X2GODPI=96 X2GO_XINERAMA=no x2gostartagent 800x600 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 R TERMINAL both; echo "X2GODATAEND:57b6188d-1487-4c88-9c6b-53043bddee5e";'"

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

x2go-DEBUG-../src/sshmasterconnection.cpp:2301> EOF on channel 0x7fee0c00c780; SshProcess object: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:2369> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:2373> Channel closed. x2go-DEBUG-../src/sshprocess.cpp:526> SSH finished: raw output (stdout): "X2GODATABEGIN:57b6188d-1487-4c88-9c6b-53043bddee5e X2GODATAEND:57b6188d-1487-4c88-9c6b-53043bddee5e " x2go-DEBUG-../src/sshprocess.cpp:532> Have stderr only, something must be wrong. x2go-DEBUG-../src/sshprocess.cpp:537> SSH finished: false - "Failed to start X2Go Agent session with ID danielk-50-1539704304_stRTERMINAL_dp24. X2Go Agent terminated unexpectedly. Aborting session startup. " (1). x2go-DEBUG-../src/onmainwindow.cpp:5390> Agent output: "Failed to start X2Go Agent session with ID danielk-50-1539704304_stRTERMINAL_dp24. X2Go Agent terminated unexpectedly. Aborting session startup.

-- Daniel Kollmer Computer Technology Group NIKHEF - Dutch National Institute for Sub-atomic Physics Science Park 105 1098 XG Amsterdam Phone: +31205922164

---

x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user

-- Daniel Kollmer Computer Technology Group NIKHEF - Dutch National Institute for Sub-atomic Physics Science Park 105 1098 XG Amsterdam Phone: +31205922164

I don't see any x2go processes running.

I have compared the debug log of this machine with one where things work, and it seems to me that this message is where things break:

x2go-DEBUG-../src/sshprocess.cpp:532> Have stderr only, something must be wrong

I don't see that on other machines where the client just breezes past this point. Not sure what I should make of it though.

Greetings Daniel

On 10/17/2018 10:51 AM, richard lucassen wrote:

On Tue, 16 Oct 2018 17:56:00 +0200 Daniel Kollmer <danielk@nikhef.nl> wrote:

...

Agent output: "Failed to start X2Go Agent session with ID danielk-50-1539704304_stRTERMINAL_dp24. X2Go Agent terminated unexpectedly. Aborting session startup. The complete relevant last part of the debug log is pasted below. Sometimes an x2goclient process running on 127.0.0.1 hangs for one or another reason. After running a "killall -9 x2goclient" I can start a new session or resume a suspended session.

I have no idea if that's your problem btw.

Just my 2 cts,

R.

-- Daniel Kollmer Computer Technology Group NIKHEF - Dutch National Institute for Sub-atomic Physics Science Park 105 1098 XG Amsterdam Phone: +31205922164

Hello Stefan

I did indeed try the things you suggested with the same results. After comparing releases on a machine where things work and this one I found that elsewhere x2go was installed from the x2go-release-epel repository while on the broken one it was the epel repository version:

x2goserver: 4.1.0.2 x2goserver-common: 4.1.0.2 x2goserver-extensions: 4.1.0.2 x2goserver-x2goagent: 3.5.99.16 x2goserver-xsession: 4.1.0.2

vs.

x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-x2goagent: 3.5.99.16 x2goserver-xsession: 4.1.0.0

I removed all packages and dependencies and installed the new version. This works. Apparently there is some sort of bug in the older version that prevents the initialization of new user sessions because diverse testusers which had never logged in and never used x2go ran into the same problem.

Interestingly enough, a user with a previously functioning session (which did not get removed) worked.

Greetings Daniel

On 10/17/2018 04:01 PM, Stefan Baur wrote:

Am 17.10.18 um 15:46 schrieb Daniel Kollmer:

...

I don't see any x2go processes running.

I have compared the debug log of this machine with one where things work, and it seems to me that this message is where things break:

x2go-DEBUG-../src/sshprocess.cpp:532> Have stderr only, something must be wrong

I don't see that on other machines where the client just breezes past this point. Not sure what I should make of it though. What happens when you create a test account on the same server, and try to log in to that? Same error, or working fine?

If it's only the single account that is affected, and not the entire server, my gut feeling would be that the user didn't just delete some session data, but messed with some configuration file, maybe .profile or .bash_rc. Look if any of those contains a redirect (>) instruction, maybe some ">/dev/null" somewhere that has become dangling.

Some more things to try:

Can the affected user log in via plain ssh? What about the test user?

Assuming logging in via plain ssh works, what happens when the affected user logs in via plain ssh and runs:

x2golistsessions

Also, the output of

dpkg -l | egrep 'nx|x2go'

might provide some clues.

Kind Regards, Stefan Baur

-- Daniel Kollmer Computer Technology Group NIKHEF - Dutch National Institute for Sub-atomic Physics Science Park 105 1098 XG Amsterdam Phone: +31205922164