og00r

[og00r]

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?

[og00r]

Logs are unclear, something is blocking sockets. We cannot reproduce issue. Maybe the problem is with anti-virus / firewall? Which one are you using?

[og00r]

Can you enable logs by edit the installationDirectory/NoMachine/etc/server.cfg.
Uncomment and set the following:
SessionLogLevel 7
then restart nxserver with command:
installationDirectory/NoMachine/bin/nxserver –restart
and send us again logs? Logs of daemon process are missing and restart is requested to enable them.

[og00r]

I see a lot of errors related to access to home directory, can you check if home directory of user tnt has correct permissions?

To do that use:
“ls -l /home/”

and then check directory .nx inside with command
“ls -la /home/tnt/” (option “a” is requested here, because it is hidden directory)
In both cases owner of directory should be tnt and should have full rights on them (rwx)

[og00r]

@munsen70
it looks like 10000 lines could be too little for debug.

But please:
If You have screen lock enabled please disable it. (Settings -> Power -> black screen -> never)

then:
try “sudo grep ‘1101 NXSERVER’ /usr/NX/var/log/nxserver.log > nxserver1101.log”
but if nxserver1101.log will be to big to send, then use that command:
“sudo grep ‘1101 NXSERVER’ /usr/NX/var/log/nxserver.log | head -30000 > nxserver1101.log”

simliar things make for pid 27010:
try “sudo grep ‘27010’ /usr/NX/var/log/nxserver.log > nxserver27010.log”
but if nxserver27010.log will be to big to send, remove it and then use those two commands:
“sudo grep ‘27010’ /usr/NX/var/log/nxserver.log | head -10000 >> nxserver27010.log”
“sudo grep ‘27010’ /usr/NX/var/log/nxserver.log | tail -10000 >> nxserver27010.log”

next useful commands:
“sudo mv /usr/NX/var/log/nxserver.log /usr/NX/var/log/nxserver.log.old”
then restart
“sudo /etc/NX/nxserver –restart”
wait 30-60 seconds
then try to connect
and then “sudo cp -p /usr/NX/var/log/nxserver.log nxserver-restart.log”
nxserver-restart.log should be enough small to send us also, if not then:
sudo grep -a -i -e ‘nxframebuffer’ -e ‘checklocalsession’ /usr/NX/var/log/nxserver.log > nxserver-restart.log

then send please nxserver1101.log, nxserver27010.log and nxserver-restart.log.

As usual send to our email address forum[at]nomachine[dot]com

[og00r]

New ubuntu (17.10) moved by default to Wayland and in same time they moved from unity to gnome3, so there is a lot of changes and incoming NoMachine version 6.0 should worked there correctly, but until that time please change in /usr/NX/etc/node.cfg field:
DefaultDesktopCommand “/etc/X11/XSession ‘gnome-session –session=ubuntu'”
to
DefaultDesktopCommand “env XDG_CURRENT_DESKTOP=ubuntu:GNOME GNOME_SHELL_SESSION_MODE=ubuntu dbus-launch –exit-with-session gnome-session –session=ubuntu”
it could help in your case.

[og00r]

Use ls -ltr /usr/NX/var/log/node/ to check which directories are newest one. Take few from the bottom of list and pack them.

[og00r]

Strange, check how big are files and directories there with command:
“sudo du -ha /usr/NX/var/log/”

if nxserver.log or nxerror.log is too big, then try get last lines with command:
sudo tail -10000 <path_to_log_file> > newLogfile.log

Most requested files in that case are nxserver.log (with enabled SessionLogLevel 7 in server.cfg), nxerror.log and directory /usr/NX/var/log/node/ with its subdirectories.

[og00r]

I don’t see nothing wrong in that part of nxerror.log.
I will need logs (with debug) and another output of:

ps awwxo uid,ppid,pid,sid,etime,comm,args

Please enable debug, restart nxserver (sudo /usr/NX/bin/nxserver –restart) and send server side logs to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.

[og00r]

For the ‘/var/log/Xorg.*.log’ I have 4 different ones, is there a specific one I should look at

Look at newest one.

Please check also file /usr/NX/var/log/nxerror.log for errors related with WMRunning, because process list looks ok.

[og00r]

“grep: ‘wayland: No such file or directory
bash: xorg’: command not found…”
it is wrong because command is wrong,
“ps -ef | grep -i E ‘wayland|xorg” you miss dash before “E” . should be “ps -ef | grep -i –E ‘wayland|xorg‘“.

Maybe use:
“ps -ef | grep -i -e wayland -e xorg”
or
“ps -ef | grep X”

Check also maybe do you have any errors in ~/.xsession-errors or /var/log/Xorg.*.log?

[og00r]

Can you look for any information in nxerror.log (/usr/NX/var/log/)? There could be something related to NXWMRunning.

Also logs in /var/log/lightdm/ and /var/log/Xorg.*.log should be checked for errors.

[og00r]

When you login to system, which desktop environment is set? (settings icon is right next to password field)

There should be option gnome-xorg, which must be used. Do you have access to that machine? Can you login there (with option gnome-xorg) and then try connect with NoMachine?
Output from command from earlier post will be helpful (situation when user is already logged).

[og00r]

There should be “ps -ef | grep -i –E ‘wayland|xorg‘“.
From yours information’s, I’m expecting problem is that physical session is running on wayland.
According to this https://www.nomachine.com/fr/FR10N03221 you should disable wayland, restart whole system and try again.

[og00r]

Do you have some errors in ~/.xsession-errors?
Could you set SessionLogClean 0 in node.cfg, restart nomachine, reproduce problem, and check directory T-C-… in /usr/NX/var/log/node/ for errors?

[Author]

Posts