NetXMS Forum

Hi, This is a bug in the server, not your configuration: https://github.com/netxms/netxms/issues/3682 Here's what's actually happening: when the node leaves maintenance mode, the server re-generates threshold events for every threshold whose state changed during maintenance. That's where your two "task running" events at 04:00 came from. Those events can be processed while the node is still flagged as in maintenance, and then they get correlated to the "maintenance enter" event, which is why they reference 8766568. By default, EPP rules ignore correlated events, so the rule that should terminate the alarm never sees them. It's a timing race, which is why it only happens sometimes. Workaround until it's fixed: enable Accept correlated events on the EPP rule that terminates the alarm on OS_PROCESS_OK. As a side effect, the alarm will also be terminated when the task recovers while the node is still in maintenance, which is probably what you want anyway. If the same rule also creates the alarm, split it into two rules and set the flag only on the terminating one. Otherwise alarms will be created during maintenance too.

Hello Alex, you are right. My mistake was that I downloaded the wrong file, now it works as expected. Thank you

Hi Alex, Thanks for the detailed explanation. The problem was caused by an offline network mount. After disabling the metric on the server and restarting the agent, it runs without any issues. One weird thing that happened while troubleshooting was that the command gdb -p $(pgrep nxagentd) --batch -ex 'thread apply all bt' > nxagentd-threads.txt  didn't generate thread information; it only displayed "[New LWP <process ID>]" lines.

Database query planning is a separate mystery on its own. Anyways, developers restored additional index as it was before v. 6.0, that will be included in next patch release.