Session negotiation fails after update to 7.0

Forum / NoMachine for Linux / Session negotiation fails after update to 7.0

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #31195
    Frank Steiner


    after upgrading from 6.12.3 to 7.0.211 NoMachine stopped working. Client and Server both SuSE Linux Enterprise 15 SP2, we are connecting to the physical desktop using Linux passwords. nxserver.log and nxerror.log show:

    ==> nxerror.log <==
    8304 8477 12:49:36 695.289 HostWmRunningHelper: WARNING! Failed to open display ‘:0’.

    ==> nxserver.log <==
    8304 8304 2021-01-11 12:49:36 695.581 NXSERVER WARNING! Cannot check WM on display :0 EEXIST
    8442 8442 2021-01-11 12:49:37 143.785 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user xxx –priority realtime –mode 0 –pid 28 -H 5’ with pid ‘8478/8478’ finished with exit code 1 after 0,429 seconds.
    8442 8442 2021-01-11 12:49:37 143.890 NXSERVER WARNING! NXExec process 8478 finished abnormally with exit code 1.
    8442 8442 2021-01-11 12:49:37 144.057 NXSERVER ERROR! Cannot connect to local node.

    Downgrading to 6.12.3 makes it work again without problems. I collected the debug log, should I upload it somewhere?







    The logs can be sent directly to forum[at]nomachine[dot]com.



    At first glance this looks like a known issue described here:

    The nxnode we create for user ‘fst’ fails immediatelly.

    Please check if the nxerror.log file in the ‘<user home>/.nx’ directory
    contains the errors similar to the ones described in that document:

    23813 23813 16:55:23 743.409 File: ERROR! Can't lock FD#7 with mask 0x5.
    23813 23813 16:55:23 743.506 File: ERROR! Error is 9, 'Bad file descriptor'.
    Error: Cannot lock log file '/home/user01/.nx/nxserver.log'

    If yes, the workaround for this problem is described in the same document.

    Please let us known if it helped the situation or, if it don’t, please
    send us the logs from ‘<user home>/.nx’ directory at the same address as before.


    Frank Steiner

    Yes, that was the reason. Sorry I missed that, but I wasn’t aware it would log in the home directory, so I missed the error messages there 🙂 and couldn’t google for it.


    Thanks for your help!

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

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