NetXMS Support Forum

Hi!

I think it should not be very hard. I'll try to create TCHAR version of opendir/readdir/closedir today. I'll notify you when they will be done.

Best regards,
Victor

Yes, that means that you are running 1.0.8. I'll check this.

Best regards,
Victor

Hi!

1. Looks like you need to create filtering script to perform additional filtering when creating alarms from traps. If you can tell me how important traps can be distinguished from non-important (probably different message text or error code, etc.), I can help with filtering script creation.

2. Most likely you have incorrectly configured alarm key. Ensure that it includes unique node ID (macro %i), or make it empty to disable alarm duplication checking at all.

Best regards,
Victor

Hi!

You can define new parameters in agent implemented by external script, and then collect these parameters as usual. You can use any external program as parameter handler, and first line of the command's output will be considered as parameter's value. For example, if you have script myscript.vbs and wish to define new parameter AppUsage, you can add the following line to nxagentd.conf:

ExternalParameter = AppUsage:cscript.exe //B //Nologo myscript.vbs

Restart agent, and you will have new parameter AppUsage available for collection.

Best regards,
Victor

Hi!

What version of NetXMS server you are using? There was a bug with accessing situation attributes using -> operator, but it was fixed in 1.0.8.

Best regards,
Victor

For SQLite, parameter DBName is database file name. So, if you specify just "netxms", it is relative to current directory. If you run netxmsd from different directory, it will pick wrong file. You should specify fully qualified file name in DBName.

Best regards,
Victor

Hi!

There are two different problems. One is a bug in console - it does not show attributes under instances even if they exist. But your main problem is that situation attributes are read only, i.e. you cannot do s->counter = s->counter+1; in your script. I will do something to simplify that, but currently you have only two relatively complicated workarounds:

1. In matching script in the rule, set variable CUSTOM_MESSAGE to new counter value, and in "Situation" column, set attribute counter to value "%M" (without quotes).
2. Set counter's value to %{your_script}, and create script in the library which will increase the counter. For example, you can use %{IncreaseFaxCounter} and create script named IncreaseFaxCounter in script library like this:


s = FindSituation("Multiple FAXes printed", "FaxFinder");
if (s != NULL)
    return int32(s->counter) + 1;
return 1;


It will return either increased counter value or 1 if counter was not set before.

In any case you will have two rules - one for updating counter and second to match required counter value and perform required actions. You will also need to reset counter somewhere.

Best regards,
Victor

Looks like we have a lot of Solaris problems Please try to replace src/server/core/node.cpp with attached one and recompile server. If this will not help, please send me a core file generated after crash.

Best regards,
Victor

Hi!

Maybe I'm not understand correctly, but what do you mean by "install" on Solaris or RHEL? If you are installing NetXMS server on UNIX from sources (using make install), you are supposed to create netxmsd.conf and initialize database manually, "make install" command will not do that. Or you experience this problem even after running "nxdbmgr init" for the first time?

Best regards,
Victor

Logwatch subagent can work with changing log file names. If agent detect file name change, it reads new log file from the beginning. Also, it detects file overwrite, so if file was overwritten, it also will be scanned from the beginning. How do you log files named?

Regarding question 2 - it is application specific. I don't think there should be any performance impact. Also, there should be no problem on UNIX to read file being actively written, but it can cause application misbehavior on Windows. The only way to know it for sure is to test it.

Best regards,
Victor

Hi!

You can add additional parameters to agent using ExternalParameter config file option. For example, you can add to nxagentd.conf on some node


ExternalParameter = WebVersion:wget -qO- https://www.netxms.org/download | perl -e 'while(<>) { chomp $$_; if ($$_ =~ /stable version is ([0-9\.]+)\,/) { print "$$1\n"; } }'


After that, agent will provide additional parameter named WebVersion. You can get value of this parameter by creating new DCI on this node, and create thresholds to detect value changes.

Best regards,
Victor

Hi!

You can safely ignore them. It's a side effect of applying system templates. I'll fix it in next release.

Best regards,
Victor

Добрый день!

Пока по прежнему нет поддержки перекрывающихся IP Буду делать в 1.1.x ветке.

Стандартных средств для этого нет. Можно написать простенькую программку на С или Java, которая будет через API подключаться к серверу и забирать данные в локальный файл.

Проблема в том, что NetXMS рассматривает тип OCTET STRING как текст, что не всегда правильно. snmpwalk проверяет строку на наличие непечатаемых символов, и если они есть, печатает всю строку как Hex-String. Я думаю в настройках SNMP трапов добавить опцию возвращать результат как hex string, тогда дальше можно будет сделать необходиимую обработку скриптами.