NetXMS Support Forum

Just closed issue 3023 (former NX-2821) - will be part of release 6.2.0.

Something like this was reported due to some dashboard elements leaking resources. Please try upgrading to 6.1

That's due to user-configurable tool nature. If all system users use same language, you can just change tool names in server configuration. However, if different language must be supported currently there is no solution. I've registered issue in our tracker for adding localization support to object tools:
https://github.com/netxms/netxms/issues/3243

A couple time a day the client hangs with GDI Objects maxed out at 10,000 (see screenshot). Currently on 6.1.1, but the issue started sometime around the 5.2.7 or 5.2.8 upgrade.

Нет, в rootID 0
Источник один, ивенты соотвествуют вроде

Добрый день.
Столкнулись с проблемой на новых коммутаторах SNR-S5310G-48TX-2AC, при SNMP опросе возвращаются пустые (0) значения в поле Interface. Вероятнее всего проблема в драйвере (обычно используем generic cisco для коммутаторов этой фирмы), на коммутаторах серии SNR-5ххх название идет через ge# или xe#. Также на серии 5ххх отличается и идентификатор порта, а именно 50<номер порта>, например, для физического порта ge20 идентификатор будет 5020.
reinterpret_cast<const PCRE_TCHAR*>(_T("^(Se|Serial|Et|Ethernet|Fa|FastEthernet|Gi|GigabitEthernet|Te|TenGigabitEthernet|Fo|FortyGigabitEthernet)([0-9]+)/([0-9]+)$")),
         PCRE_COMMON_FLAGS | PCRE_CASELESS, &eptr, &eoffset, nullptr));т.е. по идеи достаточно добавить в выборку драйвера |ge|xe ? Можете ли помочь с компиляцией такого драйвера?

Issue:
Windows agent tunnel binding fails on every attempt
Server log: IssueCertificate: certificate request verification failed (0 ms — fails at parse, not signature)
Agent log: certificate request failed (923)
Linux agents on same server bind successfully

NetXMS Server Info:
AlmaLinux 9.7
System OpenSSL 3.5.1
NetXMS server 6.1.1, build 6.1-452-gc20a8a4247
Self-signed CA, valid 2036
netxmsd.conf has TunnelCertificate, TunnelCertificateKey, InternalCACertificate, InternalCACertificateKey configured

Tested against:
Win 10 Pro 22H2 (19041)  | Agent v6.1.1 | Fails with 923
Win 11 Home 24H2 (26200) | Agent v6.1.1 | Fails with 923
Win 11 Home 24H2 (26200) | Agent v5.2.8 | Fails with 923
AlmaLinux 9.7            | Agent v6.1.1 | Binds Successfully

Steps to Produce:
AlmaLinux 9.7 + OpenSSL 3.5.1 + NetXMS 6.1.1 server
Self-signed CA per standard tunnel setup
Install Windows agent, configure ServerConnection + TrustedRootCertificate
TLS handshake completes, tunnel appears Unbound
Right-click → Create node and bind → error 923


See attached logs from tests above.

Please advise if you need any further information. I have not tried on the latest 6.1.2, as there doesn't appear to be an direct fix for this issue.

Thanks,

In the original log parser policy editor screenshot you have Level set to 1, but in XMLs you have values 2 and 3.

А в event log, у этого события есть что-нибудь в Root ID? Если есть, то что за событие с таким ID?

Quote from: Filipp Sudanov on May 13, 2026, 05:14:02 PM#3 which exactly part of GUI is this?

Packages -> Upload to server..

but in 6.1.2 - now ok. I think problem solved. Maybe it was related to old coockies.