Forum Replies Created
The requested log is attached;
There was only one M- directory : M-localhost-115419-1011237CFD0B60DBDDA3CF14128E27C5 with one session file inside .
Note that I stopped yesterday the nxserver service to prevent the high CPU load; I do not know if this may have interfered with your request of seeing the M- directories contents;
For those of you interested in a solution, we worked with the support on a solution to this problem which can be tested in the vagrant testbed: https://github.com/jeremyfix/devops_samples/tree/main/nomachine
Thank you for your help;
Thank you for your answer; There is indeed an ongoing discussion with the NoMachine support team ; If we succeed to make any progress (and this is for now on my side to provide more inputs) , I will drop a message in there.
Thank you for the feedback ; This is indeed the one that I used in production
# Authorize the user to open a nomachine session
/usr/NX/bin/nxserver --userenable $ SLURM_JOB_USER
And that seems to be working.
Thank you, that indeed solved the problem for at least one user under MacOS 11.xx ;
Note however your script seem to contain some windows linebreaks “^M” , and some “\r” that made it not runnable out of the box. I’m not sure how to properly correct it, I finally ran all the lines of your script one after the other.
Thank you for your help,
I’m unable to test your command because I do not possess the computer.
But indeed, the script you sent me yesterday solved the problem. I will answer the result on the other original thread.
Thank you for your help.
Hello, I feel I have a similar issue which I posted here (https://forums.nomachine.com/topic/empty-usb-device-list ; Would you mind sending me this magical script as well please?
Thank you for your help.
Thank you for your answer but unfortunately I do not understand why that should fix the problem.
Your first suggestion will just redirect the stdout and stderr to /dev/null
For the second one you propose, it triggers two questions in my mind ; The nxserver service starts
which is indeed different from the one you propose :
etc/NX/nxserver --startup; But do you know the difference ? is
etc/NX/nxserver --startupblocking when
etc/NX/nxserver --daemonis not ?
Hi, Thank you for this feedback which worked for one user running Mac OS 10.14 (For sure that was a 10.xx not sure about the 14); For this user, as soon as sharing the device was selected in NoMachine, the security app of MacOS poped up and we were able to accept the use of the extension
But, unfortunately, that did not work for 2 or 3 users that were running a 11.x MacOS. As far as I remember, there was a 11.5.2, a 11.4, and another.
For example, for the 11.5.2 user, you see on the screenshot attached to this message that the device list is empty and nothing appears on the “Security and confidentiality” where I would have expected to see something about the nomachine extension. The user tried to uninstall and reinstall NoMachine expecting the message to appear again but unfortunately not.
Do you have another suggestion on the way to proceed ?September 24, 2020 at 08:42 in reply to: Empty list of usb device, nxusb cannot be compiled because of missing relocs_32 #29593
Oh, I’m sorry. Actually , that was a little piece that I didn’t do strictly as you mentioned in the links :
I did :
sudo make -f Makefile
and I should have done
make -f Makefile
That solved it for the 5.3.0-62-generic ; I will check if it solved the problems on the other OS and keep you informed.
Thanks for your help.August 5, 2020 at 07:29 in reply to: Restrictions to session shadowing with NoMachine Linux #28856
Thank for your answer.
There may still be a point unclear to me. As the free version allows only one user to connect remotely at a time, how many simultaneous connections are allowed by the non-free versions , say, starting from the Workstation version ?
A follow-up. Following the advice given here , on the remote server with Wayland enabled, I stopped gdm (sudo service gdm stop) and restarted nxserver (sudo /etc/NX/nxserver –restart). Then, on connection, the NoMachine client asked for creating its own framebuffer and I got the correct login screen (no more blank screen) and was able to forward the USB device.
An additional bonus is that actually, when NoMachine is creating its own framebuffer, it is able to scale with the client window size, which was not the case with my previous setting using gdm.