NetXMS Support Forum

Hi Stan,

Thanks for pointing me in the right direction. I didn't know it imported anything from local files 

As for the crashing, i'm not sure. I get the occasional error in the event log where NetXMS is trying to process a certain DCI or script but none of those would have changed since 2.8. I will live with it for the moment to see if anyone else flags up a similar issue / bug.

Every couple of days, the NetXMS Core service will crash and create a dump file.
I have set the service to restart on crash so the downtime is minimal but one interesting thing that happens when it comes back up is that the "Windows" template under Templates -> Operating Systems automatically applies to all nodes that are running the windows agent.

I have disabled the auto-apply feature and removed the template from all nodes and that returns everything to normal, but next time the server crashes / restarts then that template will re-enable the auto-apply rule and apply itself to all applicable nodes again. 

Has anyone else got a similar problem, or know how to stop it re-enabling the auto-apply rule?

I have attached the info file from the latest crash dump if anyone is interested.
NetXMS 2.1-RELEASE on Windows Server 2012 R2.

I have a remote node that I need to monitor.
Unfortunately I am unable to ping the node due to firewall restrictions at the remote site.
I have seen this option (in the title) on the Polling page of the node properties, and i'm hoping that this will make the server try and connect over port 4700 instead of pinging it until it shows as available.
However if I check the box, the server will just assume the node is always down and not even try to connect.

Does anyone have any ideas?

So I managed to get a connection, by using the FQDN instead of static IP in the node's properties.

Strange.

As the title says really.
I have a working agent (AGENT1) at a remote site, with EnableProxy = yes & EnableSNMPProxy = yes. Zoning is enabled on the server and the node I am trying to get connected (AGENT2) is inside its own zone, with the working agent set as all of the proxies.

When I try to poll the status of AGENT2, I get this in the console...

Quote[07.10.2016 10:27:29] **** Poll request sent to server ****
[07.10.2016 10:27:29] Poll request accepted
[07.10.2016 10:27:29] Starting status poll for node AGENT2
[07.10.2016 10:27:29]    Starting status poll on interface unknown
[07.10.2016 10:27:29]       Current interface status is UNKNOWN
[07.10.2016 10:27:29]       Starting ICMP ping via proxy
[07.10.2016 10:27:30]       Interface is UNKNOWN for 198 polls (1 poll required for status change)
[07.10.2016 10:27:30]       Interface status after poll is UNKNOWN
[07.10.2016 10:27:30]    Finished status poll on interface unknown
[07.10.2016 10:27:30] Node is still unreachable
[07.10.2016 10:27:30] Finished status poll for node AGENT2
[07.10.2016 10:27:30] Node status after poll is CRITICAL
[07.10.2016 10:27:30] **** Poll completed successfully ****

Started nxagentd on AGENT2 in debug mode, but nothing happens after saying press ESC to exit.
Started nxagentd on AGENT1 in debug mode shows activity. When I poll the status of AGENT2, I see it trying to ping AGENT2...

QuoteRequesting parameter "Icmp.Ping(<AGENT2 IP Address>)"

but responding almost instantly with

QuoteGetParameterValue(): result is 404 (UNKNOWN_PARAMETER)

Any ideas why this is happening, or what I may be doing wrong?
Cheers