Installation error Ubuntu 14.04.3

[ubuntuuser]

After issuing the following:

sudo dpkg -i nomachine_5.1.9_7_i386.deb

 

NX> 700 Running: ‘/etc/NX/nxserver’ –startup.
NX> 700 Cannot start NX server.

That command fails with the following error:
/etc/NX/nxserver: line 121: /usr/NX/bin/nxserver.bin: No such file or directory

 

Although the file is there:

ls /usr/NX/bin/nxserver.bin
/usr/NX/bin/nxserver.bin

full output from dpkg:

sudo dpkg -i nomachine_5.1.9_7_i386.deb
Selecting previously unselected package nomachine.
(Reading database … 208007 files and directories currently installed.)
Preparing to unpack nomachine_5.1.9_7_i386.deb …
Unpacking nomachine (5.1.9-7) …
Setting up nomachine (5.1.9-7) …
NX> 701 Starting update at: Thu Mar 03 10:07:50 2016.
NX> 701 Updating: nxclient version: 5.1.9.
NX> 701 Using installation profile: Ubuntu.
NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
NX> 701 Updating: nxplayer version: 5.1.9.
NX> 701 Using installation profile: Ubuntu.
NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
To connect the remote printer to the local desktop,
the user account must be a member of the CUPS System Group: lpadmin
NX> 701 Updating: nxnode version: 5.1.9.
NX> 701 Using installation profile: Ubuntu.
NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
NX> 701 Saving configuration file to: /usr/NX/etc/node.cfg.backup.
NX> 701 Creating configuration in: /usr/NX/etc/node.cfg.
NX> 701 Updating: nxserver version: 5.1.9.
NX> 701 Using installation profile: Ubuntu.
NX> 701 Update log is: /usr/NX/var/log/nxupdate.log.
/etc/NX/nxserver: line 121: /usr/NX/bin/nxserver.bin: No such file or directory
NX> 701 ERROR: Cannot shutdown nxserver.
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: Installation of NX server is broken:
NX> 701 ERROR: Missing /usr/NX/etc/keys/node.localhost.id_dsa ssh key file!
NX> 701 ERROR: Please uninstall and install again.
NX> 701 Bye.

 

[hawk]

Hello,

We aren’t able to reproduce your problem in our lab. We need more details. Could you run below commands, collect some logs and send output to forum[at]nomachine[dot]com, please?

1) lsb_release -a

2) uname -a

And we need nxinstall.log and nxupdate.log from /usr/NX/var/log/ directory. The proper way how to do this is explained inside this link https://www.nomachine.com/DT07M00098 .

[davidblumenthal]

I’m getting a similar error in 14.04.4.

$ sudo dpkg -i nomachine_5.1.9_7_i386.deb
[sudo] password for blumenthal:(Reading database … 253505 files and directories currently installed.)
Preparing to unpack nomachine_5.1.9_7_i386.deb …
/etc/NX/nxserver: line 121: /usr/NX/bin/nxserver.bin: No such file or directory
dpkg: error processing archive nomachine_5.1.9_7_i386.deb (–install):
subprocess new pre-installation script returned error exit status 127
Errors were encountered while processing:
nomachine_5.1.9_7_i386.deb

 

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

$ uname -a
Linux blumenthal 3.19.0-56-generic #62~14.04.1-Ubuntu SMP Fri Mar 11 11:03:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

 

I’ve attached nxinstall.log but nxupdate.log doesn’t exist.

[Britgirl]

Can you submit everything to forum[at]nomachine[dot]com? The output of ‘ls -ltr /usr/NX/ /etc/NX/ /var/NX/’ would also be helpful.

Also, it would be very useful if you could enable logs as per the instructions suggested by Hawk above.

 

[hawk]

@davidblumenthal From logs and informations you sent us, we are sure that you have installed x32 package (nomachine_5.1.9_7_i386.deb) on x64 Ubuntu which don’t have support for x32 architecture packages (unless you will install x32 libraries from ubuntu repository).

To fix it you need to uninstall actual package by sudo dpkg --purge nomachine, then remove all leftovers by executing command: rm -rf /usr/NX/ /var/NX/ /etc/NX/ and install x64 package from our website (nomachine_5.1.9_6_amd64.deb).

[davidblumenthal]

Thank you, that fixed it!  Since I’m not running an amd processor, the “amd” in the name of the 64-bit package threw me off.

[Author]

Posts