NetXMS Support Forum

Network service is using portcheck subagent. This subagent provides a number or parameters that we can directly request for debugging purposes (https://www.netxms.org/documentation/adminguide/service-monitoring.html#portcheck-configuration).

So you can try on the server:
nxget <agent_ip_address> 'ServiceCheck.HTTP(www.google.com,80,/)'
The possible responses are:
0 Success, connection to target was established and expected response was received.
1 Invalid arguments were passed.
2 Cannot connect to target.
3 Invalid / Unexpected response from target

For response = 3 Portcheck can save HTTP server reply in a file that can be inspected to understand if the regex is wrong. For this to happen the following should be specified in agent config:
[portcheck]
FailedDirectory=/tmp/

As of v. 3.2. there's a bug on that matter. The thing is that when a node is discovered, an appropriate subned in created in "Entire network", having netmask of first found node. So it first found node had incorrect configuration (or if that node nad no netxms agent or snmp - in this case we can't get subnet from node and use /24) then subnet is created incorrectly (and this is not fixed due to the mentioned bug).
It's not possible to edit netmask of a subnet, the way to fix this situation is:
- check if configuration of nodes is correct
- make sure your nodes are present in a container in "Infrastructure services". Otherwise nodes will get deleted on the next step along with DCI history.
- delete the subned from Entire Network
- it should recreate again after some time with correct mask

Below are some thoughts and information about 3 real NetXMS installations that could give insight to some of your questions. We don't have information on number of pollers, but I think that "medium" and "larger" systems are using proxy functionality to poll a lot of data.

----

It's really hard to get an exact estimate of resources needed, since they depend on what exactly your NetXMS installation does. E.g. running a lot NXSL scripts would require more CPUs, etc.
A typical recommendation to start with would be a system with 4 CPU Cores and 8GB of RAM. SSD storage for the database would be preferred.
The amount of space for the database depends on how often you collect the DCIs and for how long you store them (that is polling interval and retention time).
On average a rough guess would be that every datapoint requires about 50-100 bytes of disk space, it depends of the data type and your database vacuuming settings.

Here are some data (a bit rounded) for three real NetXMS installations.
The number of nodes does not play much role, way more important is the number of collected DCIs, as collecting and saving them actually takes resources.
Only regularly collected DCIs are present in the data (no scheduled DCIs, no syslog, traps, etc), but they usually make up most of the data.
The "Medium" system has the database on a separate machine, while the other two have it on the same machine as NetXMS server.

All systems are using SSD storage and Postgres database without Timescale (but admins are considering to move to Timescale).

Smaller system
Objects:                          20500
Monitored nodes:                  2200
Collectible DCIs:                 34000
Collected datapoints per second:  370
Stored datapoints, millions:      9000
RAM:                              24
CPU cores:                        8
DB size:                          200

  Medium system
Objects:                          56000
Monitored nodes:                  2700
Collectible DCIs:                 186000
Collected datapoints per second:  980
Stored datapoints, millions:      15000
NetXMS server RAM:                6
NetXMS server CPU cores:          4
DB server RAM:                    68
DB server CPU cores:              6
DB size:                          1500

  Larger system
Objects                           41500
Monitored nodes:                  5400
Collectible DCIs:                 372000
Collected datapoints per second:  2290
Stored datapoints, millions:      44000
RAM:                              160
CPU cores:                        20
DB size:                          1500

In that script you need to check if any of these values is null. You can add a line prior to return... line:
if ((Avail == null) or (Buffer == null) or (Cached == null) or (Total == null)) abort;

abort will cancel execution of the script, DCI will not get a value at this point of time.

А что  HP 2055 возвращает по запросу .1.3.6.1.2.1.4.20.1.1 ?

Еще можно включить 6 уровень дебага для тега ndd.common
nxadm -c "debug ndd.common 6"
там будет информация о ходе опроса.

Я бы попробовал сделать Poll -> Configuration (full), если не поможет, то просто удалить эту ноду и создать заново (или подождать, нода сервера должна пересоздасться сама)

Test from template is actually not yet implemented, that's why the error. Apart from that your DCI should work, whether defined directly on a node, or in a template.

This message means that nxmc is older then the server.
What distribution did you use before? Was it for Windows?
Currently you can just download nxmc separately from https://www.netxms.org/download/

Тут поможет дебаг на 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