OpenVZ Forum


Home » General » Support » Running NX Nomachine (almost there)
Running NX Nomachine (almost there) [message #35132] Wed, 04 March 2009 15:38
neondiet is currently offline  neondiet
Messages: 1
Registered: March 2009
Location: England, UK
Junior Member
Hi,

I've installed OpenVZ and have a couple of VPS's running now, installed using the basic centos-5-x86 template. I want to run GNOME in one (possibly more) so I set about installing GNOME and NX Nomachine. It almost works. I can connect using the nxclient from another system and it logs in and authenticates, gives me a session display and even displays the panel with the menu bar at the top. However I get lots of error dialog boxes related to applets which I have to dismiss. Each one contains one of the following messages:

OAFIID:GNOME_SystemTrayApplet
OAFIID:GNOME_ClockApplet
OAFIID:GNOME_MixerApplet
OAFIID:GNOME_WorkspaceSwitcherApplet
OAFIID:GNOME_TrashApplet
OAFIID:GNOME_WindowListApplet
OAFIID:GNOME_ShowDesktopApplet

When starting apps from the menu I get error dialogue boxes with lots of the following errors in the details section:

Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0

And often the app just dies. I've tried removing /tmp/orbit-<user> and rebooting as suggested elsewhere on Google, but it makes no difference.


Here's what I did to set up the environment so far. I'm sure I must be missing something:

[root@sdltrng01 ~]# vzctl set 101 --diskspace 6000000:6100000 --save
Saved parameters for CT 101
[root@sdltrng01 ~]# vzctl set 101 --diskinodes 360000:370000 --save
Saved parameters for CT 101


[root@openvz1 ~]# yum install gnome-speech gnome-menus gnome-utils gnome-games \
gnome-python2 gnome-volume-manager gnome-python2-extras gnome-mime-data \
gnome-user-share gnome-desktop gnome-pilot gnome-python2-desktop gnome-python2-gconf \
gnome-python2-gnomevfs gnome-backgrounds gnome-doc-utils gnome-mount \
gnome-netstatus gnome-media gnome-python2-gnomeprint gnome-session \
gnome-python2-bonobo gnome-keyring gnome-icon-theme gnome-system-monitor \
gnome-python2-applet gnome-python2-libegg gnome-vfs2-smb gnome-power-manager \
gnome-python2-canvas gnome-applets gnome-themes gnome-mag gnome-user-docs gnome-vfs2 \
gnome-panel gnome-spell gnome-screensaver gnome-python2-gtksourceview gdm gnome-terminal \
nfs-utils glibc.i386 cups-libs.i386 fontconfig.i386 freetype.i386 libgcc.i386 \
libstdc++.i386 libX11.i386 libXext.i386 libXft.i386 libXrender.i386 audiofile.i386


Make sure I'm up to date with everything:

[root@openvz1 ~]# yum update


Next I install the NX rpms:

nxclient-3.3.0-6.i386.rpm
nxnode-3.3.0-12.i386.rpm
nxserver-3.3.0-15.i386.rpm

[root@openvz1 ~]# rpm -ivh nx*rpm


And then start some missing services and reboot for a clean start. Without these gconfd bitches about file locks in messages:

[root@openvz1 ~]# chkconfig --levels 345 messagebus on
[root@openvz1 ~]# chkconfig --levels 345 portmap on
[root@openvz1 ~]# chkconfig --levels 345 nfslock on
[root@openvz1 ~]# reboot

After rebooting, create a clean new user account, give it a password and then login to that account using nxclient.

It's pretty quick to set up really, and I think this is worth pursuing as I'm sure lots of people would find it useful. Can anyone spot something I've missed?

--nd

[Updated on: Thu, 05 March 2009 09:23]

Report message to a moderator

Previous Topic: ***SOLVED*** Kernel with ICH9 and cpulimit support
Next Topic: risks of granting net_admin?
Goto Forum:
  


Current Time: Mon Aug 19 23:25:46 GMT 2024

Total time taken to generate the page: 0.03280 seconds