NoMachine Linux Workstation 6.1.6 generates logfiles

Forums / NoMachine Terminal Server Products / NoMachine Linux Workstation 6.1.6 generates logfiles

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #18396

    I keep running out of inodes on my machine.

    /usr/NX/var/db/failed gets populated with 2.5 million files over a few weeks.

    /usr/NX/var/log/nxserver.log keeps printing this message very 10 seconds

    2018-05-14 17:27:38 824.344 98631 NXSERVER WARNING! D4962003C748F00ACA445538A9BE8844 nxnode died with exit code 11.
    2018-05-14 17:27:38 887.766 98631 NXSERVER WARNING! Session D4962003C748F00ACA445538A9BE8844 crashed on display 0.
    2018-05-14 17:27:41 245.724 98631 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user lightdm –priority realtime –mode 0 –pid 25’ with pid ‘111238/111238’ finished with exit code 11 after 2,344 seconds.

    This perpetual logging generates a huge number of files where my drive just runs out of inodes.


    Linux (Remote) terminal workstation: 6.1.6
    Client: MacOS X (10.13.4) – NoMachine version: 6.1.6

    Linux OS: 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:34:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

    Window Manager: Xfce4


    Hello mtariqgyahoo,

    For some reason nxnode process is crashing on your Linux system. Consecutive failed attempts of restarting it, lead to generation of huge number of leftover files in /usr/NX/var/db/failed directory.

    It’s possible to remove them by running in terminal:

    sudo /etc/NX/nxserver –history clear

    To prevent creation of the next files you can temporarily disable nxserver by running:

    sudo /usr/NX/bin/nxserver –shutdown

    Next, we should try to understand why nxnode process is not working correctly. Gather server-side logs from your linux machine according to these instructions:

    Gather, if possible, backtrace of crashing nxnode according to:

    Send backtrace and 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.