[FreeNX-kNX] server not starting

Tue May 13 11:45:35 UTC 2014

Hi Chris,

Thanks for the reply…..

I’d completely forgotten that NX is just a bunch of scripts that are called when you knock on the door, so
there aren’t any daemons running in the background listening for connections from NX……

So I have made a bit of progress with this one, but am still falling at the last hurdle….. I had some problems
with the ssh keys that we are using for authentication, and once this was fixed I was able to initiate a connection
from my Mac. I then specify a new graphical session (we’re using lubuntu as it’s fairly light-weight) and that’s
where I'm stuck.

If I save the error logs from the client I see this:
(connection)
> Warning: untrusted X11 forwarding setup failed: xauth key data not generated
> Warning: No xauth data; using fake authentication data for X11 forwarding.
> HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 105 hello NXCLIENT - Version 3.2.0
> NX> 134 Accepted protocol: 3.2.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: XXXXX
> NX> 102 Password: 
> NX> 103 Welcome to: acamar user: XXXXX
> NX> 105 listsession --status="suspended,running" --type="shadow"
> NX> 127 Sessions list of user ‘XXXXX' for reconnect:
> 
> Display Type             Session ID                       Options  Depth Screen         Status      Session Name
> ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
> 0       Local            1180F9EEEDDA8274947FF69EA3C7484E --------                      Running     X0 (Local)
> 0       Local            3E07A4581DCBE8C9568B035408845E5D --------                      Running     X0 (Local)
> 
> 
> NX> 148 Server capacity: not reached for user: XXXXX
> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --render="1" --session=“YYYYY" --type="unix-cde" --geometry="1422x770" --keyboard="pc105/gb" --client="macosx" --screeninfo="1422x770x24+render" 
> 
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 700 Session id: YYYYY-2000-5419F7EA366768C56F4F54B49215FAB9
> NX> 705 Session display: 2000
> NX> 703 Session type: unix-cde
> NX> 701 Proxy cookie: bfe307fd73f95a93508b8484151eeaa7
> NX> 702 Proxy IP: 137.222.202.133
> NX> 706 Agent cookie: bfe307fd73f95a93508b8484151eeaa7
> NX> 704 Session cache: unix-cde
> NX> 707 SSL tunneling: 1
> NX> 1009 Session status: starting
> NX> 710 Session status: running
> NX> 1002 Commit
> NX> 1006 Session status: running
> NX> 105 bye
> Bye
> NX> 999 Bye

Which is a bit confusing as there seem to be 2 local graphical sessions running, I would have guessed
only 1 (kdm).

On the machine running freenx-server if I look at the /var/tmp/nxserver.log I can see the session
starting and then ending immediately.

If I run ssh -Y XXXXX at YYYYYY (username at host)
I get in and then run
/var/lib/nxserver/nxnode —agent
I get the following:

> ./nxnode --agent
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 716 Starting NX Agent ...
> Error: Aborting session with 'Server is already active for display 0
> 	If this server is no longer running, remove /tmp/.X0-lock
> 	and start again'.
> Session: Aborting session at 'Tue May 13 12:24:28 2014'.
> Session: Session aborted at 'Tue May 13 12:24:28 2014'.
> NX> 716 NX Agent exited with status: 1
> NX> 1001 Bye. 

If I remove /tmp/.X0-lock and re-run I get the following:

> ./nxnode --agent
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
> NX> 716 Starting NX Agent ...
> _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
> _XSERVTransMakeAllCOTSServerListeners: server already running
> Error: Aborting session with 'Cannot establish any listening sockets - Make sure an X server isn't already running'.
> Session: Aborting session at 'Tue May 13 12:33:28 2014'.
> Session: Session aborted at 'Tue May 13 12:33:28 2014'.
> NX> 716 NX Agent exited with status: 1
> NX> 1001 Bye.

For the life of me I can’t work out what I did to get it to run on the other Ubuntu machine…..
where the user can login and create sessions:
If I look in /tmp on the good machine after the user has logged in there are:

> -rw-------  1 nx        nx           0 May 13 12:35 .nX1000-lock
> -r--r--r--  1 jonnytest jonnytest   11 May 13 12:35 .X1000-lock

None of these files are ever created for the normal user (not jonnytest) on the other (duff)
machine. I’m beginning to suspect that it is something account specific, but I haven’t
got a clue as to what that could be……

Any ideas?

Cheers, Jon

--
Jonathan Brooks (PhD) - Senior Research Fellow
CRiCBristol, University of Bristol, St Michael's Hill, Bristol, UK
T: +44(0)117-342-1512 W: http://www.cricbristol.ac.uk