NetXMS Support Forum

Hello!

I'm still unable to reproduce your situation nor identify possible cause. Could you please change logging to file by placing


LogFile = C:\nxagentd.log


to agent's config, run nxagentd -D and send me nxagentd.log file?

Also, one more test for crash: try to uncomment winperf.nsm and add the following to agent's config:


*WinPerf
EnableDefaultCounters = no


will it crash as well?

Best regards,
Victor

Да, через параметр System.ServiceState(). Этот параметр обсуждался на форуме, может будет полезно:

https://www.netxms.org/forum/index.php/topic,42.0.html
https://www.netxms.org/forum/index.php/topic,166.0.html

Best regards,
Victor

This topic has been moved to Идеи и предложения по функциональности NetXMS.

https://www.netxms.org/forum/index.php?topic=383.0

Идея хорошая, согласен.

А crash dump присылали уже на [email protected]?

Uptime измеряется в секундах. При желании можно трансформировать в читаемую строку таким скриптом:


SecondsToUptime($1)


Но, конечно, тогда условия вроде "меньше" или "больше" уже поставить не получится.

Best regards,
Victor

Neskol'ko raz pitalsja povtorit' u sebja etu situaciju - bezuspeshno. Esli noda podnjalas' i alarm ushel, to sledujushij SYS_NODE_DOWN delaet normal'nij Outstanding alarm. A v event policy standartnie pravila obrabotki SYS_NODE_DOWN i SYS_NODE_UP? Esche vopros - a esli iz konsoli smotret' - situacija takaja-ze?

Best regards,
Victor

Vopros k tem kto ispol'zuet russkij Windows - kak vedet sebja agent? Est' li kakie-to specificheskie problemi? Osobenno interesujet winperf subagent - vozvraschaet li on parametri System.Uptime, System.ThreadCount, System.CPU.LoadAvg i System.CPU.Usage?

Best regards,
Victor

Currently it's not possible. However, since the next release you will be able to use scripts to form event message. Inside the script, you can access event parameters and do various string manipulations on them.

Best regards,
Victor

One more question: how counter names \System\System Up Time and \System\Threads looks in your localized Windows?

Best regards,
Victor

Hello!

What kind of acknowledgment you device need? If it can be done with some external command, you can do the following:

1. Create event from SNMP trap
2. In event processing policy, define an action for this event to call external command for trap acknowledgment.

Best regards,
Victor

Currently there are no automatic layer 2 topology, but I have this in plans.

Best regards,
Victor

Sorry for delay, I was quite busy Could you please do some additional tests?

1. Comment out winperf.nsm subagent - I suspect that it can be the cause of crash.
2. If agent service crashes without winperf.nsm, run nxagentd.exe from command line with -D switch - it will cause agent to log additional debug information.

Best regards,
Victor

Hi!

NPI file is just a reference to actual package file. You should have it as well in the same directory as NPI file. Open NPI with any text editor and see what package file is required.

Best regards,
Victor

Hello!

Second error is definitely a bug in MIB compiler, I'll fix it. I\m not sure about first error - it's quite strange ta have parenthesis as part of object name, I'll check if it's allowed by standard.
As a workaround, for first error you can change object name from ms-dhcp-MillisecondsPerPacket(Avg) to ms-dhcp-MillisecondsPerPacket, and delete entire INDEX line for second error.

Best regards,
Victor