NetXMS Support Forum

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.

Какая версия сервера используется? Откуда ставилась - из пакетов, или компилировалась?
Какая база данных?

You can change logging level for particular debug tags, e.g.:
nxadm -c "debug obj.sync 6"
Then you can check current status of logging
nxadm -c "debug"
And reset logging to default level for particular tag:
nxadm -c "debug obj.sync -1"

"SQL query failed" are errors, so should be visible on debug level 0, so we assume there is no such errors on your system.

obj.sync messages are delayed, should happen within about a minute after deletion on the front-end. Try setting debug level 6 to obj.sync and see what's going to be in the log.

1) please show full output of nxadm -c 'sh st'
2) please show full output of nxadm -c 'sh q'
3) please show graph of NetXMS server: physical memory used by process for the duration for few days - from server start till out of memory event.

Try checking server log either for SQL query error messages or messages with tag [obj.sync           ] saying something like "Unable to delete...". If you see nothing, try increasing debug level to 6.

Agent reads it's configuration file only on start-up, so you have to restart the agent so it will be able to ran this custom parameter.
Now, the server reads available parameters from the agent on configuration poll only. So once you've restarted the agent, you can do a manual configuration poll and then the parameter should appear in the list.

ssh functionality is implemented only in ssh.nsm subagent, server does not do ssh communications. So, if you have zoning, you need to load ssh.nsm on zone proxies. If there's no zoning, agent running on netxms server will be used for ssh commands, so you need to enable ssh.nsm there.

Try to use -P instead of -p.
(one day nxpush will give correct error message in that case )