Duplicate processes when NoMachine server is running

Forums / NoMachine for Linux / Duplicate processes when NoMachine server is running

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #23983
    ticotexas
    Participant

    Is it normal to have most processes duplicated? It seems like NoMachine has most things running duplicated. All the processes have my username in the System Monitor.

    The reason I ask is because the Java process is for something I have called remote-launcher-server that uses a specific port. When NoMachine was running, every time I booted, it would try to start that twice and give an error about the port is “Failed to start server, Address already in use, (Bind Failed)”. Once I stopped NoMachine server from starting, that error stopped, and I noticed no duplicates.

    Is there a way to have NoMachine server running, so that I can connect remotely, but avoid this duplicate process issue?

    #24014
    ticotexas
    Participant

    See attachment.

    Attachments:
    #24019
    Mth
    Contributor

    Hello.

    This doubling of processes is most likely caused by the NoMachine starting the virtual desktop because it cannot detect the physical
    desktop and the server.cfg key CreateDisplay is set to 1.

    To avoid NoMachine creating it on each startup you can edit

    /usr/NX/etc/server.cfg

    config file and set this key to 0 or comment it.

    This key may be set to 1 because when you first connected, NoMachine had no physical session detected, asked to create “Display on demand” (which is simple virtual session). When you select yes, there is a checkbox to select, which will make NoMachine to start this session automatically on startup.

    Setting it to 0 will make it stop, but it does not solve the issue that you have running physical desktop and NoMachine did not detect it.

    If this key is set to 0 and after doing

    # /etc/NX/nxserver –restart

    you would not get NX> 161 Enabled service: nxnode. and you cannot access your desktop, we would require logs
    to investigate this further.

    Article on how to collect logs:

    https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

    After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.

    /Mth

    #24036
    ticotexas
    Participant

    @Mth

    Yes, that was exactly it. Thank you very much! I really appreciate it. Now, it works perfectly.

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

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