When I emerged nxserver-personal I noticed error at the end of emerge -> * Adding user 'nx' for the NX server -> /usr/sbin/ebuild.sh: line 106: enewuser: command not found Which then lead to a number of errors because NX user was not created: * Setting home directory of user 'nx' to /usr/NX/home/nx usermod: user nx does not exist * Changing permissions for files under /usr/NX chown: `nx:root': invalid user chown: `nx:root': invalid user chown: `nx:root': invalid user * Generating SSH keys for the 'nx' user chown: `nx:root': invalid user * Creating NX user registration database chown: `nx:root': invalid user I manually created NX user and unmerged and emerged all packages again with no error reported. Also unable to connect to the NX server either locally (localhost) or via LAN. Not sure, at this point, if related to failure to create NX user initially. Reproducible: Always Steps to Reproduce: 1. Make sure no NX user defined on system 2. Install nxserver-personal 3.
I've updated the nxserver ebuilds so that this error doesn't happen. It'll take about an hour for the changes to reach your local rsync mirror. Best regards, Stu
Still has the same problem creating the user in nxserver-personal-1.3.2-r1
Problem still exists in current nxserver-business / personal: >>> original instance of package unmerged safely. * Adding user 'nx' for the NX server /usr/sbin/ebuild.sh: line 106: enewuser: command not found * Changing permissions for files under /usr/NX chown: `nx:root': invalid user chown: `nx:root': invalid user chown: `nx:root': invalid user * Generating SSH keys for the 'nx' user chown: `nx:root': invalid user cp: cannot stat `/usr/NX/home/.ssh/server.id_dsa.pub.key': No such file or directory * * To complete the installation, you must create a file called * '/usr/NX/etc/node.conf'. An example configuration file can * be found in /usr/NX/etc * * Caching service dependencies... >>> net-misc/nxserver-business-1.3.2-r1 merged. As per: http://forums.gentoo.org/viewtopic.php?t=200909&highlight=nxserver " the nxserver-business ebuild is forgetting to inherit an eclass for some reason - probably an ebuild bug. Perhaps "inherit eutils nxserver" instead of "inherit nxserver" would do the trick."
Patrick, please reopen this.. this isnt fixed and Ive synced 3 machines in the past 2 days, one just now.
Both cbradney@zip.com.au and I have found that this is not fixed as yet. I have re-emerged a number of times, still same problem reported about NX user not being created. Also even if I manually create the user I am still having problems getting NX server to work. The problems I have reported off list - various libraries not being found etc. do you want me to detail them here or what is best way to communicate the problems found?
Thanks for reopening. The other issue as per the info below I see is: cp: cannot stat `/usr/NX/home/.ssh/server.id_dsa.pub.key': No such file or directory It would seem the home dir changes over time confuse the install. Having put in the inherits eutils the user can be created automatically I found, but theres still connection problems. And.. once it does get installed? How are we supposed to start it? Can we rc-update add nxserver default in some way?
ping!
I've just committed a couple of changes to the eclass which should help. They should appear on your local rsync mirror in about an hour. Please emerge sync, and then re-install nxserver-personal. Best regards, Stu
Ok, sync'd: --- /etc/ --- /etc/env.d/ >>> /etc/env.d/50nxserver * Adding user 'nx' for the NX server * Adding user 'nx' to your system ... * - Userid: 101 * - Shell: /usr/NX/bin/nxserver * - Home: /usr/NX/home/nx * - Groups: (none) * Setting home directory of user 'nx' to /usr/NX/home/nx * Changing permissions for files under /usr/NX * Generating SSH keys for the 'nx' user * * You need to place your NX key.txt file into /usr/NX/etc/ * If you don't have one already, you can get an evaluation * key, or purchase a full license, from www.nomachine.com * * * To complete the installation, you must create a file called * '/usr/NX/etc/node.conf'. An example configuration file can * be found in /usr/NX/etc * ldconfig: Can't stat /opt/blackdown-jdk-1.4.1/jre/lib/i386/classic: No such file or directory ldconfig: Can't stat /usr/games/lib: No such file or directory ldconfig: Cannot stat /usr/lib/libGLcore.so: No such file or directory >>> Regenerating /etc/ld.so.cache... So, this kind of looks ok, apart from those ldconfig errrors(???), can nxserver-business be fixed now too please? Shall I submit a bug for nxserver-business? It still gets the same errors: --- /etc/ --- /etc/env.d/ * Adding user 'nx' for the NX server /usr/sbin/ebuild.sh: line 106: enewuser: command not found * Changing permissions for files under /usr/NX chown: `nx:root': invalid user chown: `nx:root': invalid user chown: `nx:root': invalid user * Generating SSH keys for the 'nx' user chown: `nx:root': invalid user cp: cannot stat `/usr/NX/home/.ssh/server.id_dsa.pub.key': No such file or directory * * You need to place your NX key.txt file into /usr/NX/etc/ * If you don't have one already, you can get an evaluation * key, or purchase a full license, from www.nomachine.com * * * To complete the installation, you must create a file called * '/usr/NX/etc/node.conf'. An example configuration file can * be found in /usr/NX/etc * >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... >>> net-misc/nxserver-business-1.3.2-r1 merged.
The nxserver- business ebuild was using the wrong eclass. I've fixed it; the updated version should appear on your local rsync mirror in about an hour. Best regards, Stu
Ok.. after screwing around a bit I got it working. thanks. It would seem a good idea to bump the ebuild versions on a few of the packages to get people to reemerge. I had to reemerge nxproxy, nxcomp and nxssh on the server to get them to work.
Policy is that we don't version bump ebuilds for fixes to the ebuild itself. Anyone who already has nxserver installed and working wouldn't gain anything by upgrading to a later revision. Best regards, Stu
Yes I realise that, but I was missing nxssh, and reemerging it put it in its place and made nxserver work. Anyway.. its working now. Thanks
Just in time for nxserver-1.4.0, which should appear in a fortnight or so :) Best regards, Stu
