NXNodeExec: node with pid ‘13625’ and exit code ‘6’.

Forum / NoMachine for Linux / NXNodeExec: node with pid ‘13625’ and exit code ‘6’.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #4925
    mt
    Participant

    Hello,

    When I try to connect to a NoMachine – Version 4.3.23 server running on OpenSuse 12.2 I can see one picture of the remote display and the remote node hangs right after.

    I stay connected but the screen is not refreshed anymore.

    Here is what my nxserver.log says after a fresh restart and a connection attempt:

    2014-10-14 12:10:00 579.106 13483 NXSERVER Shutting down NoMachine server and services.

    2014-10-14 12:10:00 869.934 21471 NXSERVER WARNING! Xauthority not found in user environment.

    2014-10-14 12:10:00 953.203 21471 NXSERVER WARNING! Cookie not found at []

    2014-10-14 12:10:05 682.616 13483 NXSERVER Starting NoMachine server 4.3.23 and services.

    2014-10-14 12:10:24 423.822 13857 NXSERVER User ‘user’ logged in from ‘127.0.0.1’.

    2014-10-14 12:10:28 536.791 13607 NXSERVER WARNING! Process (13625) finished with signal ‘6’.

    2014-10-14 12:10:28 536.969 13607 NXSERVER WARNING! NXNodeExec: node with pid ‘13625’ just died with exit code ‘6’.

    2014-10-14 12:10:32 722.070 14034 NXNODE   WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 13001: Inappropriate ioctl for device from main::checkForRunningMonitorUnix.

    2014-10-14 12:11:01 224.644 13857 NXSERVER User ‘user’ from ‘127.0.0.1’ logged out.

    2014-10-14 12:11:02 885.983 13607 NXSERVER WARNING! Node was not started.

     

    Any ideas?

     

    #4931
    Haven
    Participant

    Hello mt,
    We will need nxserver and nxnode logs to investigate further. Please follow the instructions here:
    https://www.nomachine.com/AR07K00677
    Send them to issues[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.