NetXMS Support Forum

Hi,

that's definitely a bug, we will check it.

Best regards,
Victor

Hi,

it looks like a bug (likely related to handling 64 bit integers), but we didn't have time to check it yet. Somebody from the team will take a look at it shortly. You may also register issue in out tracker - that will help not forget about this issue.

Best regards,
Victor

Hi,

make sure that netxmsd is not running, then run

nxdbmgr unlock

to remove database lock.

Best regards,
Victor

Hi,

yes, idea is that you add this attribute on each node where default threshold value should be overridden. You cannot exclude certain DCIs from being applied as part of template.

Best regards,
Victor

Hi,

that's quite unusual behavior for SNMP agent to return error on whole packet due to one invalid OID, but server definitely should be modified to handle such response correctly. Is it possible to provide us remote access to one such device for debugging? If not, could you provide full packet capture (output of tcpdump -w)?

Best regards,
Victor

Hi,

do you see correct value in "Last values"? Do you have data type for DCI set to 64 bit integer?

Best regards,
Victor

Hi,

please check if there is any errors logged in UI log (usually it is in $HOME/.nxmc/data/.metadata/.log).

Best regards,
Victor

Hi,

we are using libtre as regexp engine, their regexp syntax is described here: https://laurikari.net/tre/documentation/regex-syntax/.

There are two options for testing regexps and parsers:

1. Create simple NXSL script like below:

if ($2 match $1)
{
println "Matched";
println "  CG1 = " . $1;
println "  CG2 = " . $2;
println "  CG3 = " . $3;
println "  CG4 = " . $4;
println "  CG5 = " . $5;
}
else
{
println "Not matched";
}


and run it from command line:

victor@hp8570w ~/tmp $ /opt/netxms/bin/nxscript regex.nxsl 'Error\s(.*)' 'Error 44'
NetXMS Scripting Host  Version 3.0.1690
Copyright (c) 2005-2018 Victor Kirhenshtein

Matched
  CG1 = 44
  CG2 = Error 44
  CG3 =
  CG4 =
  CG5 =
victor@hp8570w ~/tmp $


2. Use nxlptest tool (I'm not sure though if it is included into deb packages). It allows you to run specific log parser from command line overriding trace level and file name specified in the parser. For example, if I want to test parser on my syslog I can do it like this:

/opt/netxms/bin/nxlptest -D9 -t9 -f /tmp/syslog /opt/netxms/etc/syslog_parser.xml

It will run parser from /opt/netxms/etc/syslog_parser.xml with maximum diagnostic output reading data from /tmp/syslog instead of /var/log/syslog as defined in the parser.

Best regards,
Victor

Hi,

you can change threshold to script like this:

v = GetCustomAttribute($node, "VoltageThreshold");
return $1 < ((v != null) ? v : 22);


then threshold will fire if voltage is less than 22 unless you have custom attribute VoltageThreshold set on a node - in that case it will compare current value with value of this attribute. So if you need to override threshold to fire if below 25v on specific node, go to that node properties, page "Custom Attributes", and add attribute VoltageThreshold with value 25.

Best regards,
Victor

Hi,

from value sizes it seems that value is there but cannot be displayed for some reason (possibly UI bug). Is it possible to provide raw value from database for testing?

Best regards,
Victor

Hi,

how big are those tables? Also, could you check values stored in tdata table for those two table DCIs - is value for empty table really small?

Best regards,
Victor

ПОхоже модем надо переключать в правильную кодировку. Можете прислать результаты команды AT+CSCS=? на вашем модеме?

This is the idea of templates (and why you always get a warning when editing template item on a node). If you need customizable thresholds you can use combination of script thresholds and custom attributes. For example, if you need to check that value is less than 10 unless custom value is set on a node in custom attribute "CustomThresholdValue" you can use the following script threshold:

v = GetCustomAttribute($node, "CustomThresholdValue");
return $1 < ((v != null) ? v : 10);


Best regards,
Victor

В 2.2.13 появилась функция обнаружения нод-дубликатов (с одинаковыми адресами), и в ней уже нашли несколько багов. Попробуйте отключить, выставив параметр сервера NetworkDiscovery.MergeDuplicateNodes в 0.

Попробуйте переключить драйвер из текстового в PDU режим.