[FreeNX-kNX] FreeNX trouble

[Paul van der Vlis]

Jan Luehr schreef:
> Hello,
> 
> sadly I've come again to the point where my FreeNX-Server ist completly 
> unuseable.
> If've run freeNX on Debian Etch for months. When Etch finally become stable 
> (or around that time), some dist-upgrade broke my installation.
> Broke means:
> - Users were unable to login
> - NXClient itself was able to establish a public key based ssh connection
> - NX logs authentication failures using ssh auth attempts,
> - sshd logging showed some connections but no authentication attempts.
> 
> However, at first I suspected zum libraries got incomptible with some new etch 
> ones wants and rebuilt the nomachine sources.
> I also upgraded freeNX to 0.6. But that didn't change anything.
> I began playing around with the installation - scripts, but did'nt solve the 
> problem.
> However, after a some try-outs I broke NX completely
> - NX doesn't log

Did you turn loging on in /etc/nxserver/node.conf ?

> - NXClients timeout:
> NX> 203 NXSSH running with pid: 23412
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: 192.168.1.205 on port: 20290
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> NX> 280 Ignoring EOF on the monitored channel
> NX> 280 Ignoring CLOSE on the monitored channel
> Killed by signal 15.
> 
> and ssh logs successful connections
> May 21 22:43:36 alpha sshd[12996]: Accepted publickey for nx from 192.168.34.0 
> port 53791 ssh2
> May 21 22:44:38 alpha sshd[13016]: Accepted publickey for nx from 192.168.34.0 
> port 54625 ssh2
> May 21 22:45:49 alpha sshd[13037]: Accepted publickey for nx from 192.168.34.0 
> port 54626 ssh2
> May 21 22:47:45 alpha sshd[13072]: Accepted publickey for nx from 192.168.34.0 
> port 40863 ssh2
> May 21 22:48:17 alpha sshd[13080]: Accepted publickey for nx from 192.168.34.0 
> port 34256 ssh2
> 
> In an act of despair I renamd all my NX-libs, bins and dirs, killed the NX 
> users and installed freenx from 
> http://kern.nl/freenx/ ./
> 
> But that haven't changed anything at all.
> Do you have any ideas how to repair my installation?

Maybe remove everything again, and check by hand of all directories are 
removed. Remove if they still exicts:
/usr/bin/nxserver
/usr/lib/nx
/var/lib/nxserver
/etc/nxserver

Check /etc/passwd for a user called "nx", and remove it.

Install everything new from kern.nl. Use the defaults of the FreeNX 
installation. You don't have to do anything special.

I have seen on some machines problems with fetching the packages from 
kern.nl. There I had to download them manually with wget, and install 
them with dpkg.

I have installed FreeNX 6.0 on 4 Etch servers now, and all work fine. 3 
of them are coming from Sarge, One of them has already longer Etch, and 
had the older FreeNX before, and I have seen the problems what you describe.

If it still does not work, I would look at the authentication. Can you 
login with ssh to localhost, with the user you are using?  Try something 
like:  "ssh jan at localhost".

What does "nxserver --status" say?

server:~/freenx# nxserver --status
NX> 100 NXSERVER - Version 1.5.0-60 OS (GPL)
NX> 110 NX Server is running
NX> 999 Bye


With regards,
Paul van der Vlis.





-- 
http://www.vandervlis.nl/