NetXMS Support Forum

I have a few devices running and resolving with a fix IP address and sending syslog to NETXMS server.  These devices are mostly routers.  My question is when I change the router device IP, the device seems to continue to work fine and DNS is updated. But all the syslog messages are no longer updating.  I cannot seem to get them back.  Is there a way to remap the old device ip to new one.

I've tried deleting the device, and readding it back, but nothing seems to make syslog update the new address to allow the messages to map to the device. 



Thanks

Hi,

Those messages are warnings, not errors. Upgrade did not fail. This is normal PostgreSQL collation mismatch. Has nothing to do with 15→17 — comes only from Debian 12→13, because Trixie has glibc 2.41 instead of 2.36, and PostgreSQL remembers glibc version used to build indexes.

For in-place upgrade use pg_upgradecluster. Stop NetXMS, make dump for safety, drop empty PG17 cluster that was auto-created, then upgrade:

systemctl stop netxms-server
sudo -u postgres pg_dump -Fc netxms > /backup/netxms.dump   # safety net
pg_dropcluster 17 main --stop        # remove empty auto-created PG17 cluster
pg_upgradecluster 15 main
nxdbmgr check
systemctl start netxms-server
# when verified:  pg_dropcluster 15 main

Important detail: pg_upgradecluster without --method=upgrade uses dump method inside. It rebuilds all indexes under new glibc, so you get no collation warnings and no reindex needed. Only -m upgrade / -m link (fast file-reuse mode) makes the warnings. If you use that mode, fix it correct way — reindex first, then refresh — for each database (netxms, postgres, template1):

REINDEX DATABASE netxms;
ALTER DATABASE netxms REFRESH COLLATION VERSION;

Do not run only REFRESH. It hides warning but leaves bad-sorted indexes. Reindex is mandatory.

Hello @all,

today i updated our NetXMS server vom Debian 12 to 13. At the first try i upgraded, as part of the Debian Update, the Postgres Cluster from 15 to 17 too. But there are many warnings:

Example:
Fixing hardcoded library paths for stored procedures...
WARNUNG:  Version von Sortierfolge für Datenbank »postgres« stimmt nicht überein
DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE postgres REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
Upgrading database postgres...
WARNUNG:  Version von Sortierfolge für Datenbank »postgres« stimmt nicht überein
DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE postgres REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
Fixing hardcoded library paths for stored procedures...
WARNUNG:  Version von Sortierfolge für Datenbank »netxms« stimmt nicht überein
DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE netxms REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.
Upgrading database netxms...
WARNUNG:  Version von Sortierfolge für Datenbank »netxms« stimmt nicht überein
DETAIL:  Die Datenbank wurde mit Sortierfolgenversion 2.36 erzeugt, aber das Betriebssystem hat Version 2.41.
TIP:  Bauen Sie alle Objekte in dieser Datenbank, die die Standardsortierfolge verwenden, neu und führen Sie ALTER DATABASE netxms REFRESH COLLATION VERSION aus, oder bauen Sie PostgreSQL mit der richtigen Bibliotheksversion.

So i decided to rollback the snapshot of the VM and upgrade Debian without the cluster update of Potsgres.

Are there any howto's or links to websites where i can figure out how i make the Postgres Cluster Update from 15 to 17 on the "right" way for NetXMS?

Greetings
Marco

Dear NetXMS Moderators and Support Team,
I am writing to ask for your guidance on an interface identification issue.
I have two Huawei C8865 switches configured as an MLAG pair, with IP addresses 10.61.10.9 and 10.61.10.10 respectively. There are only 3 physical ports used for inter-switch interconnection between the two devices. However, NetXMS incorrectly recognizes a large number of other unrelated ports as inter-switch interconnect ports.
I have uploaded the system screenshots and detailed interface information for your reference. It would be highly appreciated if you could help look into this issue and offer some advice.
Thank you very much for your time and assistance.

Может быть проблемой изменение в 6.1.3 "-   Server no longer attempts to retry agent package deployment after non-transient errors"?
Ближе к старту логи перемежаются с
*D* [packages           ] Completed package deployment job [13196459] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196460] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196461] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196462] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196463] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196464] (package [4] "nxagent-6.0.1-x64.exe") removed
*D* [packages           ] Completed package deployment job [13196465] (package [4] "nxagent-6.0.1-x64.exe") removedпростыней таких записей. Причем даже после пары стартов сервера(по нескольку дней тваких записей -_-) он не перестает их спамить.
Я пересадил интереса ради сервис на пустую базу - мгновенно запускается без проблем. История о деплоях я так понимаю в базе хранится, ее принудительно есть вариант зачистить?

Hi Filipp,

Thanks for feedback.

I think one thing that could be implemented would be permissions to view the list of backups performed and another to export or view the backup content.

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.

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