NoMachine error: Session Failed. Application terminated prematurely

[rfalba]

Hi,
I was able to use NoMachine free version successfully to connect from a Windows 10 machine to a remote Ubuntu 16.04 (Unity desktop env) machine. After changing to NoMachine Workstation 6.11.2.1 and NoMachine Enterprise Client 6.11.2.1, I get an error: The session negotiation failed. Error: Session failed, application terminated prematurely. The remote machine is using an Nvidia graphics card with proprietary drivers.

Remote:
$ grep DefaultDesktopCommand /usr/NX/etc/node.cfg
DefaultDesktopCommand “/etc/X11/Xsession ‘gnome-session –session=ubuntu'”

$ ls /usr/share/xsessions/
ubuntu.desktop xfce.desktop

$ grep ^Exec /usr/share/xsessions/ubuntu.desktop
Exec=gnome-session –session=ubuntu

Any pointers on how to fix this?

Attachments:

1. NoMachine-log-2020.08.31-12.22.11.zip

[graywolf]

Desktop log in Ubuntu 16.04 are located in $HOME/.cache/upstart. Search those files for errors.

[rfalba]

Hi,

Looked at those files but all of them have a modified date older than when I last experienced the error with NoMachine. So, I guess no log related to the error is being logged to those files?

[graywolf]

Look also into $HOME/.xsession-errors and /var/log/messages.

Could you list the files located in $HOME/.cache/upstart?

[rfalba]

Thanks a lot for the follow up!
$HOME/.xsession-errors is not being modified, modified date is 3 days older than when the error happened, and /var/log/messages doesn’t exist in the machine. /var/log/syslog doesn’t seem to have anything relevant either. Sorry, I’m really out of clues here, I’d really appreciate any help. Bellow are entries from journalctl, and client’s session logs.

**********************
ls -lat $HOME/.cache/upstart
**********************
drwx—— 2 user user 12288 Aug 28 13:04 .
-rw-r—– 1 user user 108 Aug 28 13:04 gpg-agent.log
-rw-r—– 1 user user 100 Aug 28 13:04 indicator-sound.log
-rw-r—– 1 user user 447 Aug 28 13:04 unity7.log
-rw-r—– 1 user user 1872 Aug 28 13:04 unity-panel-service.log
-rw-r—– 1 user user 2327 Aug 28 13:04 unity-settings-daemon.log
-rw-r—– 1 user user 114 Aug 28 09:37 unity-panel-service-lockscreen.log
-rw-r—– 1 user user 246 Aug 27 21:32 unity-panel-service.log.1.gz
-rw-r—– 1 user user 300 Aug 27 21:32 unity-settings-daemon.log.1.gz
-rw-r—– 1 user user 613 Aug 27 20:36 unity7.log.1.gz
-rw-r—– 1 user user 195 Aug 27 20:36 hud.log.1.gz
-rw-r—– 1 user user 88 Aug 27 20:36 update-notifier-crash-_var_crash__usr_bin_make.1004.crash.log
-rw-r—– 1 user user 112 Aug 27 20:36 update-notifier-crash-_var_crash__bin_bash.1004.crash.log.1.gz
-rw-r—– 1 user user 127 Aug 27 16:22 bamfdaemon.log.1.gz
-rw-r—– 1 user user 120 Aug 27 13:23 indicator-printers.log.1.gz
-rw-r—– 1 user user 313 Aug 27 02:32 unity-settings-daemon.log.2.gz
-rw-r—– 1 user user 211 Aug 27 01:18 hud.log.2.gz
-rw-r—– 1 user user 157 Aug 26 17:25 unity-panel-service.log.2.gz
-rw-r—– 1 user user 519 Aug 26 17:14 unity7.log.2.gz
-rw-r—– 1 user user 121 Aug 26 13:24 indicator-printers.log.2.gz
-rw-r—– 1 user user 130 Aug 26 12:04 unity-panel-service-lockscreen.log.1.gz
-rw-r—– 1 user user 321 Aug 25 23:57 unity-settings-daemon.log.3.gz
-rw-r—– 1 user user 356 Aug 25 19:40 unity-panel-service.log.3.gz
-rw-r—– 1 user user 1311 Aug 25 15:29 unity7.log.3.gz
-rw-r—– 1 user user 189 Aug 25 13:51 hud.log.3.gz
-rw-r—– 1 user user 129 Aug 25 13:51 bamfdaemon.log.2.gz
-rw-r—– 1 user user 121 Aug 25 13:25 indicator-printers.log.3.gz
-rw-r—– 1 user user 193 Aug 25 10:53 indicator-sound.log.1.gz
-rw-r—– 1 user user 359 Aug 24 16:19 unity-panel-service.log.4.gz
-rw-r—– 1 user user 270 Aug 24 16:19 unity-settings-daemon.log.4.gz
-rw-r—– 1 user user 131 Aug 24 15:21 bamfdaemon.log.3.gz
-rw-r—– 1 user user 791 Aug 24 15:16 unity7.log.4.gz
drwxr-xr-x 22 user user 4096 Aug 24 15:04 ..
-rw-r—– 1 user user 210 Aug 24 15:00 hud.log.4.gz
-rw-r—– 1 user user 118 Aug 24 13:35 indicator-printers.log.4.gz
-rw-r—– 1 user user 194 Aug 24 12:14 indicator-sound.log.2.gz
-rw-r—– 1 user user 118 Aug 23 13:36 indicator-printers.log.5.gz
-rw-r—– 1 user user 119 Aug 22 13:37 indicator-printers.log.6.gz
-rw-r—– 1 user user 290 Aug 22 06:39 unity-settings-daemon.log.5.gz
-rw-r—– 1 user user 247 Aug 21 20:04 unity-panel-service.log.5.gz
-rw-r—– 1 user user 422 Aug 21 17:03 unity7.log.5.gz
-rw-r—– 1 user user 119 Aug 21 13:38 indicator-printers.log.7.gz
-rw-r—– 1 user user 406 Aug 20 18:38 unity-settings-daemon.log.6.gz
-rw-r—– 1 user user 468 Aug 20 18:23 unity-panel-service.log.6.gz
-rw-r—– 1 user user 1691 Aug 20 17:31 unity7.log.6.gz
-rw-r—– 1 user user 279 Aug 20 17:30 hud.log.5.gz
-rw-r—– 1 user user 496 Aug 20 17:11 indicator-sound.log.3.gz
-rw-r—– 1 user user 170 Aug 20 15:37 window-stack-bridge.log.1.gz
-rw-r—– 1 user user 127 Aug 20 12:27 bamfdaemon.log.4.gz
-rw-r—– 1 user user 241 Aug 19 16:51 hud.log.6.gz
-rw-r—– 1 user user 318 Aug 19 16:45 unity-settings-daemon.log.7.gz
-rw-r—– 1 user user 154 Aug 19 16:36 unity-panel-service.log.7.gz
-rw-r—– 1 user user 782 Aug 19 13:42 unity7.log.7.gz
-rw-r—– 1 user user 127 Aug 19 13:17 bamfdaemon.log.5.gz
-rw-r—– 1 user user 292 Aug 19 13:15 indicator-sound.log.4.gz
-rw-r—– 1 user user 129 Aug 18 16:34 bamfdaemon.log.6.gz
-rw-r—– 1 user user 153 Aug 18 14:32 dbus.log.1.gz
-rw-r—– 1 user user 257 Aug 18 14:24 indicator-sound.log.5.gz
-rw-r—– 1 user user 450 Aug 18 13:42 dbus.log.2.gz
-rw-r—– 1 user user 225 Aug 18 13:41 at-spi2-registryd.log.1.gz
-rw-r—– 1 user user 114 Aug 18 13:41 gpg-agent.log.1.gz
-rw-r—– 1 user user 68 Aug 18 13:41 indicator-network.log.1.gz
-rw-r—– 1 user user 508 Aug 18 13:41 indicator-sound.log.6.gz
-rw-r—– 1 user user 145 Aug 18 13:41 bamfdaemon.log.7.gz
-rw-r—– 1 user user 57 Aug 18 13:41 click-user-hooks.log.1.gz
-rw-r—– 1 user user 102 Aug 18 13:41 gnome-keyring-ssh.log.1.gz
-rw-r—– 1 user user 60 Aug 18 13:41 ssh-agent.log.1.gz
-rw-r—– 1 user user 207 Aug 18 13:41 update-notifier-crash-_var_crash__usr_bin_compiz.1004.crash.log.1.gz
-rw-r—– 1 user user 218 Aug 18 13:41 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.1.gz
-rw-r—– 1 user user 72 Aug 18 13:41 update-notifier-release.log.1.gz
-rw-r—– 1 user user 68 Aug 18 13:41 upstart-event-bridge.log.1.gz
-rw-r—– 1 user user 100 Aug 18 13:41 window-stack-bridge.log.2.gz
-rw-r—– 1 user user 88 Aug 18 12:26 indicator-application.log.1.gz
-rw-r—– 1 user user 90 Aug 18 12:26 indicator-datetime.log.1.gz
-rw-r—– 1 user user 142 Aug 18 12:26 indicator-keyboard.log.1.gz
-rw-r—– 1 user user 238 Aug 18 12:21 hud.log.7.gz
-rw-r—– 1 user user 513 Aug 18 12:05 indicator-sound.log.7.gz
-rw-r—– 1 user user 507 Aug 18 12:05 dbus.log.3.gz
-rw-r—– 1 user user 241 Aug 18 12:05 at-spi2-registryd.log.2.gz
-rw-r—– 1 user user 117 Aug 18 12:05 gpg-agent.log.2.gz
-rw-r—– 1 user user 77 Aug 18 12:05 indicator-network.log.2.gz
-rw-r—– 1 user user 60 Aug 18 12:05 click-user-hooks.log.2.gz
-rw-r—– 1 user user 107 Aug 18 12:05 gnome-keyring-ssh.log.2.gz
-rw-r—– 1 user user 69 Aug 18 12:05 ssh-agent.log.2.gz
-rw-r—– 1 user user 241 Aug 18 12:05 update-notifier-crash-_var_crash__usr_bin_compiz.1004.crash.log.2.gz
-rw-r—– 1 user user 246 Aug 18 12:05 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.2.gz
-rw-r—– 1 user user 84 Aug 18 12:05 update-notifier-release.log.2.gz
-rw-r—– 1 user user 77 Aug 18 12:05 upstart-event-bridge.log.2.gz
-rw-r—– 1 user user 106 Aug 18 12:05 window-stack-bridge.log.3.gz
-rw-r—– 1 user user 88 Aug 18 12:04 indicator-application.log.2.gz
-rw-r—– 1 user user 89 Aug 18 11:25 indicator-application.log.3.gz
-rw-r—– 1 user user 446 Aug 18 11:00 dbus.log.4.gz
-rw-r—– 1 user user 226 Aug 18 10:59 at-spi2-registryd.log.3.gz
-rw-r—– 1 user user 114 Aug 18 10:59 gpg-agent.log.3.gz
-rw-r—– 1 user user 69 Aug 18 10:59 indicator-network.log.3.gz
-rw-r—– 1 user user 57 Aug 18 10:59 click-user-hooks.log.3.gz
-rw-r—– 1 user user 102 Aug 18 10:59 gnome-keyring-ssh.log.3.gz
-rw-r—– 1 user user 61 Aug 18 10:59 ssh-agent.log.3.gz
-rw-r—– 1 user user 220 Aug 18 10:59 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.3.gz
-rw-r—– 1 user user 72 Aug 18 10:59 update-notifier-release.log.3.gz
-rw-r—– 1 user user 69 Aug 18 10:59 upstart-event-bridge.log.3.gz
-rw-r—– 1 user user 100 Aug 18 10:59 window-stack-bridge.log.4.gz
-rw-r—– 1 user user 390 Aug 18 10:30 dbus.log.5.gz
-rw-r—– 1 user user 230 Aug 18 10:30 at-spi2-registryd.log.4.gz
-rw-r—– 1 user user 114 Aug 18 10:30 gpg-agent.log.4.gz
-rw-r—– 1 user user 69 Aug 18 10:30 indicator-network.log.4.gz
-rw-r—– 1 user user 57 Aug 18 10:30 click-user-hooks.log.4.gz
-rw-r—– 1 user user 102 Aug 18 10:30 gnome-keyring-ssh.log.4.gz
-rw-r—– 1 user user 61 Aug 18 10:30 ssh-agent.log.4.gz
-rw-r—– 1 user user 216 Aug 18 10:30 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.4.gz
-rw-r—– 1 user user 72 Aug 18 10:30 update-notifier-release.log.4.gz
-rw-r—– 1 user user 69 Aug 18 10:30 upstart-event-bridge.log.4.gz
-rw-r—– 1 user user 100 Aug 18 10:30 window-stack-bridge.log.5.gz
-rw-r—– 1 user user 89 Aug 18 10:29 indicator-application.log.4.gz
-rw-r—– 1 user user 130 Aug 14 16:01 unity-panel-service-lockscreen.log.2.gz
-rw-r—– 1 user user 543 Aug 12 14:31 dbus.log.6.gz
-rw-r—– 1 user user 246 Aug 12 11:40 at-spi2-registryd.log.5.gz
-rw-r—– 1 user user 117 Aug 12 11:40 gpg-agent.log.5.gz
-rw-r—– 1 user user 77 Aug 12 11:40 indicator-network.log.5.gz
-rw-r—– 1 user user 411 Aug 12 11:40 update-notifier-release.log.5.gz
-rw-r—– 1 user user 60 Aug 12 11:40 click-user-hooks.log.5.gz
-rw-r—– 1 user user 107 Aug 12 11:40 gnome-keyring-ssh.log.5.gz
-rw-r—– 1 user user 70 Aug 12 11:40 ssh-agent.log.5.gz
-rw-r—– 1 user user 248 Aug 12 11:40 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.5.gz
-rw-r—– 1 user user 78 Aug 12 11:40 upstart-event-bridge.log.5.gz
-rw-r—– 1 user user 106 Aug 12 11:40 window-stack-bridge.log.6.gz
-rw-r—– 1 user user 99 Aug 12 11:35 indicator-application.log.5.gz
-rw-r—– 1 user user 493 Aug 12 11:08 dbus.log.7.gz
-rw-r—– 1 user user 245 Aug 12 11:08 at-spi2-registryd.log.6.gz
-rw-r—– 1 user user 77 Aug 12 11:08 indicator-network.log.6.gz
-rw-r—– 1 user user 117 Aug 12 11:08 gpg-agent.log.6.gz
-rw-r—– 1 user user 60 Aug 12 11:08 click-user-hooks.log.6.gz
-rw-r—– 1 user user 107 Aug 12 11:08 gnome-keyring-ssh.log.6.gz
-rw-r—– 1 user user 70 Aug 12 11:08 ssh-agent.log.6.gz
-rw-r—– 1 user user 249 Aug 12 11:08 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.6.gz
-rw-r—– 1 user user 84 Aug 12 11:08 update-notifier-release.log.6.gz
-rw-r—– 1 user user 78 Aug 12 11:08 upstart-event-bridge.log.6.gz
-rw-r—– 1 user user 248 Aug 12 11:08 window-stack-bridge.log.7.gz
-rw-r—– 1 user user 88 Aug 12 11:07 indicator-application.log.6.gz
-rw-r—– 1 user user 118 Aug 12 11:07 indicator-session.log.1.gz
-rw-r—– 1 user user 110 Aug 12 10:37 indicator-bluetooth.log.1.gz
-rw-r—– 1 user user 90 Aug 12 10:37 indicator-datetime.log.2.gz
-rw-r—– 1 user user 239 Aug 12 10:03 at-spi2-registryd.log.7.gz
-rw-r—– 1 user user 117 Aug 12 10:03 gpg-agent.log.7.gz
-rw-r—– 1 user user 78 Aug 12 10:03 indicator-network.log.7.gz
-rw-r—– 1 user user 60 Aug 12 10:03 click-user-hooks.log.7.gz
-rw-r—– 1 user user 107 Aug 12 10:03 gnome-keyring-ssh.log.7.gz
-rw-r—– 1 user user 70 Aug 12 10:03 ssh-agent.log.7.gz
-rw-r—– 1 user user 249 Aug 12 10:03 update-notifier-crash-_var_crash__usr_NX_bin_nxnode.bin.1004.crash.log.7.gz
-rw-r—– 1 user user 86 Aug 12 10:03 update-notifier-release.log.7.gz
-rw-r—– 1 user user 78 Aug 12 10:03 upstart-event-bridge.log.7.gz
-rw-r—– 1 user user 89 Aug 11 19:15 indicator-application.log.7.gz
-rw-r—– 1 user user 253 Jul 29 10:08 session-migration.log.1.gz

***********************
client session logs:
***********************
Info: Starting NoMachine version 6.11.2.
Info: Loading settings from ‘C:\Users\user\.nx\config\player.cfg’.
Info: Loaded translation files for ‘English’.
10120 18972 12:01:27 173.291 Main: Creating the client session.
10120 18972 12:01:27 173.291 ClientSession: Initializing session at 0x0317eda8.
10120 20128 12:01:27 525.397 MdnsdListThread: WARNING! Could not open directory ‘C:\Users\user\.nx\cache’.
10120 18972 12:01:27 893.463 ClientSession: Going to add child with pid ‘1468’ and process at 0x00000000.
10120 18972 12:01:27 894.460 ClientSession: Now there are 1 running child processes.
10120 18972 12:01:27 894.460 ClientSession: Initialized session at 0x0317eda8.
10120 18972 12:01:27 901.444 Main: Entering the GUI event loop.
Info: Slave server running with pid 19856.
Info: Listening to slave connections on port 42959.
10120 22412 12:01:32 161.641 ClientUpnp: WARNING! Mapping of port ‘4295’ failed after ‘4267’ ms.
10120 18972 12:01:41 817.139 ClientSession: Starting session at 0x0317eda8.
10120 18972 12:01:41 817.139 ClientSession: Going to start session ‘C:\Users\user\Documents\NoMachine\conn’.
10120 18972 12:01:41 845.068 Connection: Initializing connection at 0x03f14fd0.
10120 18972 12:01:41 847.063 Connection: Initialized connection at 0x03f14fd0.
10120 18972 12:01:41 847.063 Connection: Starting connection at 0x03f14fd0.
10120 18972 12:01:41 847.063 ClientDaemonConnector: Starting a new connection to host ‘myhost’ on port ‘4000’.
10120 18972 12:01:41 850.055 Connection: Started connection at 0x03f14fd0.
10120 18972 12:01:41 863.022 ClientSession: Started session at 0x0317eda8.
Info: Connection to 172.25.113.43 port 4000 started at 12:01:42 059.528.
10120 22908 12:01:42 648.033 ClientSession: A valid certificate for this server was found.
10120 22412 12:01:46 064.368 ClientUpnp: WARNING! Mapping of port ‘4295’ failed after ‘4251’ ms.
10120 18972 12:01:51 165.425 ClientSession: Going to query the server for available services.
10120 18972 12:01:54 620.657 ClientSession: Selecting the destination node.
10120 18972 12:01:54 934.861 ClientSession: Going to query the node for available services.
10120 18972 12:01:55 069.520 ClientSession: Going to create a new session.
10120 18972 12:01:55 214.150 Keyboard: Current model ‘evdev’ session model ‘evdev’ layout ‘en_US’ variant ‘(empty)’ options ‘(empty)’.
10120 18972 12:02:02 326.108 Connection: Connection at 0x03f14fd0 failed.
10120 18972 12:02:02 327.112 ClientSession: Runnable at 0x03f14fd0 caused the session at 0x0317eda8 to fail.
10120 18972 12:02:02 327.112 ClientSession: Failing reason is ‘The session negotiation failed.

Error: Session failed, application terminated prematurely.’.
Info: Connection to 172.25.113.43 port 4000 closed at 12:02:02 327.112.
10120 18972 12:02:02 355.036 ClientSession: Stopping session at 0x0317eda8.
10120 18972 12:02:02 379.988 Connection: Stopping connection at 0x03f14fd0.
Info: Slave server running with pid 22416.
10120 18972 12:02:02 379.988 ClientDaemonConnector: Stopping the current connection.
Info: Listening to slave connections on port 64849.
10120 18972 12:02:02 380.970 Connection: Stopped connection at 0x03f14fd0.
10120 18972 12:02:02 405.906 ClientSession: Stopped session at 0x0317eda8.

****************
$ journalctl -b -0
****************
…
…
Sep 02 10:02:17 host nxexec[961]: pam_unix(nx:session): session opened for user user by (uid=127)
Sep 02 10:02:17 hosy systemd-logind[1040]: New session c5 of user user
Sep 02 10:02:17 host systemd[1]: Started Session c5 of user user
Sep 02 10:02:18 host nxexec[961]: pam_unix(nx:session): session closed for user user
Sep 02 10:02:18 host systemd-logind[1040]: Removed session c5.
…
…

[graywolf]

take a look of unity7.log and unity7.log.*.gz about the date and time you got the problem.

Try also this: run a custom NoMachine session with only xterm into it. Use xterm to test the Unity support with command /usr/lib/nux/unity_support_test -p.

[rfalba]

The error occurred on August 30th, those file were last modified on the 28th, so it seems nothing was logged there related to the error. I have reproduced the error several times until today, all files in $HOME/.cache/upstart are unchanged. When I try to run a custom session with only the console I get a completely black screen that after a minute or so terminates.

[graywolf]

Isn’t xterm installed? That could be the reason console session didn’t work.
Look at errors nxserver.log: there are recorded the unexpected terminations or relevant processes and missing xterm problem.

[rfalba]

Xterm is installed but I’m not sure how to test it can run without issues. I don’t have access to the physical machine. Logs in nxserver.log are the following:

**************
nxserver.log
**************
$ sudo cat /usr/NX/var/log/nxserver.log
2020-09-14 10:18:17 991.556 11776 NXSERVER User ‘user’ logged in from ‘x.x.x.x’ using authentication method NX-password.
2020-09-14 10:18:40 142.870 11804 NXNODE WARNING! Cannot open: /proc/11876/environ.
2020-09-14 10:18:40 142.903 11804 NXNODE WARNING! Error is: 2, ‘No such file or directory’.
2020-09-14 10:19:17 087.592 11776 NXSERVER User ‘user’ from ‘x.x.x.x’ logged out.

[graywolf]

Hello. Do you still experience that problem?

Btw, provided Xterm is installed, console custom session must just work. Otherwise something has gone bad on your system or in NoMachine installation and errors would have been recorded in nxserver.log and /usr/NX/var/log/node/.

[Author]

Posts