NetXMS Support Forum

Currently NetXMS supports "Nested Group" functionality, so I'll just add the same for LDAP sync.

It looks like it might be MarinaDB problem we have fixed (we had a lot of problems with MarinaDB recently). Most probably this problem happened due to corrupted DB upgrade. The fix will be included in next release 2.2.9. Now this problem could be fixed only with hands, by manually adding a column to the table or as you did - by recreating the database.
We highly do not recommend SQLite usage, we recommend PostgreSQL as a database.

Latest stable branch javadoc: https://www.netxms.org/documentation/javadoc/stable/
Release 2.2.8 javadoc: https://www.netxms.org/documentation/javadoc/versioned/Release-2.2.8/

There are two options. You can set ulimit in console and run netxmsd by hands on this console or edit the netxmsd system file (add LimitCORE=infinity line). More information can be found there: https://unix.stackexchange.com/questions/345595/how-to-set-ulimits-on-service-with-systemd

Fix will be included in next stable build.

Verify that debug packages for netxms are installed (if installed from the repository), set ulimit to unlimited and provide core dump.

Debug script is created for the Linux systems. In Windows you can create dumb from Task Manager by right click on the process "Create Dump File". Sorry, that have not asked for the OS first.

Multiple search bases can be used separated by semicolon ( symbol.
Configuration looks OK. You can check server log on 4 lvl.

Yes you can synchronize also groups from LDAP (just use correct LdapSearchFilter and LdapGroupClass). In case of Windows AD LdapGroupClass should be "group". You also can create groups in NetXMS and add LDAP users under NetXMS groups. If as LdapUserUniqueId and LdapGroupUniqueId   "objectGUID" will be used, then even if you will move users or groups in LDAP they will be considered as the same users even though they have different DN.

Looks like you have really a lot of object updates and server is unable to delivere all updates to the client so everything just stuck. I'll rework object update messages, but can't promise the release number where it will get in.

Hi,

Yes it might be the issue. Can you please update your system to 2.2.8 and check poller load by "show threads" command? If "Current load" will be more than 100%, than can you please take thread dump using https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh script? Please check that debug packages are installed if server is installed from repository.

Script usage:
Run script with first parameter - path to netxmsd binary, script will generate thread dump into /tmp folger

What is difference between servers? Number of nodes, different OS?

You can use Internal "Dummy" DCI and make all scripting in transformation script section.

Исправлено в версии 2.2.7. Возможное временное решение для Status map это убрать в настройках элемента фильтр (возможно уберёт проблему).

Please check that group everyone has System Right "View all alarm categories". Node status is not affected by events. It can be affected by status calculation(properties of object), by default status is calculated based on child object status, alarms, and DCI's that have "Use this DCI for node status calculation" option selected.