Forum / NoMachine for Linux / NoMachine enterprise evaluation fails to install properly on RHEL 6.5
- This topic has 3 replies, 2 voices, and was last updated 11 years, 9 months ago by  Britgirl. Britgirl.
- 
		AuthorPosts
- 
		
			
				
January 30, 2014 at 10:17 #2004 peter.kovacParticipant peter.kovacParticipantI’m trying to evaluate some of the NoMachine Enterprise products on a RHEL6.5 server and none of the RPMs (or the tarball) appear to install and work properly. The init script expects a file that isn’t created (/etc/NX/nxserver). The nxserver binary (/usr/NX/bin/nxserver) fails because it needs nxd. The trial license bundled expired 1/11. Copy/paste of the session details below. Has anyone gotten this tool installed on RHEL6? From what I can tell, this is effectively a non-starter. [root@nxtesthost ~]# /etc/init.d/iptables status 
 iptables: Firewall is not running.
 [root@nxtesthost ~]# getenforce
 Permissive[root@nxtesthost ~]# rpm -Uvh nomachine-enterprise-desktop-evaluation_4.0.369_2_x86_64.rpm 
 Preparing… ########################################### [100%]
 1:nomachine ########################################### [100%]
 NX> 701 Starting update at: Wed Jan 29 13:10:21 2014.
 NX> 701 Updating: nxclient version: 4.0.369.
 NX> 701 Using installation profile: Red Hat.
 NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
 NX> 701 Updating: nxplayer version: 4.0.369.
 NX> 701 Using installation profile: Red Hat.
 NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
 NX> 701 Updating: nxnode version: 4.0.369.
 NX> 701 Using installation profile: Red Hat.
 NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
 NX> 701 ERROR: Cannot change context for: /etc/NX/nxnode to: shell_exec_t.
 NX> 701 Creating configuration in: /usr/NX/etc/node.cfg.
 NX> 701 Node update completed with warnings.
 NX> 701 Please review the update log for details.
 NX> 701 Updating: nxserver version: 4.0.369.
 NX> 701 Using installation profile: Red Hat.
 NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
 NX> 701 Saving configuration file to: /usr/NX/etc/server.cfg.backup.
 NX> 701 Creating configuration in: /usr/NX/etc/server.cfg.
 NX> 701 ERROR: Cannot start service: nxserver.
 NX> 701 Server update completed with warnings.
 NX> 701 Please review the update log for details.
 NX> 701 Update completed with errors at: Wed Jan 29 13:10:27 2014.
 NX> 701 NoMachine was configured to run the following service:
 NX> 701 NX service on port: 4000[root@nxtesthost ~]# cat /usr/NX/etc/server.lic —– Begin subscription data —– NX Subscription Certificate Copyright (c) 2001,2013 NoMachine, http://www.nomachine.com Date: Thu Dec 12 20:45:45 CET 2013 
 Product: NoMachine Enterprise Desktop Evaluation
 Customer: NoMachine
 E-mail: info[at]nomachine.com
 Product Id: LEDE
 Subscription Id: None
 Subscription Type: Evaluation
 Expiry: Sat Jan 11 20:45:45 CET 2014
 Platform: Linux
 Users: Unlimited
 Connections: Unlimited
 Virtual Desktops: None
 Processors: Unlimited
 Product Key: 338152313bf6c6675450c46807bc572c923bc271
 Subscription Key: e53908b00eacb1858d2b2d77a87cde65dbc29835—– End subscription data —– [root@nxtesthost ~]# /etc/init.d/nxserver start 
 ERROR: /etc/NX/nxserver doesn’t exist
 [root@nxtesthost ~]# /usr/NX/bin/nxserver –startup
 NX> 618 Your evaluation period has expired. Please visit
 NX> 618 the NoMachine Web site at http://www.nomachine.com/
 NX> 618 to acquire a valid subscription.
 NX> 999 Bye.[root@nxtesthost ~]# date -s “Thu Dec 12 20:45:45 CET 2013” 
 Thu Dec 12 14:45:45 EST 2013
 [root@nxtesthost ~]# /usr/NX/bin/nxserver –startup
 NX> 161 Enabled service: nxserver.
 NX> 500 ERROR: Cannot start service: nxd.[root@nxtesthost log]# cat /etc/redhat-release 
 Red Hat Enterprise Linux Server release 6.5 (Santiago)January 30, 2014 at 17:13 #2046 BritgirlKeymaster BritgirlKeymasterThis is a bug. Problems with update are not related to the expired evaluation license. You should simply get a warning message and the server will refuse to work once update completed. We have reproduced it and there is a workaround available while users wait for the fix to be released. January 31, 2014 at 09:18 #2057 peter.kovacParticipant peter.kovacParticipantExcellent — /tmp mounted as noexec was the problem. Switching that allowed the install to complete properly and it now works like a champ. Fantastic response (especially since I didn’t tell you /tmp was noexec); I’m most impressed! January 31, 2014 at 09:24 #2061 BritgirlKeymaster BritgirlKeymasterOur pleasure 😉 
- 
		AuthorPosts
This topic was marked as solved, you can't post.

