Forum Replies Created
-
Posts
-
Only nxd process is affected? Are other processes running correctly?
Could you paste output of ‘ps -ef | grep nx’?
Also could you gather nxserver logs from the affected remote server?
This article contains information how to do it correctly:
https://www.nomachine.com/DT10O00163 (you can attach them here or send directly to forum[at]nomachine[dot]com).
If possible please run nxserver –restart after enabling logs, then gather them.one of them updated to Mac OS 10.15.4 a week ago
Were you able to connect to that machine after system update, was any pop show up to allow nxnode process?
The latest macOS requires some more permissions, are you able to reinstall manually NoMachine on those machines?
Or is only ssh connection available right now? You can try do it with vnc as ” VNC is working on one of them”
if you don’t have physical access to that machine.Also could you gather nxserver logs from the remote server so we can see whether the problem is with permissions on
new macOS version or if problem is somewhere else? This article contains information how to do it correctly:
https://www.nomachine.com/DT10O00163 (you can attach them here or send directly to forum[at]nomachine[dot]com).You can do it through ssh and if possible please run nxserver –restart after enabling logs.
Could you also check if nxnode process (ps -ef | grep nxnode) is running for correct user? (by comparing user id for that process with
logged user / root (if login window is active). Write the output here.How exactly it looks? Is appear any error during connection? After or before login? Is machine available on list?
Was machine reboot done after installation?
Could paste here output of nxserver –status from both machines?We also ask to enable logs on server.cfg and node.cfg, then gather them after issue reproduction.
For nxplayer logs please:
click on Settings to open Player preferences and click on the Privacy tab
select the Don’t delete log files on exit checkboxHere is article with details how to do it:
https://www.nomachine.com/DT10O00163In received logs there are only logs from client side, which is not enough to proceed with problem.
Please enable logs on server side reproduce the problem and send them if possible.
Here is article how to do this:
https://www.nomachine.com/DT10O00163At this moment all can I say, is that connection is closed after entering username to login procedure.
Please ensure that account name is correct and user is active in system.
Can you try start session without dbus? Just change DefaultDesktopCommand in node.cfg to:
DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax /usr/bin/startplasma-x11"and try again
also could you give us version of yours dbus-launch? and Manjaro version?
Any logs in /var/log or journactl (if available)?Looks like it is a problem with the detection of the correct desktop owner on your machine, as there is no current workaround for such issue, we could prepare and send you patched package. Are you interested in receiving and testing it?
To disable Wayland, restart of the machine is suggested.
But can you paste output of
/etc/NX/nxserver –version
to ensure which version are you using?Also is it virtual session for that affected user? If yes can you try disabling automatic screen lock in operating system config?
After this, creation of new virtual session will be requested.Logs don’t include the full problem (looks like could be enabled little to late), could you check next time on login window if:
– nxserver –daemon is running (for example withps -ef | grep nx)
– then gather his pid and check if it is listening on localhost (commandsudo lsof -p <pid of nxserver --daemon> | grep -a LISTEN)Also new set of logs with these informations would be needed, at the moment it looks like daemon is not running or is not accepting any connections.
Few questions:
– Is that login loop on ubuntu login window or do you mean login loop in nxplayer?
– What version of NoMachine are you using?
– Maybe session (or login window) is running on Wayland? (currently Wayland is not supported on VM)
– Is there any information that login failed?
– Is he trying to connect his own session or someone else’s session?Just looking on the forum seems I have to disable Wayland on the Ubuntu VM as Display Server. Is it correct?
Yes, NoMachine does not support Wayland on virtual machines. You can disable it:
E.g. in case of GNOME desktop, add the following key to /etc/gdm/custom.conf:
WaylandEnable=falseand restart gdm:
systemctl restart gdmRelated to the Display Settings the maximum resolution available is the resolution of the VM I have to connect to, or there are some limit?
Yes, it is maximum.
What version of macOS are you using?
Was it installed through command line? If not and if mac os is not “Catalina” then we will need some logs.
Article on how to collect logs:https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)
Please enable them and reproduce issue (restart whole os that it will be on login window, try to connect, then log in and connect correctly again.
Gather logs after that.
After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.
Could you also show ouput of # /etc/NX/nxserver –status when it is on login window?
Could you please gather some logs for us to check this issue?
Article on how to collect logs:https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)
Please enable them, restart the nxservice:
‘/etc/NX/nxserver –restart’
And try reproduce problem.
Gather logs then.
After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.But I must ask why did you stop gdm? Is it on purpose? Because now it will try to create virtual session.
Is it happening before or after login?
To understand better what is happening, we need to see the server-side logs from the destination Windows host.
Please follow the instructions here: https://www.nomachine.com/AR10K00697 and then send them to forum[at]nomachine[dot]com.
Enable logs, restart NoMachine, reproduce problem, gather logs and send them.
Also output from nxserver –status could be useful.About that warnings:
‘NX> 162 WARNING: Cannot find X servers running on this machine.
NX> 162 WARNING: A new virtual display will be created on demand.’
It happens because NoMachine cannot find correct session with new plasma in version 5.17.
There is Trouble Report for it (separate from TR10Q09440):https://www.nomachine.com/TR10Q09441
As there is no workaround at this moment we could prepare packages with fix for you, but you should confirm what packages you are using (nxserver –version) on what architecture (x86 or x64).
So I assume virtual sessions are working correctly right now?
About warning during restart and physical session.
‘NX> 162 WARNING: Cannot find X servers running on this machine.
NX> 162 WARNING: A new virtual display will be created on demand.’
It happens, because NoMachine can not find correct session with new plasma in version 5.17.
There is a Trouble Report for it:https://www.nomachine.com/TR10Q09441
As there is not workaround at this moment we could prepare package with fix for you, but we need to know what packages you are using (nxserver –version) on what architecture (x86 or x64) for Arch Linux?