I am using OpenSuse 12.2 with XFCE desktop environment.
I have installed the freenx from repositories and tried to start the nxserver with the command nxserver --start.After executing the command it says it has started but immediately when I check with --status command it shows nxserver is stopped.
Can anyone give me the link or post the procedure on HOW TO INSTALL AND CONFIGURE NXSERVER.
I have followed numerous but none of them are working to me.
On 01/12/2013 05:26 PM, nishanth9042 wrote:
>
> Hi guys,
>
> I am using OpenSuse 12.2 with XFCE desktop environment.
>
> I have installed the freenx from repositories and tried to start the
> nxserver with the command nxserver --start.After executing the command
> it says it has started but immediately when I check with --status
> command it shows nxserver is stopped.
>
> Can anyone give me the link or post the procedure on HOW TO INSTALL AND
> CONFIGURE NXSERVER.
>
> I have followed numerous but none of them are working to me.
>
> Thanks in advance.
>
>
To my knowledge there is no working freenx server for 12.2… not yet anyhow.
My solution was to go back to 12.1.
I remember that Gnome and probably XFCE didn’t work until I added -norender to the AGENT_EXTRA_OPTIONS_X. It indeed affected 12.2 and not 12.1 and Gnome or Xfce but not KDE. But the bug has been fixed in the latest NX agent, which is available in my repo
# zypper info NX
Information for package NX:
Repository: PTA
Name: NX
**Version: 3.5.0-121.1**
Arch: x86_64
Vendor: obs://build.opensuse.org/home:please_try_again
Installed: Yes
Status: up-to-date
Installed Size: 9.0 MiB
Summary: Proxy System for X11
Description:
NX provides a proxy system for the X Window System.
You need this version of the NX agent. Then it works with or without -norender, in Gnome and Xfce sessions.
Notice that if you install FreeNX from my repo with freenx-setup, you should be able to open a XFCE session directly by choosing “CDE” as desktop in NoMachine client, thanks to this change in /usr/bin/nxloadconfig
If you search the forum, you will also find threads where this issue has been discussed. I also thought it was broken until somebody gave me the solution. Later, I received a bug report mentionning that the bug had been fixed in the latest NX agent released by NoMachine. Thus I updated the package and it solved the problem (at least that particular one).
**# /usr/bin/nxsetup --test**
----> Testing your nxserver configuration ...
Warning: Invalid value "NX_LOGFILE=/var/log/nxserver.log"
No logfile will be kept.
Warnings occured during config check.
To enable these features please correct the configuration file.
<---- done
----> Testing your nxserver connection ...
**HELLO NXSERVER **- Version 3.2.0-73 OS (GPL, using backend: 3.5.0)
<--- done
----> Testing your nxserver configuration …
Error: Invalid value “NX_HOME_DIR=/var/lib/nxserver/home”
Warning: “/usr/lib/cups/backend/nxipp” is not executable.
Users will not be able to enable printing.
Warning: “/usr/lib/cups/backend/smb” is not executable.
Users will not be able to enable printing.
Warning: Invalid value “COMMAND_START_KDE=startkde”
Users will not be able to request a KDE session.
Warning: Invalid value “COMMAND_START_GNOME=gnome-session”
Users will not be able to request a Gnome session.
Warning: Invalid value “COMMAND_SMBMOUNT=/sbin/mount.cifs”. You’ll not be able to use SAMBA.
Errors occured during config check.
Please correct the configuration file.
Only the error is relevant. And that you don’t have a warning about invalid COMMAND_START_CDE shows me that you used freenx-setup indeed.
I’m not sure why you don’h have /var/lib/nxserver/home, since it is nx user’s home directory. This user should have been created as well as his home directory.
If you don’t have an nx user or his home directory is invalid, the nx server is not going to work for sure.
I don’t know what you have done before. Did you try to install another port of FreeNX or NoMachine NX (which ‘nx’ user has another home directory) ? Or didn’t you execute freenx-setup as root?
First thing to do is to check if you have an nx user already. If so, I would delete this user and run freenx-setup again. Try this first and see if you got the nx user created!
If it doesn’t help, I would uninstall FreeNX (you don’t need to uninstall the NX agent) and clear the directory /etc/nxserver (as well as /var/lib/nxserver if it exists), then install FreeNX again using YaST or zypper (but from my repo) and run freenx-setup again.
yeah I have deleted and then re installed freenx but didn’t work.
OUTPUT of freenx-setup is
allowing AuthorizeKeysFile2 back
Setting up /etc/nxserver …done
Generating public/private dsa key pair.
Your identification has been saved in /etc/nxserver/users.id_dsa.
Your public key has been saved in /etc/nxserver/users.id_dsa.pub.
The key fingerprint is:
31:e1:6e:fe:57:f9:99:04:a6:3e:9c:b8:43:33:f5:7e root@linux.site
The key’s randomart image is:
±- DSA 1024]----+
| . |
| . . |
| + |
| . o . o |
| S . + … |
| o + . .o. |
| o * o…o|
| + =… E.|
| .+… . |
±----------------+
Setting up /var/lib/nxserver/db …done
Setting up /var/log/nxserver.log …done
Setting up special user “nx” …
----> Testing your nxserver configuration …
Error: Invalid value “NX_HOME_DIR=/var/lib/nxserver/home”
Warning: “/usr/lib/cups/backend/nxipp” is not executable.
Users will not be able to enable printing.
Warning: “/usr/lib/cups/backend/smb” is not executable.
Users will not be able to enable printing.
Warning: Invalid value “COMMAND_START_KDE=startkde”
Users will not be able to request a KDE session.
Warning: Invalid value “COMMAND_START_GNOME=gnome-session”
Users will not be able to request a Gnome session.
Warning: Invalid value “COMMAND_START_CDE=startlxde”
Users will not be able to request a CDE session.
Warning: Invalid value “COMMAND_SMBMOUNT=/sbin/mount.cifs”. You’ll not be able to use SAMBA.
/usr/bin/nxloadconfig: line 595: strings: command not found
Warning: Invalid cupsd version of “/usr/sbin/cupsd”. Need version 1.[2345].
Users will not be able to enable printing.
/usr/bin/nxloadconfig: line 624: strings: command not found
Error: Could not find 1.5.0 or 2.[01].0 or 3.[012345].0 version string in nxagent. NX 1.5.0 or 2.[01].0 or 3.[012345].0 backend is needed for this version of FreeNX.
Errors occured during config check.
Please correct the configuration file.
The explanation is obvious now. You have an nx user, but his home directory has not been created.
The reason is that this nx user has not been deleted but his home directory was by the function createnxuser (which actually does not create the nx user but deletes his home directory). I agree that it sounds weird, but see the comment in the script:
function createnxuser {
# Running nxsetup with existing nx user doesn't work on openSUSE
# Thus we only use this function to delete the nx user yet.
#if (! $GROUPMOD nx 2>/dev/null) ; then
# echo "- creating nx group"
# setnxgid $NXGID ; groupadd -g $NXGID nx
#fi
#setnxuid $NXUID
#echo "- creating nx user"
rm -f $nxetc/{users,passwords}* /var/log/nxserver.log
rm -fr $nxhome $nxsess
# useradd -r -c "$nxfing" -d $nxhome -s $nxssh -u $NXUID -g $NXGID nx
# mkdir -m 755 $nxsess
# mkdir -m 700 -p $nxssh $nxsess/{closed,failed,running}
# chown -R nx $nxhome $nxsess
}
Before running freenx-setup again, you have to delete the nx user manually with:
# userdel nx
When it doesn’t work the first time, it’s kind of tricky.
Also I assume that you ran freenx-setup as root? Did you? You have to run everything as root as this point.
Then nxsetup is not able to write to /var/lib and create the nx user home directory on your system. I don’t know why.
At the end, freenx-setup (my script) just executes nxsetup (included in FreeNX package) by running this:
if "$NXSETUP" ] ; then
case $os in
ubuntu|linuxmint) "$sshkeys" ] || $nxkeygen ;;
archlinux|mandrivalinux) "$sshkeys" ] && nxsetup --install $sshkeys ;;
*)
id nx &>/dev/null && createnxuser
**nxsetup --install $sshkeys**
;;
esac
printf "
"
"$CUSTOMNODE" ] && patchnode || extraopts
-f /usr/lib/cups/backend/ipp ] && chmod 755 /usr/lib/cups/backend/ipp
-f $skey ] && createNXsession
fi
This command (in red) should create the nx user and its home directory /var/lib/nxserver.
I don’t know why it failed to create this directory. But this is the reason why the nx server doesn’t work for you.
:\
You could add a line (in blue) in the script to echo the command. It will tell us at least if this command is going to be executed.
if "$NXSETUP" ] ; then
case $os in
ubuntu|linuxmint) "$sshkeys" ] || $nxkeygen ;;
archlinux|mandrivalinux) "$sshkeys" ] && nxsetup --install $sshkeys ;;
*)
id nx &>/dev/null && createnxuser
**echo nxsetup --install $sshkeys**
**nxsetup --install $sshkeys**
;;
esac
printf "
"
"$CUSTOMNODE" ] && patchnode || extraopts
-f /usr/lib/cups/backend/ipp ] && chmod 755 /usr/lib/cups/backend/ipp
-f $skey ] && createNXsession
fi
Either something is missing earlier and this command doesn’t get executed, or it is executed but nxsetup doesn’t create /var/lib/nxserver.
But if I didn’t introduce a new bug in the script last time I updated it (which is of course always a possibility), something may be different on your system. I don’t get it yet.