NetXMS Support Forum

Quote from: sabonez on October 05, 2012, 09:14:21 AM
СМС-ки вроде в UCS-2.

SMS с русскими буквами можно посылать только в PDU режиме насколько я понимаю. Кроме того, сам сервер должен работать в UNICODE или code page должен быть выставлен в CP-1251.

Quote from: sabonez on October 05, 2012, 09:14:21 AM
База у меня в 1251, с utf-8 почему-то java-console под вендой не задружилась - резала русские имена. Если это как-то лечится, может есть смысл конвертнуть базу в UTF?

Здесь скорее проблема с самим сервером, а не с базой. Проверьте что параметр CodePage в netxmsd.cond выставлен в CP1251, или попробуйте UNICODE сборку сервера.

Я сталкивался с проблемами со скоростью порта. Generic SMS драйвер по умолчанию пытается работать на 9600. Попробуйте поставить скорость побольше - 38400 или выше, и проверьте что в настройках самого виртуального порта тоже эта скорость стоит (это для Windows актуально, про Linux не знаю).

Quote from: SKYnv on October 03, 2012, 08:13:43 AM
это нормальная работа?

Quotenetxmsd: sh po
PT  TIME                   STATE
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:03:01   poll: M_Uz_Zarech_16 [5464] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:02:59   wait
S   03/Oct/2012 11:01:10   poll: 192.168.1.33 [7713] - wait for lock
S   03/Oct/2012 11:00:35   poll: 192.168.1.33 [7683] - wait for lock
S   03/Oct/2012 11:03:16   wait
S   03/Oct/2012 11:02:50   wait
S   03/Oct/2012 11:00:40   poll: 192.168.1.33 [7701] - wait for lock
S   03/Oct/2012 11:00:15   poll: 192.168.1.33 [7695] - wait for lock
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7710] - wait for lock
S   03/Oct/2012 11:01:20   poll: 192.168.1.32 [7722] - wait for lock
S   03/Oct/2012 11:01:20   poll: 192.168.1.32 [7728] - wait for lock
S   03/Oct/2012 11:01:25   poll: 10.255.141.201 [114] - wait for lock
S   03/Oct/2012 11:00:55   poll: 192.168.1.33 [7719] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:00:35   poll: 192.168.1.33 [7731] - wait for lock
S   03/Oct/2012 11:02:58   wait
S   03/Oct/2012 11:02:51   wait
S   03/Oct/2012 11:00:45   poll: 192.168.1.32 [7692] - wait for lock
S   03/Oct/2012 11:03:12   wait
S   03/Oct/2012 11:03:11   wait
S   03/Oct/2012 11:03:10   wait
S   03/Oct/2012 11:00:40   poll: 192.168.1.33 [7725] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:01:10   poll: 192.168.1.32 [7698] - wait for lock
S   03/Oct/2012 11:01:05   poll: 192.168.1.32 [7680] - wait for lock
S   03/Oct/2012 11:02:55   wait
S   03/Oct/2012 11:00:45   poll: 192.168.1.33 [7707] - wait for lock
S   03/Oct/2012 11:02:40   wait
S   03/Oct/2012 11:01:05   poll: 192.168.1.32 [7704] - wait for lock
S   03/Oct/2012 11:00:45   poll: 192.168.1.33 [7677] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:02:41   wait
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7716] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:03:06   wait
S   03/Oct/2012 11:03:10   wait
S   03/Oct/2012 11:00:55   poll: 192.168.1.33 [7689] - wait for lock
S   03/Oct/2012 11:03:01   wait
S   03/Oct/2012 11:03:01   wait
S   03/Oct/2012 11:03:16   wait
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7686] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:03:08   wait
S   03/Oct/2012 11:02:45   wait
S   03/Oct/2012 11:03:01   poll: 192.168.1.146 [5696] - wait for lock
S   03/Oct/2012 11:02:48   wait
S   03/Oct/2012 11:03:05   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7704] - hook
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7695] - hook
C   03/Oct/2012 10:59:51   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7683] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7719] - hook
C   03/Oct/2012 11:02:22   poll: 10.255.141.201 [114] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.32 [7722] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7686] - hook
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:03:12   wait
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7731] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7710] - hook
C   03/Oct/2012 10:59:30   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7698] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7707] - hook
C   03/Oct/2012 11:02:48   wait
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:02:00   wait
C   03/Oct/2012 11:01:42   poll: 192.168.1.32 [7716] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7689] - hook
C   03/Oct/2012 11:01:42   poll: 192.168.1.33 [7713] - hook
C   03/Oct/2012 11:02:24   wait
C   03/Oct/2012 11:01:32   poll: 192.168.1.33 [7677] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.32 [7728] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7725] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7701] - hook
C   03/Oct/2012 11:01:36   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7680] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7692] - hook
R   03/Oct/2012 11:00:50   wait
R   03/Oct/2012 11:00:50   wait
R   03/Oct/2012 11:02:41   wait
...
T   03/Oct/2012 11:02:46   wait
T   03/Oct/2012 11:03:12   wait
T   03/Oct/2012 11:02:05   poll: 192.168.1.146 [5696]
T   03/Oct/2012 11:02:15   poll: 192.168.1.33 [7677]
T   03/Oct/2012 11:02:24   wait
T   03/Oct/2012 11:02:05   poll: M_Uz_Zarech_16 [5464]
T   03/Oct/2012 11:03:06   poll: 192.168.1.32 [7686]
T   03/Oct/2012 11:02:41   poll: 192.168.1.32 [7680]
T   03/Oct/2012 11:02:48   wait
T   03/Oct/2012 11:02:51   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
A   03/Oct/2012 10:27:21   check

учитывая что ноды 1.32 1.33 были удалены сутки назад.

Нет, поведение ненормальное. Похоже, что зависли hook-скрипты по каким-то причинам. Сейчас думаю без рестарта сервера уже ситуация не поправится.

Quote from: SKYnv on October 01, 2012, 02:56:52 PM
постоянно сыпляться

QuoteSql query failed commands out of sync you can't run this command now

поиск выдал примерные причины
http://www.mysql.ru/docs/man/Commands_out_of_sync.html
http://habrahabr.ru/post/21326/

А какие именно запросы?

Quote from: SKYnv on October 02, 2012, 12:32:09 PM
на вики присутствует

QuoteNumberOfBusinessServicePollers     A number of threads responsible for business service (SLA) monitoring.     10     Yes

в конфиге создающимся по умолчанию отсутствует.

Спасибо, поправил.

Sorry, I completely forgot about it Now added as an issue to bug tracker (https://www.radensolutions.com/chiliproject/issues/128) - will try to implement it in few days.

Best regards,
Victor

Hi!

Few clarifications:

1. There are no difference between ExternalParameter and ExternalParameterShellExec on UNIX/Linux. They only behave differently on Windows.

2. There are two timeouts that must be taken into consideration:
a) ExecTimeout on agent - timeout for executing external program
b) AgentCommandTimeout on server - timeout for any command sent from server to client

In general AgentCommandTimeout must be greater or equal to ExecTimeout.

Also, if you have couple of external parameters with possible long collection time, you may create wrapper script to get them all at once and use it as external parameters provider - see wiki for details: http://wiki.netxms.org/wiki/ExternalParametersProvider.

Best regards,
Victor

Multipliers on charts implemented in 1.2.4.

Best regards,
Victor

Hi!

Try to change speed in port's settings. Generic driver uses 9600 by default, and I've seen cases where GSM modem was not working on speed below 38400. Make sure that speed in port settings match configured port speed in SMSDrvConfig parameter.

Best regards,
Victor

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

Hi!

I incorporate patch into the trunk. Thank you!

Best regards,
Victor

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

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

Poprobuju povtorit' u sebja segodnja vecherom.

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