NetXMS Support Forum

Hi,

can you create process dump when agent start using 100% CPU and send it to me?

Best regards,
Victor

Hi!

1) You can use actions with timers. For example, execute action on node down event with timer set to 5 minutes, and cancel this timer on "node up" event. If node will recover within 5 minute interval, timer will be cancelled and action never executed.

2) Yes, diff will be correct method in this case.

Best regards,
Victor
 

Fix is already made, I plan to made release 2.2.13 within a week.

Best regards,
Victor

There are no standard way for doing that. If there is only one user session you can uninstall agent service and add nxagentd.exe to autorun so it will start within user session. Or you can use combined approach - leave agent as a service, run external subagent via autorun and define actions in this subagent.

Best regards,
Victor

Hi,

I don't see any logs attached.

Best regards,
Victor

There was packaging error in web UI installer, but it was replaced shortly after release. When did you download it?

Best regards,
Victor

Hi,

that's actually looks like a bug. If alarm is already resolved system should not change it's state. We will fix it for next release.

Best regards,
Victor

Hi,

I suggest using script threshold. Script could be following:


!($1 like "Online") && !($1 like "Ready")


Best regards,
Victor

Hi,

most likely database client library is not installed or not in the path. Please provide more details of your setup - OS, database, full netxmsd.conf and full output of nxdbmgr.

Best regards,
Victor

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