nx client ubuntu server problems

[ashc]

hello, i am new to nxclient and I am trying to connect to my ubuntu server but I am having issues with FreeNX any help would be much apreciated...


Here is what the details say on NXClient

it sais authentication complete, then sais connection error?


NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
NX> 700 Session id: r16252.ovh.net-1000-54925100B44AAC086A5CE1859BE1BADA
NX> 705 Session display: 1000
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: bd322a48d61e520202a6cc8fb502b983
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: bd322a48d61e520202a6cc8fb502b983
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/admin/.nx/F-C-r16252.ovh.net-1000-54925100B44AAC086A5CE1859BE1BADA/session". You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. Session log follows:
/usr/bin/nxserver: line 1368: 23542 Terminated sleep $AGENT_STARTUP_TIMEOUT
Can't open /var/lib/nxserver/db/running/sessionId{54925100B44AAC086A5CE1859BE1BADA}: No such file or directory.
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{54925100B44AAC086A5CE1859BE1BADA}': No such file or directory
NX> 1006 Session status: closed
NX> 1009 Session status: starting
NX> 1009 Session status: starting
NX> 1001 Bye.
NX> 280 Exiting on signal: 15

any ideas, would be much apreciated

[Hibbelharry]

First Task when this happens:
Delete the cache of the nx client and just try again. There's a button for this in the preferences.

If this doesn't help set keeping the session logs enabled in node.conf like stated in the error message and check the content of the log for errors.

[ashc]

First Task when this happens:
Delete the cache of the nx client and just try again. There's a button for this in the preferences.

If this doesn't help set keeping the session logs enabled in node.conf like stated in the error message and check the content of the log for errors.

hello, thanks very much for your help, i am quite new to this program, i have cleared the cache and still no luck, but i am unsure of how to do the second thing you have suggested, if you could guide me in the right direction, it would be much apreciated,

again thanks for your help