Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#5026
General Support / Re: NXSL script help
October 01, 2012, 06:41:14 PM
Hi!

Quote from: tivanni on October 01, 2012, 02:18:30 PM
when I add a filtering script to the event processing policy, where i can found the output of the print/println command?
If i add a print or a println command to the filter script, when the event occuor i can't find the output in the remote console server or in the server console or in other way.

You should use trace() function to write messages to server's log.

Quote from: tivanni on October 01, 2012, 02:18:30 PM
Another questions...in the filtering script of event processing policy, can i put directly the code?Or, have I to add the declaration of the main (sub main(){etc )

Yes, you can write code directly. Defining main() is not necessary. Also, the following code is also valid:


trace(0, "main() starts here");

sub someFunction()
{
}

trace(0, "main() continues here");


Quote from: tivanni on October 01, 2012, 02:18:30 PM
I have to create a filter script that send the alarm's mail for an interface down for only specific interface...
I tried to insert in the event processing police as source the specific interface, but did'nt work; so i use as source the switch and i wanna to add a filter script that select for which interface the alarm's mail have to start. Any suggestion?

Source of interface down event is the node. You can filter events using script by interface name or index. For example, to pass SYS_IF_DOWN events only for interface named "eth2", you can use the following script:


return $2 == "eth2";


We use $2 here because interface name passed as second parameter with SYS_IF_DOWN event. You can see this from event description:

Generated when interface goes down.
Please note that source of event is node, not an interface itself.
Parameters:
  1) Interface object ID
  2) Interface name
  3) Interface IP address
  4) Interface netmask
  5) Interface index

Best regards,
Victor
#5027
General / Re: Agent.Ping: StdDeviation
September 28, 2012, 07:29:58 PM
Hi!

I incorporate patch into the trunk. Thank you!

Best regards,
Victor
#5028
General Support / Re: Raspberry Pi - Wallboard Deployment
September 28, 2012, 01:55:03 PM
Hi!

I have added command line options to nxmc.exe to allow automatic connect. New options are:

-auto - connect automatically
-server=address - set server address
-login=login_name - set login
-password=password - set password

These changes will be included in 1.2.4 release. If you need them urgently, contact me.

Best regards,
Victor
#5029
Most likely instance will not be 0 in that case, but 1, 2, 3 or anything else. You can use MIB explorer to find exact OIDs - just find .1.3.6.1.4.1.2021.10.1.3 in MIB tree, right-click on it, select "Walk", and see the results.

Best regards,
Victor
#5030
Общие вопросы / Re: Баги 1.2.3
September 26, 2012, 06:45:28 PM
Poprobuju povtorit' u sebja segodnja vecherom.
#5031
Hi!

ICMP response time measured in milliseconds. I doubt that it is possible or useable to use higher precision for that.

I'm not sure about NagVis, never work with that. Depending on how it collects data it could be possible. However, NetXMS has it's own network map implementation, so why do you need to integrate it with NagVis?

Best regards,
Victor
#5032
Hi!

Yes, there was an error in the makefile for odbcquery subagent. Current svn trunk contains fixed version.

Best regards,
Victor
#5033
Hi!

Did you install agent from deb package or by compiling source? What is the output of

ldd /usr/lib/libnsm_odbcquery.so

?

Best regards,
Victor
#5034
Конструкция вида


uint32(value);


смысла не имеет - возвращается преобразованное значение, которое выбрасывается. Тогда надо писать так:


value = uint32(value);


По сути type cast можно рассматривать как специальные функции - они принимают одно значение и возвращают преобразованное значение.
#5035
Действительно, uint32(x) делал cast в int32. Опять copy/paste :)

Пре-инкремент у меня работает как надо - я это уже исправлял. В аттаче свежесобранный интерпретатор для 32 битного Windows.
#5036
Hi!

winperf and wmi are part of agent installation. You should just load them in nxagentd.conf.

Automatic network maps should be available in 1.2.4 release, somewhere in October.

Best regards,
Victor
#5037
Hi!

Check that libsensors4-dev package ins installed, and then run configure again.

Best regards,
Victor
#5038
Quote from: SKYnv on September 22, 2012, 07:03:27 PM
1) пре инкремент
работает как декремент

Исправил.

Quote from: SKYnv on September 22, 2012, 07:03:27 PM
2) uint32 conversion
не работает данная конвертация

А можно пример скрипта?

Quote from: SKYnv on September 22, 2012, 07:03:27 PM
3) парсер и "//"
если в конце скрипта добавить комментарий с помощью
//
то парсер выдаст ошибку
Quotesyntax error, unexpected '/', expecting $end
хотя на
/* В конце*/
парсер реагирует нормально

Исправил.

Quote from: SKYnv on September 22, 2012, 07:03:27 PM
большой скрипт не напишешь, постоянно Stack underflow...

Это скорее всего следствие одной из ошибок. Можете привести пример скрипта, который дает stack underflow?
#5039
Yes, it was broken. I uploaded it again, you can try again now.

Best regards,
Victor
#5040
Hi!

I have fixed some of the problems causing "No context available outside of the request service lifecycle" errors. Please try updated war file: https://www.netxms.org/download/rc/nxmc-1.2.3.2.war.

Best regards,
Victor