NetXMS Support Forum

Здесь понадобится два скрипта. Делается примерно так:

1. Делаем список HTTPS.Certificates

ExternalList = HTTPS.Certificates:script1.cmd


Скрипт должен выдавать список сертификатов, каждый в своей строчке.

2. Изменяем параметр HTTPS.CertificateExpireDate чтобы он принимал имя сертификата:

ExternalParameter = HTTPS.CertificateExpireDate(*): powershell.exe -file "\\server\Scripts\test.ps1" -certname $1


Насколько я знаю power shell можно будет в скрипте получить имя сертификата в переменной certname. Дальше в скрипте все как сейчас.

3. Делаем DCI на сервере:
Параметр

HTTPS.CertificateExpireDate({instance})


Instance discovery method: agent list
Имя списка: HTTPS.Certificates

Try to start agent with debug level 6 or higher, and check what is going on with incoming connections. Make sure that agent logging is set to file.

Best regards,
Victor

Похоже это следствие ошибки в ReadPersistentStorage - если записи с заданным ключом нет, то возвращается пустая строка, а не NULL. Правильным вариантом кода будет

ReadPersistentStorage($event->dciId . "_0x" . right(d2x($node->id), 8, "0"));

Предварительно можно еще проверить что $event->dciId не NULL.

Parameter itself is ok, there is 1023 character limit. Problem is with instance value where actual OID will not fit. It is fairly easy to extend instance length limit to 1023 characters as well, I can do that for next release.

Best regards,
Victor

А точно работает? ReadPersistentStorage на делает подстановку, т.е. будет искаться ключ %<dciId>_%i, а не скажем 127_313.

Можно помимо генерации аларма делать запись с таким-же ключом в persistent storage, и в правиле отсылки почты по SYS_THRESHOLD_REARMED проверять наличие такого ключа, и только если он есть выполнять отсылку.

Try to cancel configuration wizard and run initialization manually (using nxdbmgr init) - it may provide more diagnostic information. You can also try to create user and database manually and choose "use existing database" option in configuration wizard.

Best regards,
Victor

Hi,

make sure that if you are using Windows authentication you have used * as login name and current user has access rights to the database, or if you are using SQL authentication (using login and password) that mixed mode authentication is enabled on SQL Server. Another possible issue could be using IP address (event loopback) with TCP/IP connector not enabled on SQL Server side.

Best regards,
Victor

Limits are 1023 characters for DCI parameter name and 255 characters for instance name.

Best regards,
Victor

Hi,

that could indicate that node representing NetXMS server is no longer considered to be local server. You can check that in server debug console - type command

show obj NetXMSServer

and check isLocalMgmt flag value. If this is the case try to find if new node was created to represent NetXMS server.

Best regards,
Victor

Hi,

currently it's not possible. I've added feature request for ability to pass extra parameters to generated event: https://track.radensolutions.com/issue/NX-1643

Best regards,
Victor

Hi,

this will require changes in NetXMS SNMP code. I've added feature request for that: https://track.radensolutions.com/issue/NX-1642

Best regards,
Victor

Hi,

yes, this is known issue fixed in 2.2.13 (crash because of improperly loaded scheduled task).

Best regards,
Victor

Hi,

yes, there is a bug in server (buffer overflow). Just fixed it with commit 0b33902b23047427b5d15ca9b70c75ed5571affa. You can rebuild server from source or wait for release 2.2.15 with the fix.

Best regards,
Victor

Hi,

log file does not suggest that service is not started. Try to run with debug level 9. If netxmsd process disappears after start, try to run it under gdb and provide stack trace (output of bt command in gdb).

Best regards,
Victor