The first thing I'd do is ssh to the box as $USER and delete .Xauthority and/ 
or .xhost from the home for, then rm -r the .x2go user session folder. Then try 
again.

If that doesn't fix it, can you ssh -X user@host from a client that is X11 
capable (Ubuntu client?) and run a simple xterm ?

Matt


> On Jun 7, 2016, at 2:13 PM, M.Rule <[email protected]> wrote:
> 
> We recently moved a server to a new network and x2go is not longer working. 
> The x2go client crashes too quickly to view or copy the error messages that 
> occur before it fails.
> 
> On the server side, I can see these messages in this in auth.log. I've 
> replaced all possible identifying information (hopefully) with bash-style 
> variable substituions (e.g. $USER). I apologize as this reduces clarity, but 
> I don't want any identifiable details on record.
> 
> $DATE $TIME $HOSTNAME sshd[14538]: reverse mapping checking getaddrinfo for 
> $INTERNET_PROVIDER [$INTERNET_PROVIDER_IP] failed - POSSIBLE BREAK-IN ATTEMPT!
> $DATE $TIME $HOSTNAME sshd[14538]: Accepted publickey for $USER from 
> $INTERNET_PROVIDER_IP port 49488 ssh2: RSA $A_RSA_KEY
> $DATE $TIME $HOSTNAME sshd[14538]: pam_unix(sshd:session): session opened for 
> user $USER by (uid=0)
> $DATE $TIME $HOSTNAME systemd-logind[1544]: New session 10 of user $USER.
> $DATE $TIME $HOSTNAME su[15451]: Successful su for $USER by root
> $DATE $TIME $HOSTNAME su[15451]: + ??? root:$USER
> $DATE $TIME $HOSTNAME su[15451]: pam_unix(su:session): session opened for 
> user $USER by (uid=0)
> $DATE $TIME $HOSTNAME systemd-logind[1544]: New session c20 of user $USER.
> $DATE $TIME $HOSTNAME su[15451]: pam_unix(su:session): session closed for 
> user $USER
> $DATE $TIME $HOSTNAME su[15468]: Successful su for $USER by root
> $DATE $TIME $HOSTNAME su[15468]: + ??? root:$USER
> $DATE $TIME $HOSTNAME su[15468]: pam_unix(su:session): session opened for 
> user $USER by (uid=0)
> $DATE $TIME $HOSTNAME systemd-logind[1544]: Removed session c20.
> $DATE $TIME $HOSTNAME systemd-logind[1544]: New session c21 of user $USER.
> $DATE $TIME $HOSTNAME sshd[14538]: pam_unix(sshd:session): session closed for 
> user $USER
> $DATE $TIME $HOSTNAME su[15468]: pam_unix(su:session): session closed for 
> user $USER
> $DATE 17:04:56 $HOSTNAME systemd-logind[1544]: Removed session c21.
> $DATE 17:05:01 $HOSTNAME systemd-logind[1544]: Removed session 10.
> 
> I'm not really familiar with things like this, but it looks like it is 
> repeatedly creating new sessions, and then these sessions are closed (for 
> some reason). I don't understand form these messages.
> 
> On the client side, this is as much of the log as I can get before the 
> program crashes. I haven't been able to locate the x2go client logfiles .
> 
> NXPROXY - Version 3.5.0
> 
> Copyright (C) 2001, 2010 NoMachine.
> See http://www.nomachine.com/ for more information.
> 
> Info: Proxy running in client mode with pid '534'.
> Session: Starting session at 'Tue $DATE 21:55:25 2016'.
> Info: Connecting to remote host 'localhost:31001'.
> Info: Connection to remote proxy 'localhost:31001' established.
> Info: Connection with remote proxy completed.
> Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent 
> session.
> Warning: Failed to read data from the X auth command.
> Warning: Generated a fake cookie for X authentication.
> Info: Using MODEM link parameters 256/24/1/0.
> Info: Using cache parameters 4/4096KB/8192KB/8192KB.
> Info: Using pack method '4k-png-3' with session 'unix-kde-depth_32'.
> InfoInfo: Established X server connection.
> Info: Using shared memory parameters 0/0K.
> 
> Can anyone help me debug this? I need more detailed errors if I'm going to 
> solve this on my own -- I can't really access all the error messages, nor 
> interpret the errors available, at the moment. 
> 
> Thanks in advance if you're able to help.
> Best,
> M. Rule. 
> _______________________________________________
> x2go-user mailing list
> [email protected]
> http://lists.x2go.org/listinfo/x2go-user
_______________________________________________
x2go-user mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-user

Reply via email to