NetXMS Support Forum

This should be fixed in the current version

I am currently using NetXMS 6.1 and I've noticed that I am not always getting alarms when nodes become unreachable at least not immediately. I have also observed timeouts when using the client for simple activities like creating a new node that I have previously not encountered before.

I took a look at the log for my server and noticed these entries -

2026.04.17 09:16:50.436 *I* [watchdog           ] Thread "Recurrent scheduler" r                           eturned to running state
2026.04.17 09:17:48.752 *I* [watchdog           ] Thread "Syncer Thread" returne                           d to running state
2026.04.17 09:19:36.335 *E* [watchdog           ] Thread "Syncer Thread" does no                           t respond to watchdog thread
2026.04.17 09:21:56.337 *E* [watchdog           ] Thread "Recurrent scheduler" d                           oes not respond to watchdog thread
2026.04.17 09:24:24.322 *I* [watchdog           ] Thread "Recurrent scheduler" r                           eturned to running state
2026.04.17 09:26:36.342 *E* [watchdog           ] Thread "Recurrent scheduler" d                           oes not respond to watchdog thread
2026.04.17 09:32:38.323 *I* [watchdog           ] Thread "Recurrent scheduler" r                           eturned to running state
2026.04.17 09:33:06.359 *I* [watchdog           ] Thread "Syncer Thread" returne                           d to running state
2026.04.17 09:34:56.347 *E* [watchdog           ] Thread "Syncer Thread" does no                           t respond to watchdog thread
2026.04.17 09:35:56.348 *E* [watchdog           ] Thread "Recurrent scheduler" d                           oes not respond to watchdog thread

I'd appreciate any suggestions on how to fix this.

Hi,

since upgrading to v6 one of my SQL-queries is slower than usual.
Similar queries are still fast like before the update.

I don't know why the DB should threat them differently.


Slow Query:
SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value'
-> FROM idata_1177 d
-> JOIN items i ON i.item_id = d.item_id
-> WHERE i.item_id IN (38416,38421,38422)
-> AND idata_timestamp BETWEEN <starttime> AND <endtime>
-> ORDER BY idata_timestamp;

describe idata_1177;
+-----------------+--------------+------+-----+---------+-------+
| Field           | Type         | Null | Key | Default | Extra |
+-----------------+--------------+------+-----+---------+-------+
| item_id         | int          | NO   | PRI | NULL    |       |
| idata_timestamp | bigint       | NO   | PRI | NULL    |       |
| idata_value     | varchar(255) | YES  |     | NULL    |       |
| raw_value       | varchar(255) | YES  |     | NULL    |       |
+-----------------+--------------+------+-----+---------+-------+


EXPLAIN SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value'
-> FROM idata_1177 d
-> JOIN items i ON i.item_id = d.item_id
-> WHERE i.item_id IN (38416,38421,38422)
-> AND idata_timestamp BETWEEN <starttime> AND <endtime>
-> ORDER BY idata_timestamp;
+----+-------------+-------+------------+-------+---------------+---------+---------+------------------+------+----------+----------------------------------------------+
| id | select_type | table | partitions | type  | possible_keys | key     | key_len | ref              | rows | filtered | Extra                                        |
+----+-------------+-------+------------+-------+---------------+---------+---------+------------------+------+----------+----------------------------------------------+
|  1 | SIMPLE      | i     | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL             |    3 |   100.00 | Using where; Using temporary; Using filesort |
|  1 | SIMPLE      | d     | NULL       | ref   | PRIMARY       | PRIMARY | 4       | netxms.i.item_id | 1355 |    11.11 | Using where                                  |
+----+-------------+-------+------------+-------+---------------+---------+---------+------------------+------+----------+----------------------------------------------+
2 rows in set, 1 warning (0,00 sec)


EXPLAIN ANALYZE SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value' FROM idata_1177 d JOIN items i ON i.item_id = d.item_id WHERE i.item_id IN (38416,38421,38422) AND idata_timestamp BETWEEN <starttime> AND <endtime> ORDER BY idata_timestamp;
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| EXPLAIN |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| -> Sort: d.idata_timestamp  (actual time=2041.314..2041.572 rows=4318 loops=1)
    -> Stream results  (cost=418.24 rows=452) (actual time=978.482..2039.624 rows=4318 loops=1)
        -> Nested loop inner join  (cost=418.24 rows=452) (actual time=978.464..2037.612 rows=4318 loops=1)
            -> Filter: (i.item_id in (38416,38421,38422))  (cost=3.63 rows=3) (actual time=0.086..0.144 rows=3 loops=1)
                -> Index range scan on i using PRIMARY over (item_id = 38416) OR (item_id = 38421) OR (item_id = 38422)  (cost=3.63 rows=3) (actual time=0.084..0.137 rows=3 loops=1)
            -> Filter: (d.idata_timestamp between 1776340969454 and 1776427369454)  (cost=7.70 rows=151) (actual time=678.666..679.068 rows=1439 loops=3)
                -> Index lookup on d using PRIMARY (item_id=i.item_id)  (cost=7.70 rows=1355) (actual time=0.046..659.711 rows=525672 loops=3)
 |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (2,05 sec)


Fast Query:
SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value'
-> FROM idata_921 d
-> JOIN items i ON i.item_id = d.item_id
-> WHERE i.item_id IN (83253,83254)
-> AND idata_timestamp BETWEEN <starttime> AND <endtime>
-> ORDER BY idata_timestamp;

describe idata_921;
+-----------------+--------------+------+-----+---------+-------+
| Field           | Type         | Null | Key | Default | Extra |
+-----------------+--------------+------+-----+---------+-------+
| item_id         | int          | NO   | PRI | NULL    |       |
| idata_timestamp | bigint       | NO   | PRI | NULL    |       |
| idata_value     | varchar(255) | YES  |     | NULL    |       |
| raw_value       | varchar(255) | YES  |     | NULL    |       |
+-----------------+--------------+------+-----+---------+-------+


EXPLAIN SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value'
-> FROM idata_921 d
-> JOIN items i ON i.item_id = d.item_id
-> WHERE i.item_id IN (83253,83254)
-> AND idata_timestamp BETWEEN <starttime> AND <endtime>
-> ORDER BY idata_timestamp;
+----+-------------+-------+------------+--------+---------------+---------+---------+------------------+------+----------+-----------------------------+
| id | select_type | table | partitions | type   | possible_keys | key     | key_len | ref              | rows | filtered | Extra                       |
+----+-------------+-------+------------+--------+---------------+---------+---------+------------------+------+----------+-----------------------------+
|  1 | SIMPLE      | d     | NULL       | range  | PRIMARY       | PRIMARY | 12      | NULL             | 2880 |   100.00 | Using where; Using filesort |
|  1 | SIMPLE      | i     | NULL       | eq_ref | PRIMARY       | PRIMARY | 4       | netxms.d.item_id |    1 |   100.00 | NULL                        |
+----+-------------+-------+------------+--------+---------------+---------+---------+------------------+------+----------+-----------------------------+
2 rows in set, 1 warning (0,00 sec)


EXPLAIN ANALYZE SELECT CONVERT(i.description, CHAR) 'metric', FLOOR(idata_timestamp/300000)*300000 'time', CONVERT(idata_value,DOUBLE) 'value' FROM idata_921 d JOIN items i ON i.item_id = d.item_id WHERE i.item_id IN (83253,83254) AND idata_timestamp BETWEEN <starttime> AND <endtime> ORDER BY idata_timestamp;
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| EXPLAIN |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| -> Nested loop inner join  (cost=3749.56 rows=2880) (actual time=1.607..5.474 rows=2880 loops=1)
    -> Sort: d.idata_timestamp  (cost=581.56 rows=2880) (actual time=1.563..1.708 rows=2880 loops=1)
        -> Filter: ((d.item_id in (83253,83254)) and (d.idata_timestamp between 1776340969454 and 1776427369454))  (cost=581.56 rows=2880) (actual time=0.021..1.171 rows=2880 loops=1)
            -> Index range scan on d using PRIMARY over (item_id = 83253 AND 1776340969454 <= idata_timestamp <= 1776427369454) OR (item_id = 83254 AND 1776340969454 <= idata_timestamp <= 1776427369454)  (cost=581.56 rows=2880) (actual time=0.018..0.876 rows=2880 loops=1)
    -> Single-row index lookup on i using PRIMARY (item_id=d.item_id)  (cost=1.00 rows=1) (actual time=0.001..0.001 rows=1 loops=2880)
 |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0,01 sec)

We just published patch release 1 for version 6.1. Changes since version 6.1.0:

- Notification channel driver for Matrix
- Improved status poll implementation when poll count for status change is greater than 1
- Fixed bug in context menu display in alarm view, data collection view, and other table views
- Fixed background colors in alarm view
- Fixed issues:
  - #2471 / NX-2264 (In rack view, tooltip is shown for chassis, not for its elements)
  - #2560 / NX-2354 (Agent file policy are not propagated to cluster member nodes)
  - #2978 / NX-2776 (Add additional parameters to events created from synchronized Windows Events)
  - #3018 / NX-2816 (L2 topology map is built with same interface used multiple times)
  - #3036 / NX-2834 (Do not display value in percent in bar chart legend)
  - #3126 / NX-2926 (Logwatch last read location is incorrectly saved for Windows agent)
  - #3166 (Escape special characters in Prometheus metric argument values)
  - #3173 (Set restrictive file permissions on auto-generated cert/key files)
  - #3175 (CTabFolder high CPU consumption in Infrastructure and Entire Network)
  - #3176 (Support for installed product list retrieval on apk-based distributions)
  - #3189 (Incorrect current value in chart legend)
  - #3190 (Multiple Asterisk subagent metrics fail on newer Asterisk versions)

Just to inform that x86_64 linux static agent is missing in today 6.1.1 release (https://netxms.com/download/releases/6.1/nxagent-6.1.1-linux-x86_64-static.tar.gz)...

mariadb

Hi, 6.1.0 is live, 6.1.1 is merged, but still waiting for CI. Usually it's become available in matter of hours.

Quote from: dneil on April 16, 2026, 03:03:20 PMWhen will the 6.1 Client be released to Flathub?  I've updated my server today and now I don't have a working client on my Linux boxes.

Thanks so much Filipp, I looked in the documentation but hadn't noticed it,
Alessio.

Sorry, this was overlooked for a while. First guess is that there are some issues with syncer thread. It's not visible in show threads, as there's just one syncer threads. In debug console there's

netxmsd: sh sy
Last run at .........: 16.Apr.2026 15:22:58
Last run time .......: 1 ms
Average run time ....: 119 ms
Max run time ........: 132 ms
Min run time ........: 0 ms

And System -> NetXMS Server -> Server Performance has metrics for it, specifically Server.SyncerRunTime.Last. Pls check if this metric looks reasonable.

Slow log opening might indicate problems with DB performance, DB might need tuning. What are the specs on DB VM, is it dedicated to NetXMS or a shared database? How's CPU consumption and IO stats? How big is the database on disk?
You can also use mysql subagent to collect stats about DB operation - https://netxms.org/documentation/adminguide/database-monitoring.html#mysql

Which database you are using?