NetXMS Support Forum

Только если использовать какую-то внешнюю утилиту для отсылки писем вместо встроенного SMTP клиента.

Hi,

the you have to set search base to the top of the tree, and filter out non-IT users in LDAP search filter. Filter to include only users from IT OUs could look like following (not tested):


(ou:dn:=Information Technology)


I took the OU name from log posted earlier: "CN=a1,OU=Information Technology,OU=Staff,OU=xxx1,DC=mycompany".

Here is more information on such filtering: http://help.globalscape.com/help/eft6/Advanced_LDAP_Filtering.htm.

Best regards,
Victor

Hi,

problem is that you set search base to group object itself, so NetXMS reads only that group object (you can see hint on this in line "Found entry count: 1" - it means that only one matching object was found). You have to set search base to OU=Information Technology,OU=Staff,OU=xxx1,DC=mycompany. If you want to import only users that are member of that group, you should control it with LDAP search filter.

Best regards,
Victor

Hi,

try to run server with debug level 6 and check what's in the log regarding active discovery.

Best regards,
Victor

Hi,

currently it's not possible. We have plans to add IPFIX/NetFlow support in 2.1.

Best regards,
Victor

Hi,

1.2.17 has few known LDAP bugs that was fixed in 2.0. I'm not sure though if that's one of those known bugs. If you can try 2.0-M4 (or wait for 2.0-M5 which will be available next week) it will be great.
Also, is is possible that LDAP server do not respond to requests from NetXMS server? This can be the reason of timeout on client connect.

Best regards,
Victor

В 2.0-M5 добавуил параметр агента File.FolderCount - аналогичен File.Count, только считает папки, а не файлы. Теперь получить кол-во папок новее одного дня можно так:

File.FolderCount(C:\Install,*,0,,-86400)

возможность использования File.Time.Change() похоже зависит от операционки - на Windows меняется после создания подпапки.

Отправил адрес в личку. Смогу заняться в понедельник-вторник думаю.

That actually make sense to interpret runtime error / abort in auto apply script as no action - otherwise small typo can cause mass remove of templates. I've made change in server logic - now only explicitly returned false will cause unbind - runtime errors will be interpreted as "no change". It will be included in 2.0-M5 release.

Best regards,
Victor

Hi,

it's a known issue, I plan to fix it in 2.0-M5 release.

Best regards,
Victor

Hi,

32 bit version of nxzlib.dll attached.

Best regards,
Victor

Hi,

you can disable built-in active discovery and create your own external script which will do network scan and then use nxshell to create node in NetXMS.

Best regards,
Victor

Можно поставить threshold "data collection error" на счетчик - он сработает если произойдет ошибка сбора данных.

Например такой скрипт:


x = 1;
y = null;

z = x / y;

println "z=" . z;


завершится с ошибкой:


Error 5 in line 4: Invalid operation with NULL value


добавляем try/catch:


x = 1;
y = null;

try
{
   z = x / y;
}
catch
{
   z = "ERROR CODE=" . $errorcode . "; LINE=" . $errorline . "; TEXT=" . $errortext;
}

println "z=" . z;


Скрипт отработает и выдаст


C:\Source\NetXMS\x64\debug>nxscript.exe test20.nxsl
NetXMS Scripting Host  Version 2.0-M5
Copyright (c) 2005-2015 Victor Kirhenshtein

z=ERROR CODE=5; LINE=6; TEXT=Error 5 in line 6: Invalid operation with NULL value

C:\Source\NetXMS\x64\debug>


Еще можно в письмо вставлять URL нужного дашборда.