NetXMS Support Forum

Hi,

I'm monitoring the states of Windows VMs with thresholds that trigger events.
The "OS_MAJOR_PROCESS_NOT_RUNNING" event is triggered with the event key "OS_PROCESS_NOT_RUNNING%i".

This normally works as intended, but sometimes the alarm doesn't resolve when the node leaves maintenance mode.
Attached are the event logs in .csv format, as well as some details on the individual events.

Why didn't the alarm resolve with "maintenance leave" (event 8769121)?
Both "task running" events still reference "maintenance enter" (event 8766568).
eventlog.csv
event_8769122.txt
event_8769123.txt
event_8768197.txt
event_8768198.txt     

Hello Alex,

you are right. My mistake was that I downloaded the wrong file, now it works as expected.

Thank you

Good Afternoon,

The Auto-link Nodes feature on the custom map type seems to have stopped working somewhere between the NetXMS server version 6.0.5 to 6.2.4. I can confirm it was working fine on 6.0.5 .

For example, trying to link two nodes together on a Layer 2 topology map works as intended, but when trying the exact same on a custom map type it does not link them together anymore.

Furthermore existing maps on which I already used the Auto-link nodes feature retain the links,
although when removing them and replacing them with new auto-links, it also doesn't work.

Has anyone else encountered this or even know of a potential fix / workaround?

Yes, it's already fixed in the code and will be in 6.2.6, which isn't released yet: https://github.com/netxms/netxms/issues/3656. Only the agent on the Windows machine needs to be updated.

Hi,

Still not fixed - nothing in 6.2.4 or 6.2.5 changed this part of the agent. Remaining problem is now tracked in https://github.com/netxms/netxms/issues/3621 (#3137 was closed after the split).

To move it forward, please post:

• exact warning lines from the server log - package name in them shows which part of the agent produces the duplicates
• nxagentd log with debug level 6 for tag "winnt", covering a full logon and logoff
• System.InstalledProducts table taken twice - once with a user logged on, once without
• whether these are RDS/terminal servers, and whether profiles are roaming, FSLogix or UPD

Hi Alex,

thanks for the infos. The checked EXE is unfortunately not a service. So i give the WMI thing a try...

Do you patch this in the V6.2.6 ?

Greetings
Marco

PS: As allways: Great Support... Many thanks... 

Hi Marco,

Yes, this is a bug in the Windows agent: https://github.com/netxms/netxms/issues/3656

Process.Count never sees the most recently started process on the machine. So it returns 0 while your EXE is the newest running process, and goes back to 1 as soon as something else starts after it - that's why it looks random. It's not specific to 6.2, so downgrading won't help. Process.CountEx and the other Process.* metrics have the same problem.

Until it's fixed: if the process runs as a service, monitor the service instead (service name, not display name; 0 means running):
System.ServiceState(ServiceName)
Otherwise, with the WMI subagent loaded (SubAgent = wmi.nsm in nxagentd.conf), this returns the real count:
WMI.Query(root\cimv2,"SELECT ProcessId FROM Win32_Process WHERE Name='yourapp.exe'",%%count%%)

Hello @all,

we are running NetXMS at V6.2.5. We notice since the last versions, that process.count returns 0 even the checked EXE is running.

Have anyone else this behaviour to?

Greetings
Marco

We have upgraded to netxms server 6.2.5 and netxms windows x64 agent to 6.2.5 and still seeing duplicate packages and also the warnings in the netxms server logs.

Great job, thanks everyone!

Alessio.