Server.AverageDCPollerQueueSize not supported

[mark99]

After updating to 2.2.14, the server node's DCC display now has the internal parameter Server.AverageDCPollerQueueSize showing as unsupported. That entry under the template DCC shows as enabled, but when looking at the server node DCC, it shows as unsupported.

This is a very small home environment, so there's only a single unclustered server node.

This parameter has always worked without any problems. No other parameters seem to be affected. No changes have been made either to this parameter or to this node. No other node is so affected. Any ideas?

Thanks!

UPDATE

After rebooting the server today, I got the following additional alarms:

[Minor] NetXMSServer Status of DCI 86 (Internal: Server.ThreadPool.Usage(SCHEDULER)) changed to UNSUPPORTED
[Minor] NetXMSServer Status of DCI 95 (Internal: Server.ThreadPool.LoadAverage(SCHEDULER,1)) changed to UNSUPPORTED
[Minor] NetXMSServer Status of DCI 96 (Internal: Server.ThreadPool.CurrSize(SCHEDULER)) changed to UNSUPPORTED
[Minor] NetXMSServer Status of DCI 97 (Internal: Server.ThreadPool.Load(SCHEDULER)) changed to UNSUPPORTED

I'm also unable to see the server node's agent config file through the workbench. I get a communications failure.

None of these issues were showing before I did a bare metal restore, updated PostgreSQL, then updated to NetXMS 2.2.14.

[victor]

Hi,

that could indicate that node representing NetXMS server is no longer considered to be local server. You can check that in server debug console - type command

show obj NetXMSServer

and check isLocalMgmt flag value. If this is the case try to find if new node was created to represent NetXMS server.

Best regards,
Victor

[mark99]

Hi Victor,

This is strange. All of the other nodes' agents can communicate with the server without any problems. The server's agent isn't seen by the core service, which I think is the reason for the errors I've seen. In the agent config file for the server, I've made sure that the server's correct IP address was in the MasterServers line, and I tried 127.0.0.1 and localhost, but no luck. I haven't added any nodes, so there wasn't an opportunity to get the server node confused. The issue seems to be that the server can't talk to the agent on the same machine. This is probably going to be something obscure: simple but not obvious (at least to me!).

[victor]

Try to start agent with debug level 6 or higher, and check what is going on with incoming connections. Make sure that agent logging is set to file.

Best regards,
Victor

[mark99]

Hi Victor,

I am embarrassed to report that this problem was actually caused by some overzealous antivirus software blocking the agent/server communications. This was not due to any issues with NetXMS!

Now I have to figure out how to tell the "Smart Firewall" to stop interfering with this legitimate traffic!

Thank you,

Mark