NetXMS Support Forum

Hi Alex,

have the developers been able to find anything in the meantime?
We're unfortunately losing track quite quickly due to the high volume of messages, as many of the monitored servers are terminal servers with a large number of users.

Best regards,
Alwin

Обновился сегодня до 6.1.4, картина та же - в логах
2026.06.15 09:14:46.273 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1019137] synchronized
2026.06.15 09:14:47.378 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [24221] synchronized
2026.06.15 09:14:47.854 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1156814] synchronized
2026.06.15 09:14:48.502 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [30735] synchronized
2026.06.15 09:14:51.565 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1124015] synchronized
2026.06.15 09:14:53.247 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [25299] synchronized
2026.06.15 09:14:53.267 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [25294] synchronized
2026.06.15 09:14:53.283 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод  [25290] synchronized
2026.06.15 09:14:53.297 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [25279] synchronized
2026.06.15 09:14:56.335 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [24221] synchronized
2026.06.15 09:15:15.217 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1169854] synchronized
2026.06.15 09:15:22.324 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1169854] synchronized
2026.06.15 09:15:22.341 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [1228844] synchronized
2026.06.15 09:15:33.625 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод  [40143] synchronized
2026.06.15 09:15:37.719 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [51255] synchronized
2026.06.15 09:15:39.234 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [46110] synchronized
2026.06.15 09:15:39.550 *D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node именаНод [61507] synchronized

Just added physical interface marking in FortiSwitch driver.

Сделал исправление в сервере, должно исправить падение. Войдет в следующий релиз.

sh st
Objects............: 58867
   Nodes...........: 9113
   Interfaces......: 47716
   Access points...: 0
   Sensors.........: 0
Collectible DCIs...: 168107
Active alarms......: 245
Uptime.............: 3 days, 13:25:08

В ноды вообще все скопом эндпоинты идут? В духе точек, принтеров и т.п.

Cache mode в default, в настройках сервера off

Regarding the XML error, is there a way to find out which section the error originates from? This makes it difficult to view the server logs over time.

Regarding the MIB error, yes, the date changes and when I compile via the GUI a new file is created, but it remains invalid, although no error is reported.

I've had to manually edit some MIB files before uploading them to the interface due to inconsistencies in their definitions, but I don't remember exactly which ones.

Thank you!

sh st - только при запущенном сервере, но в принципе оттуда только количество нод нужно было.

cache mode тут в доке описан: https://netxms.org/documentation/adminguide/data-collection.html#offline-data-collection

Yes, these messages are 251-related. I've created ticket for this issue: https://github.com/netxms/netxms/issues/3322

Quote from: lhpaladin on June 12, 2026, 03:58:29 AMAnother question: can the password be entered using `nxencpasswd`?

Ups, that was forgotten in the implementation. Hopefully will be fixed in 6.2, created a ticket for it: https://github.com/netxms/netxms/issues/3321