NetXMS Support Forum

To clarify, with what exactly version are the screenshots?

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.

Да, так правильно. Ну или можно чуть более лаконично:

if (($node.name in ["ISW001", "ISW002", "ISW003"]) and ($1.name ~= "^VLAN.*"))
{
    return false;  // не создавать VLAN-интерфейсы
}
return true;


Это напереповторявшиеся задачи на деплой пакетов. Там есть косяк, что у переповторов нет ограничения: https://github.com/netxms/netxms/issues/3277

Ну и второй косяк, что при старте сервер всю эту таблицу грузит в память: https://github.com/netxms/netxms/issues/3402

У колонки статус в базе значения такие 0=scheduled ... 5=running states, 6=completed, 7=failed, 8=cancelled.
Можно стереть все со статусом 7 (при остановленном сервере). Ну или вообще очистить эту таблицу, а то они опять наповторяются (ну или в UI эти задачи отменить).

Треды нормально собрались, все хорошо. Дока возможно через cloudflare не обновилась сразу.

А это такие запрос к базе покажут:

SELECT count(*) FROM package_deployment_jobs;

SELECT status, count(*) FROM package_deployment_jobs GROUP BY status;

А можете попробовать собрать дамп потоков сервера в в то время, когда сервер так тупит при старте? Инструкция тут: https://netxms.org/documentation/adminguide/advanced.html#collecting-a-thread-dump

Скрипт нужно запустить 3 раза, получившиеся файлики прислать нам

Fix for the issue should be available in v. 6.2.

Вероятно эти сложности: https://www.netxms.org/forum/general-support/issues-upgrading-from-netxms-server-6-1-4-to-6-2-0-via-apt-package-manager/msg35569/#msg35569

For XML error - I don't see it in current development version log, so changes are that it's already fixed, pls double-check when v.6.2 is out.

For MIB error - I guess MIB compiler is failing on some specific MIB file. You can try removing some of your MIB files until you find which one is causing the issue (you can remove half of them, recomplie, then another half, etc...). Or you can just share your whole MIB file collection.

Make sure that IP address in node's Properties -> Communications is correct.
Then run Configuration Poll on that node.

If it's still not working, try enabling debug, from Tools -> Server Console:

debug syslog 6

and check server log lines when your device sends something.

Reading of installed software on Windows was fixed, please wait for release v.6.2 to come out.
The only note - for all this to work correctly you'd also need to upgrade server to v.6.2, because now agent reports packages with information about user name for each package and server prior to v.6.2. is not able to read this field.

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

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.