NetXMS Support Forum

Отправляю скриншоты правил уведомлений и логов событий.
Правила уведомления изменил на SYS_NODE_DOWN / SYS_NODE_UNREACHABLE, а когда нода поднимается обратно то SYS_NODE_UP.

Нет. Хуже. База начала расти постоянно. При входе в logs - alarm выдавала ошибку базы данных.
Архив тоже оказался проблемным (не сразу заметил проблемы, и с базой из архива случились те же проблемы что и с рабочей базой).
Итог: установил новый сервер на базе последней сборки netxms (6.2.1) на актуальной ubuntu server (26.04 LTS).

Проблему наблюдаю ту же что изначально. Смена событий для нотификации на предложенные не помогла. Завтра постараюсь прислать скриншоты

My apologies, I overlooked that. The version of NetXMS is 6.2.1.

Just to inform that after upgrade to 6.2.1 (server and web interface) graphs doesn't accomplish time period settings on first opening (eg. time period in properties is set to 1 day and they opens as last hour...).

Manual or auto refresh restores correct time period display settings....

To clarify, with what exactly version are the screenshots?

Thank you for your help! I found that the peer node information on both devices failed to fully auto-update to the latest timestamp. I have manually deleted all port entries with a Peer Last Updated timestamp from half a month ago on the two devices, then re-run the configuration polling operation with reset. Please refer to the attachment for the current running status of the devices; could you help analyze this issue and advise a solution?

Alex,

Thanks or the update and I appreciate the work around. It worked great !!

Thanks for the follow-up — you are right, 6.2.1 does not fully fix this.

The fix that went into 6.2.1 removed the visible flickering of the columns, but not the underlying cost. Grid views still re-measure and repack every column on each refresh cycle, and that is what you are seeing as constant repainting on the Data Collection and Interfaces tabs. On a node with many interfaces or DCIs a refresh can be triggered very often, so it never settles.

I've opened https://github.com/netxms/netxms/issues/3418 to track it. The proper fix is to repack columns only when the content actually changes shape (new columns, first data load, or when you ask for it), instead of on every refresh.

Until then you can avoid the problem by unchecking "Resize columns automatically" in the view menu of the affected view. The setting is remembered per view, and with it off the columns are no longer repacked on refresh.

Was this addressed in 6.2.1 ? if so I am still seeing the same thing. Its looks like a constant repainting of the data. I normally see it when looking at the Data Collection on a node or interfaces tab.

If it was upgraded and the version is still stuck, the servlet container is most likely serving the old version from its work directory. In that case:

    Stop the container (the NetXMS WebUI service, if installed with the Windows installer)
    Delete the contents of the work directory — C:\NetXMS-WebUI\jetty-base\work with the installer's default prefix; the location may differ for other containers or a custom setup
    Start the container again

After that, do a full page reload in the browser.