NetXMS Support Forum

Тут поможет дебаг на 9 уровне. В принципе он нужен только по тегу db.query, но сейчас драйвер базы данных сделан так, что он включает нужно логирование только если глобальный дебаг при старте равен 9.
Можно сделать так - указать DebugLevel = 9 в конфиге сервера и сразу после запуска выполнить
nxadm -c "debug 0"
nxadm -c "debug db.query 9"

В логе перед строчкой SQL query failed должны будут быть строки с расшифровкой полей SQL запроса, по ним можно будет определить с какой нодой это связано.

rpm пакеты есть в планах, но точный срок назвать сложно.

Both Postgres and TimescaleDB are in one driver - Postgres. When performing nxdbmgr init it asks what type of database to use.

SSH connections are performed from netxms agent. It is either a proxy, or agent on netxms server. These agents need to have ssh subagent loaded (SubAgent=ssh.nsm in config file).

NetXMS takes CPU load information from /proc/stat. We just read this file once per second, calculate deltas and divide the deltas by sum of them.
Please run below command on a container that got into that state and share the output:

n=1; while [ $n -le 60 ]; do cat /proc/stat | grep cpu0; sleep 1; n=$((n+1)); done

Then restart the container and get these stats again so we could have some data for comparison.

Looks interesting. Does it happens for all LXC containers on Proxmox or only for some of them? What is Proxmox version and what are the systems that are insde the containers?

Do you have particular reasons to compile the agent? There are packages for Ubuntu: https://www.netxms.org/documentation/adminguide/installation.html#installing-on-debian-or-ubuntu

There's a field called Format string that accepts java8 format strings. And there's a custom thing - if there's * character after %, multiplier operation is done first and then format is applied.
So:
%*.2f will be the value with multiplier, having 2 signs after decimal

And the same input value can be even used twice:
%*1$.2f (%1$d b)

What kind of interface table do you mean? Is it a metric of netxms agent or from some SNMP device, or your custom external table? Can you show how data in that table look like?
What result do you want to get?

Most probably another copy of netxmsd is running. You can check what process has acclaimed a port with
sudo netstat -lptun
You may need to install it.
sudo apt install nettools

These are ports 4701, 4703 and 4747.

Developers are planning to rewrite the part of code that is responsible for that bug. So it makes no sense to debug the current code as it is, let's wait for a new version.

Ah, right, you have server on Windows. For Win it too complicated to set up the compiling environment. Let's get back to this next week, we will try to make a test build that should be able to get some more debug information.

2.2.17 is a fairly old version that we do not support any more. It's recommended to upgrade to 3.1.

It's a rare bug that is hard to replicate. Would it be possible that you compile netxms server from sources? If yes, we could prepare a patch that could do deeper debugging in this situation.

In configuration -> Server configuration there is parameter AgentCommandTimeout that defines, how long server waits for queries to agent. By default it's 4000 ms. It's good to keep this low, otherwise, if there'll be a lot of parameters, that take to long to reply, server poller processes will be massively occupied with waiting and server will have problems with getting all the data it should.

From agent side there is param in config file ExecTimeout that defines how long agent waits for an extrenal process (2000 ms by default).

It's better to keep the above settings as the are, since there's a special approach for running long queries - ExternalParametersProvider.
(https://www.netxms.org/documentation/adminguide/agent-management.html#externalparametersprovider)

It runs long queries in the background, caches the result and passes it to the server when server requests corresponding metric.
There is parameter in agent configuration file that defines maximum timeout for command - ExternalParameterProviderTimeout (in seconds). If a command runs longer, it will be terminated.