NoMachine Support

Your questions answered

Knowledge Base

Searching in: Articles & FAQs
Filter the search results
Applies to:
Last update:
Searching in: Articles & FAQs
ID: AR12I00100
Applies to: NX Software
Added on: 2011-12-13
Last update: 2017-11-20
How to gather debug logs for NX 3.5.0

This article applies to NX version 3.5.0. 

To gather debug logs for most recent versions, please refer to

NoMachine v. 6 - https://www.nomachine.com/DT10O00163

NoMachine v. 5 - https://www.nomachine.com/DT07M00098

NoMachine v. 4 - https://www.nomachine.com/DT04M00076



Instructions to retrieve the relevant information from your NX 3.5.0 installation on (a) server side and (b) client side

 

(a) The Server Side

a.1 Login as user 'root' to the NX Server host.

a.2 Ensure that the session directory in the user' s home on the NX node host is not deleted at the end of the session.
To do that edit the node configuration file (/usr/NX/etc/node.cfg) and uncomment the following line:

SessionLogClean = 0

a.3  Increase the log level of NX node by modifying the SessionLogLevel key in the node.cfg file to have:

SessionLogLevel = "7"

a.4 Increase the log level of NX server by editing the server configuration file /usr/NX/etc/server.cfg and modifying the SessionLogLevel key to have:

SessionLogLevel = "7"

a.5 Reprouce the problem.

a.6 When the problem has been reproduced, locate the session directory on the server host. You can find it under the .nx directory. The .nx directory is created by default in the user's home, or in the directory specified by the UserNXDirectoryPath node configuration key, when enabled.

Session directories are named according to the following standard:

~/.nx/C-(Server Name)-(Display ID)-(Session ID)

When a session is terminated correctly, the session directory is renamed as:

~/.nx/T-C-(Server Name)-(Display ID)-(Session ID)

When a session is terminated because of an error, the session directory is renamed as:

~/.nx/F-C-(Server Name)-(Display ID)-(Session ID)

In the session directory there are three log files that can be relevant for investigation.

The file 'session' contains the stderr stream of NX Proxy and NX Agents. It usually contains the most relevant information.

The file 'errors' is an additional logging facility useful for tracing the internal operation of NX Proxy.

The file 'clients' contains the stderr of the X applications run by the user if the ClientLog key is not disabled in the NX node configuration file.

When submitting set of logs upon a request from our Support Team, be sure to include a 'tar' archive of the whole session directory:

tar -cvpf failed.session.tar $HOME/.nx/(session directory)

For example, a typical failed session might look like the following:
#> F-C-tahoe.nomachine.com-1050-0D03F09DF3A3B0756511509305D47E7C

Now extract from the syslog file the lines generated by NX Server and NX node:

#> grep NX /var/log/messages > syslog.extract

 

In case of multi-node support:

Login to the NX Node host and execute the operations described above to retrieve both the session log files and the lines generated by NX Node in the syslog file:

#> tar -cvpf failed.session.tar $HOME/.nx/(session directory)
#> grep NX /var/log/messages > node-syslog.extract

- Login to the NX Server host to extract from the syslog file the lines generated by NX Server:

#> grep NX /var/log/messages > server-syslog.extract

 

Important note for Solaris users:

Depending on the system configuration it could be required to modify the settings of the syslog daemon. Please make sure that a line similar to the following is present in the configuration file:

*.err;user.debug;kern.debug;daemon.notice;mail.crit /var/adm/messages

Then restart the daemon for the changes you have made to take effect.

Add the new file to the archive and compress it:
#> tar -rvpf failed.session.tar syslog.extract

And:
#> gzip failed.session.tar

Be sure you include the generated archive in the support request in the form of an e-mail attachment.

 

(b) The Client Side

On the client side make a compressed archive of the whole '.nx' user's directory and send it to the Support Team.

on Linux and Solaris:

tar -cvp --exclude 'cache*' --exclude 'images' -f - $HOME/.nx | gzip -c >nxdir.tar.gz

on Windows you can use the WinZip utility to generate a zip file of the directory:

%userprofile%.nx [Windows 2000/2003/XP/Vista]

excluding the 'cache' and 'images' subdirectories.