![]() ![]() If the problem affects web sessions, set also:Įdit /usr/NX/etc/node.cfg, remove the # and set the following: Library/Application Support/NoMachine/var/log/logrotate on Mac.Įdit /usr/NX/etc/server.cfg, remove the # from the key name (uncomment) and set the following: ![]() %PROGRAMDATA%\NoMachine\var\log\logrotate on Windows Rotated files are saved in the NoMachine var/log/logrotate directory: When the problem is easily reproducible or if the Support Team requested that, you may clean the logs before starting the procedure above to collect them. Send the 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. Create the compressed archives of logs. These are the general steps to collect and send logs: 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).ĭepending on the problem, it may affect the Enterprise Terminal Server or any of the Terminal Server Nodes. Server side logs have to be collected on the NoMachine server host where the problem occurs: Iį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 federated servers. 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)ĥ. How to Collect Client Logs from Users' DevicesĢ.4. Enabling Debug for the 'nxserver -daemon' Process (already running)Ģ. NoMachine Terminal Server Node (Linux)ġ.5. ![]()
0 Comments
Leave a Reply. |