Forum Replies Created
-
Posts
-
Thanks for those. It would be useful to also see the submit server-side logs to complete the investigation? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. You can upload them here or send them directly to forum[at]nomachine[dot]com.
It seems a system update overwrote some NoMachine system scripts.
You can try running this command on the server from a terminal
sudo /usr/NX/bin/nxserver --eglcapture yes.OK, if the freezing or strange log out happens again, it would be useful to see the logs from the server. 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.
So the logs are not enabled. Just to clarify, the security section of the Player has an option to enable/disable logs using the checkbox. The Server logs are gathered this way, apologies for that.
https://kb.nomachine.com/DT07S00236#2.4
https://kb.nomachine.com/DT07S00236#3.1So all those entries you are noticing are being triggered by some other event. ~240GB of disk space and folders occuping ~30GB should not be happening. As I said, please submit some samples if it starts happening again.
Hi, the logs were not complete unfortunately. We need the .nx directory from the gdm user’s home dir (look for ‘/var/lib/gdm3/.nx’). Reproducing the problem should not be required.
Hi, try disabling hardware decoding in the player. You can do that by setting the appropriate key in the player.cfg file. Instructions are available here:
https://kb.nomachine.com/AR07U01202
You need to set the key to <option key=”Enable hardware accelerated decoding” value=”disabled” /> to completely disable, making sure to quit the player first (from the tray) before then starting a new session.
Does the session still disconnect?
Please send us the client-side logs (the device you are connecting from). You can gather them using the instructions in the following document https://kb.nomachine.com/DT07S00243, specifically paragraph “Fourth Step: Collect Client Side Logs“.
Thanks for the player logs.
A crash is observed:
18874 18874 2024-09-03 09:26:14 034,814 ClientSignal: WARNING! Child process ‘18979’ died because of signal ’11’, ‘SIGSEGV’.
It would be useful to see a backtrace from the core file/crash report. Please see the instructions here:
https://kb.nomachine.com/AR09L00810Check that you have not configured NoMachine to keep logs in both the Player and Server settings to start off with (Settings > Player > Security and Settings > Server > Security. Generally, you enable logs when you need to reproduce a problem and then analyse the logs, but you should disable them afterwards.
A large number of M-* and R* could be an indication of something crashing and it would be a good idea to send us an example of what you have, so we can check them. You’ve deleted them now, but if they continue to grow, please submit some examples.
Hi, please follow the steps in the article:
Connecting to virtual desktop sessions in NoMachine
https://kb.nomachine.com/AR07K00681You need to set the ConnectPolicy key in /usr/NX/etc/server.cfg. Point iv or vi depending on your specific needs should be your case 🙂
We received client side logs, but we need to see the server side logs. 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. Thanks!
We received server side logs and the client side nxtrace log but no NoMachine player logs from the Windows machine. Please submit those as well. See point Fourth Step: Collect Client Side Logs (if requested) of the document in my previous reply. Thanks.
Do you mean the TR ‘s workaround does not help, or do you mean the keyboard is now working correctly?
You appear to have a double NAT there. So NoMachine has to go through two routers. You will need to forward the first port from external IP on Starlink to TPLink, and than from TPLink to the computer (https://kb.nomachine.com/AR04S01122). If you’re not in charge of both of these routers, you would need to contact who is in order to open the necessary ports to get access to your network from outside.
The upcoming NoMachine Network feature of version 9 will solve all these networking problems. There will be no need to know your computer’s IP address, or other network details. See this page for an introduction into what’s coming up: https://www.nomachine.com/network
It’s strange that you can connect from other clients without issues. As you said the problem appears to be on the Manjaro device you are connecting from, so for that we need the Player logs which were missing. See “Fourth Step: Collect Client Side Logs” in the link I gave previously.
Hi, there is a Trouble Report open about a similar issue. Could you check whether the steps to reproduce reflect your case and whether the workarounds also apply?