NetXMS Support Forum

This was addressed in Telegram, let's copy this info here:

execute manually the following statements:
ALTER TABLE alarms ADD rule_description varchar(255);
(may file if alter was already done by nxdbmgr and didn't rolled back - that's ok then

UPDATE metadata SET var_value='17' WHERE var_name='SchemaVersionMinor';

server should start after that

Из "готовых" девайсов поддерживается протокол NTCB (https://navtelecom.ru/ru/).
Также есть поддержка USB/Serial GPS приемников агентом NetXMS, т.е. оно будет работать на каком-нибудь Raspberry Pi.
И есть Android агент, он также поддерживает GPS.

The reason could be that caching_sha2_password, let me cite a paragraph from the docs:

Bundled MySQL database drive does not support caching_sha2_password authentication which is default for MySQL starting from version 8.  Either select Legacy Authentication Method  when  installing  MySQL,  or  use  database  driver  installed  along  with  MySQL.  Databasedriver gets installed when installing MySQL with Server-only option,  however these two folders should be included into system path:C:\Program Files\MySQL\MySQL Server 8.0\lib C:\Program Files\MySQL\MySQL Server 8.0\bin.

Currently CreateSNMP transport does not support this. I've created an issue, also there's no particular plan when this could be implemented https://track.radensolutions.com/issue/NX-2062

Meanwhile you can try creating multiple nodes with the same IP address, setting checkbox "Communication through external gateway" (this is needed so that system ignores same IP address for these nodes). Each node would have specific community string set. To consolidate all monitored values onto one node you can configure "push" DCIs on that one node and use PushDCIData() from transformation script in DCIs of the additional nodes.

If your device returns list of interfaces for all of these community strings, then interfaces with same IP address would be created. This should not cause much troubles, but you can handle this in Hook::CreateInterface to avoid interface creation for the additional nodes.

The code is correct for nodes. But configuration poll could happen for other objects, e.g. clusters. In that case there is $object variable, but $node is not available.
You can change the 2-nd line to:
if (classof($object) == "Node" && $node->driver  == "MIKROTIK")

If osquery supports ODBC, then it could be accessed that was as dbquery sybagent supports ODBC.

Otherwise it could be technically possible to develop netxms database driver that would support osquery.

What is the value of AllowedCiphers in Configuration -> Server configuration?

Did you install from packager or compiled? Can you set DebugLevel=6 in server configuration file, start the server, wait for it to crash and share last few lines of the log?

It's saying "Refer to the logs for more information". Can you check if jira is producing any logs?

If DCI has node name in "Template" column this means that this DCI was created by instance discovery. Somewhere on the node there should be prototype DCI, which defines how instance discovery is happening.

e.g. in the attache image DCI with ID 4957 is instance prototype. It's coming from Generic UNIX template. Other DCI are created with instance discovery based on this DCI.

The script in your example returns only one alarm for each key. E.g. if you have several node with NODE_DOWN alarm, only one will be returned.

Can you give some information on what you are trying to achieve as the final result?

If this is still an issue - what are values of StatusPropagationAlgorithm and StatusCalculationAlgorithm in Configuration->Server Configuration?

That's how  the system is built - while interfaces exist as child objects of a node, events and alarms are created on the node itself.
Interface name is present in event's parameters, so if you need it for some custom processing in Event Processing Policy, you can get it there using NXSL (the built-in scripting language).

Yes, right, nxapush is intended to run on remote nodes, not on the server.

If the system is correctly configured initially - agent configuration file allows connection from server - the configuration poll will happen automatically and server will properly operate with the agent. If the agent is not accessible when server is launched for the first time, the server will remember that agent is not available on that node.
That's standard procedure - server remembers, if agent or SNMP is available on each node. This is seen in Object Details - Capabiliest (isAgent, etc). Capabilities are changen on Full configuration poll (and also automatically, but with very big time interval).

1) install netxms-agent package - you probably did that
2) in /etc/nxagentd.conf there should be
MasterServers=127.0.0.0/8
3) there should be a node in netxms that corresponds to your netxms server. This node is automatically created with external IP of your machine. In properties of that node -> Communications change primary host name to 127.0.0.1
4) perform Poll -> Configuration (full) on that node. Poll output should say that there is communication with the agent.
5) try nxapush

Also, if you need to push values from server there's nxpush utility that connects directly to netxms server.