Large number of session log directories

[ong777]

On one particular workstation, I recently discovered had ran out of inodes in the root file system due to a massive number of /usr/NX/var/log/node session directories. In the last 2 weeks, there were over 1M files/directories created in this directory from users that don’t normally use NoMachine. How can I find out why or what is causing all these session log directories to be created? Besides turning off this debugging or enabling auto cleanup, how can I find why it’s doing this? The log files are on the “server” side.

I’m currently running the free version of NoMachine 6.9.2-1 on Ubuntu 18.04. The machine is a member of a NIS/NFS domain.

Note, I do see some error messages in nxerror.log about ipv6, probably b/c our company requires us to disable IPV6. We disable IPV via grub kernel option: ipv6.disable=1.

root@host:/usr/NX/var/log# tail -20 nxerror.log
unable to open tmp file “/usr/NX/var/tmp/nx/EA991EB1F9954B941B4A5490A7DE6EA0.authority-n”
unable to write authority file /usr/NX/var/tmp/nx/EA991EB1F9954B941B4A5490A7DE6EA0.authority-n
No protocol specified
No protocol specified
1675 59237 19:51:02 767.535 HostWmRunningHelper: WARNING! Failed to open display ‘:0′.
ip6tables v1.6.1: can’t initialize ip6tables table `filter’: Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
Could not open socket to kernel: Address family not supported by protocol
Could not open socket to kernel: Address family not supported by protocol
3191558 3191645 22:44:42 927.676 ServerNetworkInfoHandler: WARNING! Obtaining network data failed.
Usage: nxnode …
this command is intended to be used only by NX Server
or NX Workstation.
ip6tables v1.6.1: can’t initialize ip6tables table `filter’: Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
Could not open socket to kernel: Address family not supported by protocol
Could not open socket to kernel: Address family not supported by protocol
1662 2874 22:49:55 204.039 ServerNetworkInfoHandler: WARNING! Obtaining network data failed.
Error: Session with pid ‘13688’ terminated unexpectedly.
Error: Session with pid ‘130834’ terminated unexpectedly.

Thanks,

Quang

 

[Britgirl]

At a glance, it seems like a problem with access to the local xserver. Could something have changed on the system that would trigger this? Having a look in the session directory from var/log/node/ could reveal something useful.

It’s impossible for us to know why this is happening without taking a look at the logs. First of all, I would update to 7.8.2 if possible because there have been several releases since 6.9.1 and we can’t be sure that this isn’t related to something we already fixed. If the problem is still there after updating, enable debug, restart the server and then gather the logs up. Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Instructions for enabling debug are available here: https://knowledgebase.nomachine.com/DT11R00182.

[Author]

Posts