NetXMS Support Forum

English Support => General Support => Topic started by: Marshall Chen on March 30, 2020, 09:35:26 AM

Title: Internal DCI's of NetXMS server changed to UNSUPPORTED
Post by: Marshall Chen on March 30, 2020, 09:35:26 AM
I just upgraded NetXMS server from v2.2.10 to v3.2.400. Everything is fine apart from below DCIs of NetXMS server itself.

Server.ThreadPool.Load
Server.ThreadPool.CurrSize
Server.ThreadPool.LoadAverage
Server.ThreadPool.Usage
Server.Heap.Active
Server.Heap.Allocated
Server.Heap.Mapped

it's keeping sending alarm saying the status of DCI changed to UNSUPPORTED. I can't find any post to discuss this case, anyone can give some prompt?


Title: Re: Internal DCI's of NetXMS server changed to UNSUPPORTED
Post by: Woody on March 30, 2020, 03:09:37 PM
Hello,
here is the same issue, but on an other server:
https://www.netxms.org/forum/general-support/snmp-requests-changed-to-unsupported/ (https://www.netxms.org/forum/general-support/snmp-requests-changed-to-unsupported/)
I hope this will be fixed soon.
Title: Re: Internal DCI's of NetXMS server changed to UNSUPPORTED
Post by: tfines on April 19, 2020, 11:59:04 PM
Seeing the same thing on NetXMS server 3.2.380 on Windows.
Title: Re: Internal DCI's of NetXMS server changed to UNSUPPORTED
Post by: Filipp Sudanov on April 28, 2020, 01:26:53 AM
Thank you for reporting.
The ThreadPool DCIs are failing because you have only one SYNCER process configured (default setting) - in this case thread pool mechanisms are not used.
Server.Heap ones work only if server was compilled with jemalloc.

In coming 3.3. version out of the box templates were updated to fix these issues.