NetXMS Support Forum

https://www.netxms.org/documentation/adminguide/hypervisor-monitoring.html

Да, переход на 2.1 - долгий. Мы сильно поменяли структуру хранения табличных метрик, и все данные при апгрейде конвертируются в новый формат.
После апгрейда рекомендую сделать вакуум - база будет в разы меньше.

На данный момент этот артибут недоступен из nxsl

Try http://mysqltuner.com/, it usually gives you quite decent ideas about MySQL configuration (it's not a silver bullet though).

Are you using HiDPI screen by any chance?

Check that metric is provided by the agent:

nxget -I VM_IP|grep SSH

Also check agent version:

nxget VM_IP Agent.Version

Also check output of "dmesg" - most likely there will be records like "Out of memory: Kill process 29957 (netxmsd) score 366 or sacrifice child"

Yes, I'd recommend at least 2GB of memory when database is on the same server.
How many servers you have configured in the NetXSM?

Hello.

It's know issue and we are working on it.

DB lock is there to prevent multiple instances of the server from corrupting data integrity. If daemon is not running but lock is there, usually that means that  it either crashed of database was shutdown first.
In your case, netxmsd is not starting at all, or crash at some point?

There is a stale lock in the database.
Make sure that netxmsd is not running and remove it with "nxdbmgr unlock".
You can also run "nxdbmgr check" for consistency check.

Problem with slow external parameters is that server retrieve values in a single thread (per agent) and it can block data collection from the agent

Well, it behaves as expected.
If you need to handle long-running command - use ExternalParameterProvider (https://wiki.netxms.org/wiki/ExternalParametersProvider)

Please increase debug level to 5, reproduce problem and send us agent log

Check that you running Java 8