Forum / NoMachine Cloud Server Products / Evaluating 5.0.53 Cloud Server
Tagged: DE, Desktop environment, GNOME, virtual desktop
- This topic has 1 reply, 2 voices, and was last updated 7 years, 5 months ago by Britgirl.
December 9, 2015 at 13:11 #9274scondasParticipant
I am attempting to evaluate NoMachine Cloud Server evaluation_5.0.53_2_x86_64.rpm on an AWS EC2 RHEL 7.2 VM for a virtual desktop environment. I started with the AWS supplied AMI, installed ‘nomachine-cloud-server-evaluation_5.0.53_2_x86_64.rpm’, tiger-vnc-server, and did ‘yum groupinstall gnome’. I then connect from my client and try to “Run the default X client script on the server”. I get the following error on the client: “Cannot run ‘/etc/X11/Xsession default’. Please, ensure that the requested application is in the system PATH and that you have the appropriate credentials to execute it.”.
I see the following errors on the server:
“Dec 7 16:51:19 ip-10-0-0-16 dbus: [system] Failed to activate service ‘org.bluez’: timed out
Dec 7 16:51:19 ip-10-0-0-16 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 7 16:51:19 ip-10-0-0-16 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Activation of org.bluez timed out
My client is nomachine-5.0.53-1 on RHEL 5.
Do you have a more explicit installation guide for the server side cloud configuration using RHEL?
Thanks!December 11, 2015 at 15:08 #9321BritgirlParticipant
That happens because NoMachine should be installed after installing Gnome (or any other desktop). NoMachine, at installation time, tries to detect what your DE is and set up the system to start it, without any need for the system administrator to intervene in the basic setup. This can only work if the DE is already installed and configured as the default at installation time. You can change the DE that is started by default at any time, and obviously add a new DE that is installed later.
So if you installed GNOME when NoMachine had already been installed, you need to set some keys in /usr/NX/etc/node.cfg.
To run a custom session: please modify 2 keys, DefaultXSession and CommandStartGnome into:
DefaultXSession “/etc/gdm/Xsession gnome-session”
CommandStartGnome “/etc/gdm/Xsession gnome-session”
Please remember to remove “#” at the beginning of the line.
If you also wish to have access to a full virtual desktop via “Create a new virtual desktop” please also change the key DefaultDesktopCommand in the abovementioned file into:
DefaultDesktopCommand “/etc/gdm/Xsession gnome-session”.
You can also uninstall NoMachine and install it again, then all those keys will be set automatically.
This topic was marked as solved, you can't post.