Cannot login to Ubuntu NX server – could not retrieve NX scripts directory

Forum / NoMachine for Linux / Cannot login to Ubuntu NX server – could not retrieve NX scripts directory

  • This topic has 1 reply, 2 voices, and was last updated 7 years ago by zaq.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #14502
    higrys
    Participant

    The latest version of NoMachine Server (Free edition – 5.2.21) stopped running on Ubuntu 14.04. I used to use it for a long time but after the update I cannot login any more to the NX server running on my Ubuntu laptop. After a bit of digging, the problem boils down to nxexec command always failing with “Could not retrieve NX scripts directory” error. In log files any command issued via nxexec fails with the same error.

    Same if I try to run it manually:

    🕠  [root@Lothlorien:/home/usr/NX/var/log] # /usr/NX/bin/nxexec nxfwget.sh iptables INPUT
    Error: Could not retrieve NX scripts directory.

    Stracing the problem does not bring any more info:

    readlink(“/proc/17754/exe”, “/home/usr/NX/bin/nxexec”, 256) = 23
    lstat(“/etc/NX/server/localhost/client.cfg”, {st_mode=S_IFREG|0644, st_size=607, …}) = 0
    open(“/etc/NX/server/localhost/client.cfg”, O_RDONLY) = 3
    fstat(3, {st_mode=S_IFREG|0644, st_size=607, …}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fada4771000
    read(3, “################################”…, 4096) = 607
    read(3, “”, 4096)                       = 0
    close(3)                                = 0
    munmap(0x7fada4771000, 4096)            = 0
    lstat(“/etc/NX/node/localhost/client.cfg”, 0x7ffece9421c0) = -1 ENOENT (No such file or directory)
    lstat(“/etc/NX/player/localhost/client.cfg”, 0x7ffece9421c0) = -1 ENOENT (No such file or directory)
    write(2, “Error: Could not retrieve NX scr”…, 48Error: Could not retrieve NX scripts directory.

    I tried to add the last files which were missing also providing the configuration files as they (I think) should be. Tried all the combinations.

    I remove NoMachine completely (including manually removing all the /usr/NX/ /etc/NX etc. directories after uninstalling with dpkg. Clean install produces exactly the same errors. I reinstalled it using dpkg, later repeated it with .tar.gz. All the same. I always used standard directory structure.

    #14556
    zaq
    Participant

    Hello higrys

    We couldn’t reproduce the problem in our laboratory. Could you
    reinstall NoMachine again and reproduce problem?

    1. Uninstall NoMachine:

    sudo dpkg -P nomachine

    2. Remove all directories:

    sudo rm -rf /usr/NX /etc/NX /var/NX

    3. Check architecture of your OS:

    uname -a

    If the output include: x86_64 x86_64 x86_64 GNU/Linux
    you should use x64 package:

    nomachine_5.2.21_1_amd64.deb

    if you got: i686 GNU/Linux or i386 GNU/Linux
    please use x32 package:

    nomachine_5.2.21_1_i386.deb

    4. Install NoMachine.

    x64 system:

    sudo dpkg -i nomachine_5.2.21_1_amd64.deb

    x32 system:

    sudo dpkg -i nomachine_5.2.21_1_i386.deb

    5. Gather logs and reproduce the problem like in this link:

    https://www.nomachine.com/DT07M00098#1

    and send packed logs 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.