- This topic has 9 replies, 3 voices, and was last updated 6 years, 12 months ago by
.
-
Posts
-
Hello,
I installed 5.2.11 on several machines, and only two of the machines are exhibiting this problem. They are both multi-monitor machines (3 each, to be exact). One is running ArchLinux (with an NVIDIA GeForce GTX 980) and the other is running Windows 10 (with an NVIDIA GeForce GTX 1080). Both behave exactly the same.
- No matter which client connects to these 2 machines, I get blank screens.
- Additionally, when I connect to the Linux machine, it sometimes goes green and then blank.
- I have tried fiddling with player and connection options on both ends and none seem to have any effect. I have rebooted, reinstalled, and uninstalled/deleted the .nx directory/reinstalled.
- Sometimes the multi-monitor button is included with the screen settings icons, and sometimes it isn’t. I currently have it set to “ALL,” but I do not seem to be able to configure it for single-monitor mode anymore.
- Sometimes, the client reports that the server has a single monitor with resolution 11520×2160. Sometimes it (correctly) reports 3 monitors with 3840×2160 each.
- It usually says “codec: Unknown” but on rare occasions I can catch it as VP8 or H264.
- I get balloons that show me connecting/disconnecting to the server, but I can tell that the server quite obviously crashes and restarts after the initial connection because the tasktray icon keeps disappearing and reappearing.
- All of the servers running on the other machines work perfectly, and they are all single-monitor machines.
I’ve attached a tarball containing my server logs from the Linux machine. Would appreciate it greatly if you could help me resolve this issue.
We are aware of an issue in multi-monitor set-ups: https://www.nomachine.com/TR12M06304
This seems to be what you are experiencing (sign up to Notify me in order to receive an email from us when we’ve released the update including the fix). You will have to submit logs to forum[at]nomachine[dot]com, they were refused by our attachment tool. The restarting of the nxserver service is most likely a symptom of the TR, but we can check them to make sure.
Okay, I’m attempting to attach them individually before e-mailing them.
It’s probably worth pointing out that I tried forcing the server to use VP8, H264, and MJPEG and it crashes regardless of the codec forced. Also if I grep the logs for x264 I do not see the message that the TR mentions.
Looking in the logs we found this:
2017-04-10 03:53:24 998.815 15473 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user acc –priority realtime –mode 0 –pid 12’ with pid ‘16992/16992’ finished with exit code 11 after 9,774 seconds.
which is caused by the TR we already mentioned. Sign up to the notify me tool on the TR’s web page to know when we’ve released a fix. Thanks!
Roger that, and I’ve already subscribed.
It’s nearly a year and a half old and “due to be solved in 5.2”. I also wouldn’t call this a minor issue; 4K monitors are becoming increasingly more common.
I don’t think the enterprise version of NoMachine is a good fit for me, but I am willing to stick it out with the free version. I would personally put a monetary bounty on this issue because it’s that important to me. I am so very tired of VNC. I need this functionality yesterday, and I am sure that I am not alone.
You’re perfectly right in saying that this is not a minor issue! We are already working on it, but unfortunately it can’t be a quick fix. Video encoders don’t support such high resolutions themselves. The solution is to encode monitors in separate video streams, but this is quite a big change and it will take some time and many tests.
Just to clarify, the reason that I said that I wouldn’t call it a minor issue is because the TR (https://www.nomachine.com/TR12M06304) has it rated at “Severity: Minor”. And with it being 16 months and you still haven’t been able to put together a quick fix, you may want to consider elevating it.
I don’t think elevating the severity will change the fact that the solution is to encode monitors in separate video streams due to the video encoders not supporting such high resolutions themselves. As Fra81 mentioned it’s a rather big task and one that is underway. Believe me, if there had been a quick fix, we would have already pointed it out in the TR 😉
This topic was marked as solved, you can't post.