![]() Execute, on Linux and macOS: $ sudo /etc/NX/nxserver -logrotate When the problem is easily reproducible or if the Support Team requested that, you may clean the server/node logs before starting the procedure to collect them. These are the general steps to collect and send logs:ġ) On the server/node host set debug log level manually.ģ) On the server/node host create the compressed archives of logs.Ĥ) If requested, collect client side logs on the user's device.ĥ) Send the log archives to NoMachine Support Team by e-mail or ask Support to provide a space for uploading logs if size is too big for an e-mail attachment. In a similar way, when the problem may affect the Enterprise Terminal Server or Enterprise Terminal Server Cluster and/or any of the Enterprise Terminal Server Nodes, follow instructions for the appropriate Operating System and execute them on the affected host(s). Follow instructions for the appropriate Operating System and execute them on the affected host(s). Server side logs have to be collected on the NoMachine host where the problem occurs:įollow instructions for the appropriate Operating System and execute them on the NoMachine Server host.ĭepending on the problem, it may affect the main Cloud Server or any of the servers on the nodes. Troubleshooting COLLECT AND SEND SERVER SIDE LOGS 1. How to Debug the NoMachine Monitor on Linuxħ. How to Debug a CPU Consuming Process on LinuxĦ. How to Locate the Connection Settings File (.nxs) OTHERSĥ. ![]() How to Collect Client Logs from Users' DevicesĢ.4. Enabling Debug for the 'nxserver -daemon' Process (already running) COLLECT AND SEND CLIENT SIDE LOGSĢ. ![]() Enterprise Terminal Server Node (Linux)ġ.5. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |