501 ERROR: Session failed, application terminated prematurely

Forum / NoMachine for Linux / 501 ERROR: Session failed, application terminated prematurely

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • December 11, 2017 at 16:11 #16844
    deness
    Participant

    Hi,

    I have Linux machine with NX installed. I did connect from my Windows Laptop (5.3.12) to this Linux machine (5.3.10). Today I have updated some packages on my Linux machine and did a reboot. Now I can’t connect to Linux via NX session, but I can connect via PuTTY.

    error in nxserver.log is:

    2017-12-11 15:56:16 578.425 32197 NXNODE   NXParser: signal ‘CHLD’ received.

    2017-12-11 15:56:16 578.537 32197 NXNODE   Received ‘SIGCHLD’ signal:going to handle it

    2017-12-11 15:56:16 578.597 32197 NXNODE   handleSIGCHLD

    2017-12-11 15:56:16 578.655 32197 NXNODE   handleSIGCHLD checking child: 32248

    2017-12-11 15:56:16 578.794 32197 NXNODE   Going to call NXProcessRemove(32248)

    2017-12-11 15:56:16 578.926 32197 NXNODE   Process ‘/bin/bash -c exec -a – /bin/bash -c ‘/etc/gdm/Xsession ‘\”gnome-session –session=gnome’\” with pid ‘32248/32248’ finished with signal 15 after 5,564 seconds.

    2017-12-11 15:56:16 578.999 32197 NXNODE   session monitor: application finished.

    2017-12-11 15:56:16 579.107 32197 NXNODE   session monitor: is not agent closing ‘1’.

    2017-12-11 15:56:16 579.162 32197 NXNODE   session monitor: is disabled terminate on sigchild ”.

    2017-12-11 15:56:16 579.223 32197 NXNODE   This session is terminate on SIGCHLD, dont need receive status from Agent.

    2017-12-11 15:56:16 579.273 32197 NXNODE   session monitor: no others applications to wait going to shutting down session

    2017-12-11 15:56:16 579.423 32197 NXNODE   ERROR! Application terminated too early.

    2017-12-11 15:56:16 579.485 32197 NXNODE   Notified server that application terminated.

    2017-12-11 15:56:16 579.538 32197 NXNODE   NXClientMonitor::stop: Function start.

    2017-12-11 15:56:16 579.596 32197 NXNODE   NXClientMonitor: NXClient –monitor is running.

    2017-12-11 15:56:16 579.579 32173 NXSERVER Something to read on FD#11.

    2017-12-11 15:56:16 579.679 32197 NXNODE   Previous message repeated 1 time

    2017-12-11 15:56:16 579.716 32197 NXNODE   NXClientMonitor: NXClient –monitor status changed from connected to terminating.

    2017-12-11 15:56:16 579.788 32197 NXNODE   NXClientMonitor: NXClient –monitor is running.

    2017-12-11 15:56:16 579.806 32173 NXSERVER Handling code 249 with function handleMasterGoingToShutdown.

    2017-12-11 15:56:16 579.846 32197 NXNODE   NXConnectLocal to localhost:25001 from NXClientMonitor::sendTerminateMessageToNxMonitor.

    2017-12-11 15:56:16 579.904 32173 NXSERVER Get session id: 52F137F9F1195236E510E8F9B447CF08.

    2017-12-11 15:56:16 580.017 32173 NXSERVER Hiding virtual session in session list.

    2017-12-11 15:56:16 581.620 32173 NXSERVER Get session id: 52F137F9F1195236E510E8F9B447CF08.

    2017-12-11 15:56:16 581.679 32173 NXSERVER Informing the the multi-node server about 52F137F9F1195236E510E8F9B447CF08.

    2017-12-11 15:56:16 581.753 32173 NXSERVER Get session id: 52F137F9F1195236E510E8F9B447CF08.

    2017-12-11 15:56:16 581.837 32173 NXSERVER Handling code 247 with function handleSessionShutdownApplicationTerminatedTooEarly.

    2017-12-11 15:56:16 581.890 32173 NXSERVER Handle session shutdown application terminated too early.

    2017-12-11 15:56:16 581.941 32173 NXSERVER Connection to client still open.

    2017-12-11 15:56:16 582.091 32173 NXSERVER ERROR! Sending error message ‘NX> 501 ERROR: Session failed, application terminated prematurely.’

    Please find attached the complete debug log.

    Thank you for your help in advance!

    Best regards,

    deness

     

    December 11, 2017 at 16:16 #16847
    Britgirl
    Keymaster

    The attachments were too big. Try sending them to forum[at]nomachine[dot]com. Also, please tell us the Linux distribution and version, and what NoMachine packages you have installed from the website.

    December 12, 2017 at 10:01 #16848
    deness
    Participant

    OS: Linux lu357091 4.4.90-92.50-default #1 SMP Mon Dec 4 08:06:54 UTC 2017 (3daf360) x86_64 x86_64 x86_64 GNU/Linux

    SUSE Linux Enterprise Server 12 (x86_64)

    VERSION = 12

    PATCHLEVEL = 2

    # This file is deprecated and will be removed in a future service pack or release.

    # Please check /etc/os-release for details about this release.

    NoMachine: 5.3.10 (nomachine_5.3.10_6_x86_64.rpm)

    Attachments:
    1. nomachine_logs.zip
    December 13, 2017 at 12:26 #16888
    og00r
    Contributor

    Can you check or send us .xsession-errors files in home directory? (there could be few files, check all).

    From the logs I can see that you don’t have any running Xsession which you want to connect? To check this run the user command “ps -ef | grep X”

    What version of gdm and gnome do you have after updating your system? Was it these that you updated just before NoMachine stopped working?

    December 14, 2017 at 14:56 #16898
    deness
    Participant

    Hi,

    issue is solved. Obviously OS update broke xserver/start of Xsession. I have updated NVIDIA graphics driver and now it works.

    Thank you!

    Best regards,

    deness

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)

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