NetXMS Support Forum

nxdbmgr check should be able to fix this specific sql error. And also this error should not crash the server.

Please try starting netxms server in foreground:
systemctl stop netxmsd
netxmsd -D 6

this way server will be putting it's log on the screen. When it crashes, you should see some info on the reason it crashed. Try running it a couple of times that way to see if it's crashing on the same log line.

Try adding
MaxSessions = 100
to agent configuration file (default for this setting is 32 - https://netxms.org/documentation/adminguide/appendix.html#agent-configuration-file-nxagentd-conf)

Are you collecting a lot of ssh metrics, do these metrics take long time to return value? Or is this agent a proxy or loaded with some other tasks? I just wonder why many sessions are used at the same time.

Try using
systemctl enable --now netxms-server.service

You can see unit names by issuing
systemctl | grep netxms

ssh connections in netxms are performed via agent that is running along with the server. You can try setting debug level 6 for that agent - one way is to stop it via systemctl:

systemctl stop nxagentd

and start in in foreyground:

nxagentd -D 6


Then try running configuration poll for your uniquiti node to see if ssh capability becomes yes. Or try adding a ssh DCI on that node and forcing poll for that DCI. Log of the above agent should have some lines about ssh.

Передано разработчикам

First thing to try would be 127.0.0.1 instead of localhost - may be localhost is resolved into ipv6 address and database does not like it?

Yes, the MySQL client library shipped with NetXMS requires to use "legacy password" mode (it's possible to replace this lib, but it's not what we are currently fixing).

I've just tried installing mysql-installer-community-8.0.34.0.msi and netxms 4.4.1, it worked fine.

Did you check "Create database and database user..." on the attached screen during installation:

Да, с наложением шаблонов есть ошибка в новом клиенте (он все еще в разработке). Можно взять легаси клиент.

Ага, ну у нас есть хук скрипт Hook::PostObjectCreate который отрабатывает после создания объектов. Можно в нем для новосозданных точек делать или unmanage или менят propogation.

Hi!

There should not be length limitation, I've just tried 500000 byte log web page and it works fine.

Possible reason could be that libcurl, on which NetSVC is based is checking tls certificates. The curl output that you provided - was that curl executed on the same system where netxms agent is running?

Если менять propagate status в свойствах access point то будет игнорироваться только состояние этого access point, но если контроллер сможет падать по другим причинам (перестанет отвечать, упадет один из интерфейсов...)

Другой вариант - access point можно перевести в maintenance

Покажите, что на закладке Targets у шаблона APC

И покажите, что в контейнере Infrastructure Services -> UPS


Еще раз, ошибка происходи когда, только при попытке наложении на контейнер UPS ?

Yes, NetXMS expects IP addresses to be unique within a zone. What probably should help - we can disable interface creation. In script library there is Hook::CreateInterface script, it is executed each time a new interface is found. Here's an example:

if ($node->snmpOID == ".X.X.X.X" and $1->name == "BR0") {
  PollerTrace("Blocking interface " .. $1->name .. " creation");
  return false;
}
return true;

I am checking node's SNMP ID, you can use any other approach - by subnet, container, etc - this is not to affect other nodes that might also happen to have an interface named BR0. PollerTrace line is optional - it's just for adding some info to output of manually-called configuration poll.
You have to delete all existing BR0 interfaces (or probably just one) that you have in your system.

SYS_MAC_ADDR_CHANGED - это когда у какой-то ноды меняется мак адрес на одной из сетевых карт (но при этом мы знаем, что это та же самая нода).

Когда к порту свича подключается какое-то новое устройство, по идее должно генерироваться событие SYS_IF_PEER_CHANGED

Для новых версий нужны Java 17+ и tomcat9. Или Jetty 10.
И еще можно воспользоваться лаунчером основанным на джетти https://github.com/netxms/nxmc-web-launcher