FreeNX help for people upgrading to 11.3

hulleyrob · July 18, 2010, 12:10pm

Just incase anyone is suffering from the same problem as I was after upgrading to 11.3 that there was no such file or directory in /var/lib/nxserver/db/running/sessionID…

I found the answer in another forum and thought i would post it here.

Basically there is a change in the openssl library used to calculate the md5sum used by nx which stopped it from connecting.

Putting
COMMAND_MD5SUM=“md5sum”
at the end of /etc/nxserver/node.conf fixes the problem.

Regards

Rob

sles1983 · July 23, 2010, 10:28am

$ nxsetup --install --setup-nomachine-key --clean
Removing special user “nx” …no crontab for nx
done
Removing session database …done
Removing logfile …done
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Setting up /etc/nxserver …done
Setting up /var/lib/nxserver/db …done
Setting up /var/log/nxserver.log …done
Setting up special user “nx” …sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
done
Adding user “nx” to group “utmp” …done
Setting up known_hosts and authorized_keys2 …done
Setting up permissions …done
Setting up cups nxipp backend …cp: cannot stat `/usr/lib64/cups/backend/ipp’: No such file or directory

Solution: $ mkdir /usr/lib64/cups/backend/ipp

Enable log:
$ vi /etc/nxserver/node.conf

NX_LOG_LEVEL=5

By setting this to 0 the nxserver might be a bit faster, but passwords can be found in the log files.

NX_LOG_SECURE=1

Before turning logging on, please make sure that NX_LOGFILE is

writeable for the “nx” user

NX_LOGFILE=/var/log/nxserver.log

Fix for nxclient login error:

$ vi /etc/nxserver/node.conf

The tool to generate md5sums with

#COMMAND_MD5SUM=“openssl md5”
COMMAND_MD5SUM=“md5sum”

1). Setup again
$ nxsetup --install --setup-nomachine-key --clean

2). Add new account to system (use yast)

Test login from nxclient

It worked.

Reference - FreeNX - Fix bug on openSUSE 11.3 ( Use COMMAND_MD5SUM=“md5sum”)

super-hornet · July 23, 2010, 10:47am

Thanks! It work on my side as well.
If your were to use 64bit version, you might want to fix the cups’s ipp file also.

SH

queequeg · October 4, 2010, 9:55pm

Greetings. I stopped being able to make an NX connection after upgrading to 11.3. I followed the directions above, but am still unable to connect, and am getting a slightly different error in the setup after creating the /usr/lib64/cups/backend/ipp directory as follows:

# nxsetup --install --setup-nomachine-key --clean
Removing special user "nx" ...no crontab for nx
done
Removing session database ...done
Removing logfile ...done
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Setting up /etc/nxserver ...done
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nxserver.log ...done
Setting up special user "nx" ...sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
done
Adding user "nx" to group "utmp" ...done
Setting up known_hosts and authorized_keys2 ...done
Setting up permissions ...done
Setting up cups nxipp backend ...cp: cannot overwrite non-directory `/usr/lib64/cups/backend/nxipp' with directory `/usr/lib64/cups/backend/ipp'

The only step I can think of that I may have gotten wrong in your instructions above is

2). Add new account to system (use yast)

Can you please explain what this means? What account am I adding to the system Any other advice or suggestions you can think of would be greatly appreciated. The NX client gets this error on the remote machine:

NX> The NX service is not available or NX access was disabled on host XXX.XXX.XXX.XXX.

I can ssh into the machine just fine.

Thank you.

queequeg · October 4, 2010, 11:25pm

Update:

Never mind, it’s fixed. Apparently the old sshd_config and NX node.conf files I carried over from 11.2 didn’t jive with 11.3. I erased them both and went back to defaults, and now the above error went away and everything seems to be working perfectly.