Need to track the root cause of NoMachine session terminate

Forums / General Discussions / Need to track the root cause of NoMachine session terminate

  • This topic has 3 replies, 2 voices, and was last updated 5 years ago by kroy.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #16396

    How can I track log of NoMachine if someone session has been terminated.  There should be log in detail if user has terminated or terminated itself. I cant find correct log so it is difficult to track the root cause of session terminated.

    Can you please help me on this?


    You can monitoring sessions by using ./nxserver --history command ( It will show the complete list of sessions, including those that have been cleanly terminated or failed.


    ./nxserver –history command is not enough to find the root cause.  I want to check in detail all log how session was disconnected.


    Command --history can give quite completely information. Take a look on example:

    sudo /usr/NX/bin/nxserver --history
    Display Username  Remote IP Session ID                       Date                Status       Node           Type
    ------- --------- --------- -------------------------------- ------------------- ------------ -------------- ----------------------
    1005    user1    21274CD5BAC280EBA3CA1ED07BC051A8 2017-11-22 16:23:55 Connected    localhost:4000 physical-desktop
    1003    user2   034252F491CB5E6B2EFD0289EA9697C1 2017-11-20 18:26:31 Finished     localhost:4000 shadow
    1002    user1    A706C54F46C2D5C64C0F02E6BEE10767 2017-11-05 23:45:10 Failed       localhost:4000 unix-console
    1004    user3 -         C38F8C100B40A99BE41FDB06CCF38DAB 2017-11-16 08:40:05 Disconnected localhost:4000 unix-application

    In the “Status” column you have four possibilities:

    Connected – when it’s connected to the remote display.

    Disconnected – this status is available only for virtual desktop sessions. A session is marked as disconnected when it’s disconnected from the remote display. A disconnected session can be reconnected at any time even from a different machine (migration). While a session is disconnected, applications on remote stay running.

    Finnished – the session has been closed in a clean way and all NoMachine processes have been shut-down smoothly.

    Failed – Any of the NoMachine processes has failed to start or it has been “un-cleanly” terminated.

    More info you can find in link from previous post.

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

This topic was marked as solved, you can't post.