fisherman

[fisherman]

Hi,
I am glad that solution helped you.

[fisherman]

Hi,

If I understood well your request, it is possible for the Administrator to disable unneeded session types in NoMachine terminal server. Please check following article AR07P00989 – How to disable specific session types (e.g. custom sessions) on Linux.

[fisherman]

Crash is dumped by the OS, and depending on your configuration core file can be located in your home folder or /var/crash/ folder.

I noticed that uploaded logs exceeded upload size, so please can you email them at forum[at]nomachine[dot]com.

[fisherman]

From the logs we noticed that there is a problem that one process is hanging. With logs provided, the problem is hard to debug, to handle it we would require more data.

Please set in the /usr/NX/etc/node.cfg:
SessionLogClean 0

Also it seems, that master agent hangs in this case, so please add this line at the bottom of the /usr/NX/etc/node.cfg:
dumpCoreOnHang 1 or use echo "dumpCoreOnHang 1" >> /usr/NX/etc/node.cfg

This will cause the server to kill node with signal 11 instead of 9, so please make sure the system can handle core dumps. After this please restart the nomachine server:
/etc/NX/nxserver –restart

If the Agent hangs, the system produce core report for nxnode process. We would require the backtrace of all threads. The instruction is available here:
AR09L00810 – Using GDB to debug a core file on Linux

Make sure that debug, is enabled as per instruction Reproduce the problem and send the server and node logs as mentioned in the previous post as well as the debug traces from the core dump.

[fisherman]

You can check enabled applications, ports in Advance firewall settings “Inbound Rules”.

[fisherman]

I can only think about one possible case that you have enabled “Block all incoming connections, including those in the list of allowed apps” see screenshot.

If that is disabled please try enabling NoMachine port 4000.

Attachments:

1. 

   public_firewall.png
   

[fisherman]

Collect server side logs automatically

More info is written under paragraph “Fourth Step: Collect Client Side Logs (if requested)”

On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx

[fisherman]

Hi,
Based on the logs you send us, nxserver process is still connected and we dont see problem reproduced.
Did you reproduced problem with connection reset by peer ?

If yes, to make sure we have correct logs, please reproduce issue possibly few times again and send us player and server logs.

[fisherman]

I am not sure exactly by your post what is the problem. I did tried installation on Elementary OS 6 and did not have any issues and installation completed without errors and NoMachine works without problems.

Can it be the reason that you have some special configuration that somehow alters NoMachine installation.

Please can you show us what error you had and send us the NoMachine logs that are stored in /usr/NX/var/log?

[fisherman]

Please update your server version to latest 7.6.2.

If you still reproduce the problem, please enable debug by executing sudo /etc/NX/nxserver --debug --enable all.
Then reproduce problem, and collect logs sudo /etc/NX/nxserver --debug --collect

After collecting logs you could disable logs again by running sudo /etc/NX/nxserver --debug --disable all

[fisherman]

From the log file you sent, I see only that NoMachine nxd cannot bind to the network interface. Can you check if permissions for nxd/nomachine to bind port 4000 on the required network interfaces are correctly set?

Additionally, if after setting proper permission, you still experience problem please check if LAN connection works, and send us all NoMachine logs. You can collect them by executing sudo /etc/NX/nxserver --debug --collect

[fisherman]

Please change DefaultDesktopCommand in /usr/NX/etc/noode.cfg
with
DefaultDesktopCommand “env GNOME_SHELL_SESSION_MODE=zorin XDG_CURRENT_DESKTOP=zorin:GNOME gnome-session –session=zorin”

[fisherman]

I am glad that is helped.

[fisherman]

Please can you verify if nomachine client is installed correctly, you can do easy that by executing dpkg --list "nomachine*".

If NoMachine is installed, but failed to start, then please check your client host architecture uname -m.
If your architecture is x86_64, please use NoMachine client package Nomachine client amd64.

[fisherman]

Hello,

NoMachine on Mac OS uses connection to the physical display. “Unknown Display” and only resolution choice of 1080p could be limitation of connected monitor or limitation of headless Mac.

If you are using headless mac, possibly attaching hdmi dummy adapter would help.

Or you could try to hold Option ⌥when selecting Scaled resolution (see screenshot).

Attachments:

1. 

   scaled.png
   

[Author]

Posts