NetXMS Support Forum

Hi!

Scripting slowly moves to more and more areas of NetXMS I agree that creating and binding objects from scripts is a very good idea. I'm not sure, however, that auto bind script is the best place to create additional objects. For network discovery purposes, additional hook will be better. For example, it can be done that way that for each newly added node system executes some script from library. Or take more generic approach, and allow script execution as action in event processing policy - that way you will be able to execute your script on each SYS_NODE_ADDED event, as well as do many other things for other events.

Best regards,
Victor

Hi!

For syslog-based events to be generated, host which is source of the event must be registered as node in NetXMS. Also, I suppose you just omit <parser> tag from posted config - <rules> must be wrapped in it.

Best regards,
Victor

Ошибка в названии счетчика - должно быть

Counter = Active Remote Delivery Queue Length:"\MSExchangeTransport Queues(_total)\Active Remote Delivery Queue Length":60:A:INT:SMTP Active Remote Delivery Queue Length

MSExcahngeTransport  ->  MSExchangeTransport

Я сам это заметил только минут через 10 экспериментов

Hi!

jsut check it on my machine, and it looks like cscript suppresses output of WScript.Echo in batch mode, so agent cannot get the result. Changing

ExternalParameter = MyParameter:c:\windows\system32\cscript.exe //B //Nologo "c:\MyScript\myscript.vbs"

to

ExternalParameter = MyParameter:c:\windows\system32\cscript.exe //Nologo "c:\MyScript\myscript.vbs"

gives correct result for MyParameter.

Best regards,
Victor

Yes, or any value less than that - you can set it to 1 second for example. On each DCI poll if repeat event is set, server checks if time passed from previous event is longer than given interval, and if yes, generates new event. So, setting this to any value less than poll interval will cause new event to be generated at each poll.

Best regards,
Victor

Hi!

By default, new event is fired only once, when threshold's condition comes from false to true. If you wish to fire event on each check, you should turn on "repeat event" and set repeat interval less or equal to polling interval.

Best regards,
Victor

Hi all!

NetXMS version 1.0.10 is released. It's a bugfix version which should fix most of the network discovery problems in 1.0.9 along with few other issues. Changes from previous release:

- Network discovery improved
- Added VRRP support
- Added new object tools type: server command
- New MIBs added: VRRP-MIB
- Fixed issues: #320, #321, #322

Best regards,
Victor

Hi!

Currently you cannot execute tool on an alarm - you can call object tool, but server will not pass alarm's data to it. It's a good idea to have an "alarm tools" as well - I'll add this as feature request. It should be relatively easy to implement based on object tools - just add few more macros.

Best regards,
Victor

Hi!

Question about debian packages to experts: currently, my postrm script looks like following:


#!/bin/sh

if test "x$1" = "xpurge"; then
        rm -f /etc/nxagentd.conf
        rm -f /etc/nxagentd.conf.backup
        rm -f /etc/nxagentd.conf.sample
fi


It supposed to remove configuration files only when package uninstalled completely. However, during upgrade configuration files also got removed. What I am doing wrong?

Best regards,
Victor

Hi!

That's very strange, because German characters should be supported even by latin1 (ISO 8859-1) encoding. On what platform you are running NetXMS server and what database you are using?

Best regards,
Victor

No. But why you need that?

When you configure DCI to receive values via nxpush, you should set it's "Origin" attribute to "Push Agent", like on attached screenshot.

Best regards,
Victor

Hi!

Command line options are case-sensitive, so you should use -P instead of -p for giving password.

Best regards,
Victor

Hi!

The problem is following: you generate event SYS_THRESHOLD_REACHED when you cross threshold. This event has sverity WARNING. Then, you have the rule in event processing policy, which has two filtering conditions: if event is either SYS_THRESHOLD_REACHED or DC_HIGH_CPU_UTIL AND event's severity is CRITICAL, then generate alarm. Your event will never pass through this filter, because it has severity WARNING. Also, your custom event - CPU_USAGE - is not used at all.

You should do consistent config, for example as following:

1. In threshold, set event to DC_HIGH_CPU_UTIL
2. In event processing policy, leave "severity" column as "any", and leave only DC_HIGH_CPU_UTIL in "event" column
3. Optionally, change alarm text to %m, if you wish to have alarm text to be the same as event's message

Best regards,
Victor

Hi!

Most likely server was unable to save generated key file. By default it will try to save it under /usr/share/netxms. Check that this location is writeable by server process.

Best regards,
Victor