Britgirl

[Britgirl]

Hi, thanks for the submitting the logs. The agent logs were missing unfortunately (which we need), but in the server logs we can see the following errors:

7901 259 2024-03-23 04:06:03 608.263 Socket: ERROR! Can’t execute the sysctl request.
7901 259 2024-03-23 04:06:03 620.942 Socket: ERROR! Error is 12 ‘Cannot allocate memory’.

What we don’t know if this is due to system memory being exhausted or whether you have a per-user limit, but it’s something you need to check. Then, please gather the logs (--enable all as per the instructions) making sure not to remove the agent logs.

[Britgirl]

Take a look at the article here “The password scrambling algorithm in NX Client”, https://kb.nomachine.com/AR01C00125

[Britgirl]

If it’s a headless Linux host you are connecting to, please follow the tips in the article here https://kb.nomachine.com/AR03P00973, specifically 1) Use a X virtual framebuffer.

Better would be to disable the display manager permanently, then the DM won’t start after reboot. This is the command
to disable and stop the DM:

sudo systemctl disable --now [enter here display manager]
sudo /etc/NX/nxserver --restart (just once, after reboot all will be fine)

Now when you connect, you should be able to start your session correctly.

If that doesn’t help, please submit the following information:

– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– Desktop version (GNOME. KDE, whatever) you are connecting to.

When you connect, are you seeing a black screen with a moving cursor, or are you seeing the desktop’s content which is frozen (except for the cursor). Is there a specific application running?

[Britgirl]

At the moment, in its current version, NoMachine considers the monitors as one big screen.  What you need is for NoMachine to capture and encode each monitor as a separate video stream. Such a feature is planned and work has started, although we are unable to provide an ETA.

[Britgirl]

The logs confirm the problems we already know about. About the version, I was referring to 535 official NVIDIA drivers. Thanks for the pointing out that Ubuntu’s own 535 doesn’t fix the problem.

[Britgirl]

It’s likely you have the same problem on all the machines from which you are pulling the monitor out of.  And it’s not related to NoMachine, but the system. Rather than just pull the HDMI out, disable the Xserver correctly first and then detach the monitor. It’s option 3 in the article you mentioned (for headless Linux), the section “Use a X virtual framebuffer” which explains how to stop the display manager.

First check what display manager you have in a terminal: ps aux|grep dm

Then stop it. When you stop the display manager, you are stopping it forcibly until the machine gets rebooted. It’s not permanent. It will start up again at next reboot. An important point here to note is that when you stop any DM, NoMachine cannot know that someone stopped it because the system does not send such information to NoMachine. That’s why NoMachine (the nxserver) must be restarted.

Better would be to disable the display manager permanently, then the DM won’t start after reboot. This is the command
to disable and stop the DM:

sudo systemctl disable --now [enter here display manager]
sudo /etc/NX/nxserver --restart (just once, after reboot all will be fine)

Now when you connect, you should be able to start your session correctly.

For Windows, as explained here: https://kb.nomachine.com/AR05S01124 NoMachine is made to work out-of-the-box, but a black screen may occur in some cases. So in your case closing the lid effectively means NoMachine can’t find any GPU running there and you’re seeing a black screen. Either you keep the lid open or you attach a dongle.

[Britgirl]

We do considerable testing on headless mini PCs 😉

I suggest you look at the article dedicated to headless Linux https://kb.nomachine.com/AR03P00973

[Britgirl]

In our tests everything works as expected. What we need from you:

1) server side logs whilst producing the

I think logs from server side would be needed.  Reproduce the problem and when you do reproduce,  don’t disconnect. Just tar the .nx folder on the Lubuntu server side and send to us.  Plus the player logs from that session on the connecting client side. How to do that is explained in the following document.

You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

Then, the output of this command:

ps -ef |grep -E "X|dm|lxqt"

Thanks.

[Britgirl]

Something you can try on the fly: check in /usr/lib/x86_64-linux-gnu if you have libmfxhw64.so – if not please create a symbolic link to libmfxhw64.so.1 with:

 

cd /usr/lib/x86_64-linux-gnu/
sudo ln -s libmfxhw64.so.1 libmfxhw64.so

 

restart NoMachine and try again to see whether NoMachine uses Intel’s mfx hardware encoding.

[Britgirl]

Support for VA-API is planned and we are currently working on adding support for VPL

[Britgirl]

Hi, welcome to our Forums!

What NoMachine counts is the incoming connections on the host (or “server”), not the outgoing connections on the clients. So you are correct in your assumption 🙂 You can start as many connections as you want from any of your machines, but the server computer you want to connect to must have a NoMachine product that lets multiple connections in, if 1 connection is not enough.

So, you say that you want to connect to the Mac from both Windows PCs at the same time. On the Mac you need Enterprise Desktop. On your Windows PCs, you can stick with NoMachine (free version) or simply opt for Enterprise Client if you don’t want the NoMachine server component installed. That’s entirely up to you. To install Enterprise Desktop, you need to uninstall the free NoMachine package.

If I nomachine into a system, can I launch virtual displays to simulate a “multi-monitor” setup on that machine I’m remoting into? Would this let me have two NoMachine windows on PC A into the Mac, one NoMachine window for each monitor on the mac in view at the same time on PC A? because it sounds like that’s possible with the enterprise license features but let me know if I’ve misunderstood, thank you!

Creating “virtual displays”, what we call virtual desktops, is a feature of the NoMachine for Linux products.  On Mac and Windows you get access to the physical display running on the system, it’s not possible to create virtual displays.

You hint at multi-monitors. There can be multi-monitors on the server side so that when you connect to the Mac in the current NoMachine version, you can switch between the monitors (see more about this here: https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session). But you will have one NoMachine window. However, if I understand what you would like to achieve, you might be interested in about a planned feature that will let you display each remote monitor on the server in a separate window on the client side. So you will be able to have one NoMachine window for each monitor attached to the server.

[Britgirl]

Is there no way to get hardware encoding working with 2560×1440 dual screen setup?

It’s an nvidia limitation, I’m afraid. You can either disable one the monitors or use the option you already tried which is to resize both of them to 1920.

[Britgirl]

Hardware encoding is not enabled because NVENC, the Nvidia hardware encoder, doesn’t support resolutions over 4K for H.264 hardware encoding. In your logs we can see the following “Info: Remote desktop resized to 5120×1440”. So that is the reason for hardware encoding not being possible.

As for hardware decoding, the resolution limit should be larger but there are no errors in the logs about decoding. Can you check if it’s disabled in the Display settings? Open the session menu (Ctrl-Alt-0) -> Display -> Settings and tell us what you see there (or submit a screenshot). Does hardware decoding work if you resize the remote desktop to a lower resolution?

[Britgirl]

Are these the logs taken from Ubuntu machine you are connecting to (the remote server)?

[Britgirl]

This is dealt with in the following topic: https://forum.nomachine.com/topic/no-gpu-hardware-encoding.

Logs should be sent to forum[at]nomachine[dot]com. That way we can verify if the drivers are the cause.

[Author]

Posts