NetXMS Support Forum

Hi!

Do you have a core dump? If not, could you run netxmsd under gdb and when it crashes, issue command bt and provide it's output?

Best regards,
Victor

No, server only tries to connect to port 4700 during discovery. I've registered feature request for providing list of custom agent ports for discovery: https://track.radensolutions.com/issue/NX-1560

Best regards,
Victor

This is caused by housekeeper re-applying templates. This was added to automatically fix issues when not all DCIs were applied or updated correctly or was accidentally deleted (had those issues in few big deployments). The problem here is that template re-apply also resets DCI status to "active", which on next data collection run changes to "unsupported" and causes SYS_DCI_UNSUPPORTED event generation. Correct approach would be to leave unsupported DCIs in unsupported state. We will fix it before next release.

Best regards,
Victor

Hi,

you can add

Action = name:command

to nxagentd.conf and then execute this action either via server action from event processing policy or as object tool.

Best regards,
Victor

Hi,

you should create new zone (under Entire Network), set your Windows 10 node as zone proxy, and then create nods for each SNMP device you want to monitor in that new zone.

Best regards,
Victor

Hi,

did you give access to objects to grafana user?

Best regards,
Victor

Ответил в английской ветке: https://www.netxms.org/forum/configuration/server-and-agents-are-separated-by-nat/msg25297/#msg25297

Hi,

Geolocation is an immutable object, so you have to create new object when you need different location. NetObj and derived classes are also immutable, so you have to use NXCObjectModificationData class and session.modifyObject method. Working example for getting and setting geo location for node:


from org.netxms.base import GeoLocation

node = session.findObjectByName("netxms")
print node.getGeolocation()
md = NXCObjectModificationData(node.getObjectId())
md.setGeolocation(GeoLocation(11.0, 22.0))
session.modifyObject(md)


Best regards,
Victor

Currently no. We have a feature request for that.

Best regards,
Victor

Hi,

looks like in your setup you need agents connecting to server. In NetXMS default configuration is when server connects to agents. Reverse configuration called "agent tunnel". You have to configure server for accepting connections from agents: https://www.netxms.org/documentation/adminguide/server-management.html#server-configuration-for-agent-to-server-connection-tunnel-connection.

Best regards,
Victor

Hi,

you can only change it individually for each node. On agent side you have to add

ListenPort = nnn

to nxagentd.conf and on server side you should enter same port number in node properties Communication / Agent.

Best regards,
Victor

Hi,

replace <agent> tag with <core>. Also, it is not mandatory to use XMS format in policy - you can use same key=value format as in nxagentd.conf.

Best regards,
Victor

This version is very old. I definitely recommend upgrade to 2.2.12 first. We have fixed lot of issues, including internal locks and performance issues.

Best regards,
Victor

Hi,

this points to some internal locks being held for prolonged period. What version you are using, on what OS? Can you show event log for NetXMS server node?

Best regards,
Victor

Update: I likely found the reason for this error in numbering. Next release should show it correctly.

Best regards,
Victor