NetXMS Support Forum

Syncronized
not syncronized grep не обнаружил в текущем и ближайших логах

Без запуска сервера это возможно сделать? gdb мб - в выводе help от него не нашел аналога

Большинство нод на Windows с агентами - что-то около 2-3 тысяч. Прокси в 99.999% случаев не используется ни с нодами, ни в настройках зон

Не припомню такой настройки, этот параметр отдельно заводится или дефолтный?

Its kinda working now.

But the mobile client is incredibly limited in what data it shows.

We are mainly missing the "comment" field :/.

Hi,

thank you for your answer - maybe i found the problem.

THe error message is like (in German): The message resource exists, but the message was not found in the string/message table.
Maybe this is the 251?

Могли быть недавние изменения в работе с прокси

что дальше в этих строчках в логе, "synchronized" или "not synchronized", каких строчек больше?

насколько большая система, покажите вывод sh st в debug console

сколько нод с агентами, работают ли они напрямую или через прокси, есть ли такое что на зонах указано больше одного прокси?

включен ли cache mode на агентах?

I don't see anything wrong in the configuration (the only thing to check if RAIDCONTROLLER_LSA_CRITICAL had "write to log" checkbox).

You can try right-clicking on the template and performing "Force deployment of agent policies".

Next step is to check that policy file is really present on this machine - they should be in C:\Windows\System32\ config\systemprofile\AppData\Local\nxagentd\logparser_ap (that's home folder of System user).

And next is to enable debug in agent config:
DebugTags = logwatch.*:7
agent log should have detailed information about logparser operations

Hi,

That message is expected if the Oxidized module itself is not loaded — it's logged at startup once the server has scanned all loaded modules and found none providing a device backup interface.

The thing to check: adding the OXIDIZED settings section to netxmsd.conf only provides configuration values — it does not load the module. You also need to add the module to the load list:

Module = oxidized

So a complete config looks like this:

Module = oxidized

*OXIDIZED
BaseURL = https://oxidized.example.com
Login = user
Password = secret
DefaultModel = ios

Once the module is actually loaded, you should instead see:

[backup] Network device backup interface is provided by module OXIDIZED

If you've already got Module = oxidized in place and still see "not available", look at the lines just above it in the server log — the module reports the specific reason there, e.g.:

- Oxidized integration module initialization failed (cannot parse module configuration)
- Oxidized integration module initialization failed (invalid base URL) — the BaseURL must start with http:// or https://.

Starting the server with -D5 and checking the backup/oxidized debug-tag output will show exactly where it stops. Note that the Oxidized server being temporarily unreachable does not cause this message — that only produces a warning ("Oxidized server is not reachable, will retry on demand"), and the interface still initializes.

One more thing to confirm: the Oxidized integration was introduced in NetXMS 6.1.0, so make sure you're running 6.1.0 or later — on earlier versions the module doesn't exist.

Best regards,
Tatjana

XML parser error is not really an error - this happens in some places, e.g. if configuration of a notification channel is empty (or contains only comments).

/var/lib/netxms/netxms.cmib is more interesting. Is your server running under root user or some other user? Does this file change it's modification time when you compile MIBs from the GUI? You can just move this file to some other folder and then check if it's recreated by mib compilation.

Can 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?

NX-2437 only adds option to change MAC address for interfaces that were created manually, so guess this won't work in your case.

Дополнение от 9.6.26
Рестарт netxms-server привел к тому же процессу - "*D* [dc.agent.cache     ] Node::syncDataCollectionWithAgent: node" по куче нодов по логам и пока не стартанувший полностью сервер