NetXMS Support Forum

Try checking alarm log (View -> Alarm log) to see what was happening - what was the event that triggered the alarm and what is the alarm key.

Ah, I was thinking of .deb packages.

Generic builds are limited to use only dependencies that are available everywhere. That's why curl, ssh and asterisk stuff is not included. Web services are depending on curl.

We will try to prepare a build that would be suitable for Centos 7/8.

The basic approach is data collection via SSH - you just create a DCI with SSH origin, its running a command on the remote system and saves first line of output as DCI value.
https://www.netxms.org/documentation/adminguide/ssh-monitoring.html

Please inform, if this suits your needs.

You can try using Custom schedule and specifying exact seconds for various DCIs: https://www.netxms.org/documentation/adminguide/appendix.html#cron-format

Other possible approach could be network traffic throttling: https://man7.org/linux/man-pages/man8/tc-tbf.8.html

Which exactly version are you installing? Is it from packages or you compiled?

In NetXMS alarms that are present on a node affect node status.

Looks like your EPP does not have a rule to automatically terminate node down alarm when node comes back up (see screenshot of default EPP configuration on that).

What's currently in alarms for this node (right click on node -> alarms)?

netsvc should not be required for web services. It should be present in netxms-agent package, please check output of
dpkg-query -L netxms-agent
If its not there, what is the version of OS?

No, nxget, nxaction, nxwsget do not support tunnel connection - they attempt to connect to agent directly.

А какая точно версия NetXMS?

Можно на лету поднять ненадолго уровень дебага до 7 уровня:

nxadm -c "debug 7"

и попробовать отправить письмо. Потом опустить дебаг обратно

nxadm -c "debug 0"

Возможно, в логе будет что-то интересное.

Еще, как вариант, поснифить обмен с 25 портом на localhost с помощью Wireshark.

У меня не получилось повторить. Какая точно версия? Можете проверить на самой свежей 3.7?
Проявляется только в трансформационном скрипте, или если на ноде сделать Execute Server Script, то там тоже? Что именно в $1?

I've created an issue for this feature https://track.radensolutions.com/issue/NX-2003, but it might take quite a while until developers get to this.

Видимо что-то поменялось в языке. По документации SecondsToUptime принимает целый агрумент, так что можно округлить:

SecondsToUptime(round($1/100))

It's recommended to connect using mysql client, not 3rd party software, as heidisql is crashing here.
https://dev.mysql.com/doc/refman/5.7/en/mysql.html

It all looks like some issue with MySQL, possibly the database is corrupted. May be you can find some useful information here: https://stackoverflow.com/questions/25039927/database-corruption-with-mariadb-table-doesnt-exist-in-engine

If you have backup, I would suggest to restore from it.
Also, we generally find Postgres more reliable (if you decide to go this way, nxdbmgr allows to migrate between database engines).

A possible way to debug here is nxwsget command line app that is included with the server. This way you can isolate, whether the problem is on agent or on the server side. E.g.:
nxwsget 127.0.0.1 http://api.open-notify.org/astros.json number

Can you check in MySQL if "nodes" table exists?

Did you also upgrade MySQL itself? Can you check, if there are any errors in MySQL log file?