NetXMS Support Forum

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

We just published patch release 4 for version 6.1. It fixes few important issues: slow data conversion after migration from 5.2 or older versions, and client freeze or slow drawing of stacked charts. Some other small fixes and improvements made their way to the release as well:
- #3284 (nxdbmgr: migration fails on empty items.transformed_datatype with PostgreSQL)
- #3290 (Text in Status Explanation unreadable due to it's color)
- #3291 (Fixed time frame setting not preserved when chart view is pinned or moved between areas)
- #3298 (DCI image map element tooltip shows only DCI name, not current value)
- #3306 (Agent list instance discovery not working via gateway node on sensor)
- #3309 (Add /health endpoint in nxmc/web)

Thanks a lot for your help. I'll give it a try.

Another question: can the password be entered using `nxencpasswd`?

Thank you!

Thank you for your reply, Tatjana.

My mistake was because I had the following definition:

Module = webapi,Y
[WEBAPI]
...

Module = oxidized.nxm
[OXIZIDIZED]
...
The module declarations need to come before the configuration:

Module = webapi,Y
Module = oxidized.nxm

[WEBAPI]
...
[OXIDIZED]
...

This way, it works!

Thank you!

For 2-hour window for a server action in an EPP rule set the following:
- Snooze time: 7200
- Snooze/blocking timer key: NODE_DOWN_%i

What this does - on the first time when action is executed is starts a timer with given key, on next executions it will run the action only if such timer is not running.

You can watch these timers in Configuration->Scheduled tasks if you enable "Show system tasks" there.

Is the problem is node-wide, e.g. node down you can use timer key with just %i macro - this will expand into node's id. If problem is related to a DCI use a %i_%<dciId> macro combination - this will be both node ID and DCI ID to ensure uniqueness of the timer key.

Comments are available in open testing track (https://play.google.com/apps/testing/org.netxms.android); 1.0.6 / build 27.

Great!
Thanks a lot .

Quote from: Filipp Sudanov on June 09, 2026, 12:36:35 PMCan you give some examples of the issues for which you want to send notifications? How it can be determined that it's the same issue?

Thanks for your reply!

For nodes with frequent online/offline status or fluctuating PING latency around the threshold caused by line issues, do not send repeated alarms temporarily as the admin has been informed. Send recovery alerts only after the initial alarm is issued, and keep alerting for other new fault types on the same node.

Quote from: hellium on June 10, 2026, 03:39:56 PMBut the mobile client is incredibly limited in what data it shows.

well, that's why I'm asking for feedback

I've added comments section on object details, will be included in next update.