November 3, 2019 at 08:49 #24327
It seems that NoMachine will occasionally not authenticate a user. Yes, a fresh reinstall will usually fix it but I’m sure there’s a better way. Anyhow, here’s my problem. I installed NoMachine and even before the latest update it went from allowing a known user to connect to authentication failures. I looked at it on the NoMachine server and the server GUI said NoMachine wasn’t running yet there were NX processes in a “ps aux”. I stopped NoMachine, cleaned out the logs (nxd.log, nxerror.log, and nxserver.log) made the debugging changes to /usr/NX/etc/server.cfg and /usr/NX/etc/node.cfg, restarted NoMachine, and attempted to connect with the known good user. After it failed, I created a tarball of the logs and stopped NoMachine. The NoMachine product is the free version for linux on both the client (slackware) and server (archlinux-armV7). The desktop is Mate on both the client and server.
After restarting the server, the GUI says it isn’t running and the logs seem to point to permission issues.
JimNovember 5, 2019 at 09:12 #24337
Here’s the logs. I guess tarballs aren’t allowed.
JimNovember 5, 2019 at 10:25 #24342BritgirlKeymaster
Please send them to forum[at]nomachine[dot]com making sure you reference the subject of your topic. Thanks!November 6, 2019 at 16:22 #24356CatoContributor
What’s the output of ‘ls -la nxexec’ command executed in terminal in bin subdirectory of NoMachine installation directory?November 7, 2019 at 09:53 #24364
-r-xr-xr-x 1 root root 84196 Oct 25 23:17 nxexecNovember 7, 2019 at 13:23 #24380CatoContributor
For some reason permissions on your nxexec binary are incorrect. To fix the issue you need run ‘chmod u+s nxexec’ from terminal, inside NoMachine\bin directory, as root. Proper permissions look like this:
-r-sr-xr-x 1 root rootNovember 8, 2019 at 08:49 #24389
The ‘chmod’ allows me to connect to the Pi4 but now it won’t recognize the Desktop. I get the “No Desktop running do you want me to create one” message, I click “YES”, and then the “Ooops! Cannot find the default environment. Please contact your system administrator” screen. [No point contacting the administrator since it’s me. 🙂 ] I mailed the picture to the forum_at… email.
Attachments:November 8, 2019 at 16:36 #24401kroyContributor
Is this headless machine? It looks Xserver isn’t running. Changing node.cfg key to DefaultDesktopCommand “/usr/bin/mate-session” should allow you to create session.
As you had not proper permissions on the subfolders – we stronly recommend to reinstall NoMachine. Maybe you have system on external disk and it’s change permissions when you use disk on other device? Anyway we wasn’t able to reproduce that problem.November 11, 2019 at 09:08 #24409
The “Microsoft fix” (ctrl-alt-del and wait for the reboot to complete) took care of the problem. Figure!
No, it’s not a headless machine and a mate-session was running when the problem occurred. The system is on the SD card that the RPi4 boot from.
I was starting to think that this could have been an installation problem. Now I’m pretty sure that it was. Anyway, it’s working again and the simple fix is ‘chmod u+s NX/bin/nxexec’ and reboot.
This topic was marked as solved, you can't post.