Not able to start nxserver on Ubuntu 16.04

Forums / NoMachine for Linux / Not able to start nxserver on Ubuntu 16.04

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #27439
    Avatarresmi
    Participant

    Hi,

    I installed NoMachine, but had got some errors as below.

    But I do see the id_rsa and id_dsa created successfully.

    Still I am not able to start the server.

    Do not see it when i check ps.

    Copied the status below.

     

    Installation:

    ————–

    Selecting previously unselected package nomachine.

    (Reading database … 266198 files and directories currently installed.)

    Preparing to unpack nomachine_6.9.2_1_amd64.deb …

    Unpacking nomachine (6.9.2-1) …

    Setting up nomachine (6.9.2-1) …

    NX> 700 Starting install at: Tue May 12 12:18:44 2020.

    NX> 700 Installing: nxclient version: 6.9.2.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Compiling the USB module.

    NX> 700 Installing: nxplayer version: 6.9.2.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 To connect the remote printer to the local desktop,

    NX> 700 the user account must be a member of the CUPS System Group: lpadmin.

    NX> 700 Installing: nxnode version: 6.9.2.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Creating configuration in: /usr/NX/etc/node.cfg.

    NX> 700 Node install completed with warnings.

    NX> 700 Please review the install log for details.

    NX> 700 Installing: nxserver version: 6.9.2.

    NX> 700 Using installation profile: Ubuntu.

    NX> 700 Install log is: /usr/NX/var/log/nxinstall.log.

    NX> 700 Creating configuration in: /usr/NX/etc/server.cfg.

    NX> 700 ERROR: Cannot change ownership of: /usr/NX/etc/server.cfg to: nx:nx.

    NX> 700 ERROR: Cannot change ownership of: /etc/NX/nxserver to: nx:nx.

    NX> 700 ERROR: Cannot install file: /usr/NX/etc/keys/node.localhost.id_dsa.pub.

    /bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys: No such file or directory

    NX> 700 ERROR: Cannot install file: /usr/NX/etc/keys/node.localhost.id_rsa.pub.

    /bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys: No such file or directory

    NX> 700 ERROR: Cannot install file: /usr/NX/etc/keys/node.localhost.id_dsa.pub.

    /bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys2: No such file or directory

    NX> 700 ERROR: Cannot install file: /usr/NX/etc/keys/node.localhost.id_rsa.pub.

    /bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys2: No such file or directory

    NX> 700 Server install completed with warnings.

    NX> 700 Please review the install log for details.

    NX> 700 Install completed with errors at: Tue May 12 12:19:00 2020.

    NX> 700 NoMachine was configured to run the following services:

    NX> 700 NX service on port: 4000

     

    Status:

    ——–

    ‚óŹ nxserver.service – NoMachine Server daemon

    Loaded: loaded (/lib/systemd/system/nxserver.service; enabled; vendor preset: enabled)

    Active: failed (Result: start-limit-hit) since Wed 2020-05-13 20:11:24 IST; 17min ago

    Process: 24122 ExecStart=/etc/NX/nxserver –daemon (code=exited, status=216/GROUP)

    Main PID: 24122 (code=exited, status=216/GROUP)

     

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: nxserver.service: Service hold-off time over, scheduling restart.

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: Stopped NoMachine Server daemon.

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: nxserver.service: Start request repeated too quickly.

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: Failed to start NoMachine Server daemon.

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: nxserver.service: Unit entered failed state.

    May 13 20:11:24 blr-ubuntu-42 systemd[1]: nxserver.service: Failed with result ‘start-limit-hit’.

     

    Regards,

    Resmi

    #27517
    Avatarzaq
    Contributor

    Hello resmi,

    Looks like your issue is related to a presence of nx user.
    Probably user nx was removed during the installation process.

    Do you use domain users/LDAP/ActiveDirectory? Do you have non
    standard restrictions for users?

    A standard set of logs will be helpful. Gather them like is
    described in:

    https://www.nomachine.com/DT10O00163#1.1

    and send to forum[at]nomachine[dot]com.

Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.