NetXMS Support Forum

Server generates event SYS_SCRIPT_ERROR for runtime errors in scripts, including instance discovery filter scripts, and also generates "warning" record in server's log. First parameter contains script identification string and second parameter contains error message. Unfortunately event is not generated if there is compilation error like in your case (although warning message in log still generated). I've fixed that in development branch, starting with next release you'll also get SYS_SCRIPT_ERROR event for instance discovery filter compilation errors.

On a side note, script syntax didn't change in that part - expression like

if (a < b) && (c < d) { }

was always a syntax error. Whole "if" expression should always be enclosed in parenthesis.

Best regards,
Victor

Hi,

I was able to reproduce this on my system. It's a bug in server. It is already fixed in development code and will be included into next patch release.

Best regards,
Victor

Hi,

the standard one. You can check manual here: https://www.netxms.org/documentation/adminguide/upgrade.html

Best regards,
Victor

Нет, но есть продукт наших партнеров - https://unimus.net/. Там есть импорт узлов из NetXMS, он делает резервные копии конфигурации и показывает различия между версиями.

И то и другое похоже баг в клиенте. Посмотрим.

Как-то так:


return $1 / GetDCIValueByName($node, ".1.3.6.1.2.1.43.11.1.1.8.1.1");


Small addition: if you have lot of values to convert or they change frequently you may want to create mapping table on the server (via Configuration -> Mapping Tables) and use NXSL function map (https://www.netxms.org/documentation/nxsl-3.0/#func-map) to map code to text.

Best regards,
Victor

Everything looks good. Please show object overview for few duplicating access points (I'm mostly interested in MAC address) and output of manual configuration poll on node.

Best regards,
Victor

Another option to avoid storing double events is to remove "write to event log" option from original event.

Best regards,
Victor

Hi,

you can switch object display mode to "large labels". In addition to basic object information any DCI marked as "Show last value in object tooltips" will be displayed on the label.

Best regards,
Victor

Hi,

seems like deadlock on server shutdown. Please try to capture netxmsd thread states with attached script (preferably on 3.0).

Best regards,
Victor

Hi,

is it that b.b.b.b/24 is actually 10.b.b.b/24 (i.e. within 10.0.0.0/8)? If not, could it be that those nodes actually have other interface with address in 10.0.0.0/8 subnet?

Best regards,
Victor

Hi,

when XMPP action is triggered but you do not see messages please try to capture state of netxmsd threads using attached script (you will need to install gdb and appropriate -dbg packages if you have installed server from deb repository). Also please try to set debug level to 6 and extract lines with text XMPP from server log when XMPP action is triggered.

Best regards,
Victor

Hi,

please also send walk output for .1.3.6.1.2.1.2.2.1.

Best regards,
Victor

Could you please provide SNMP walk output for OID .1.3.6.1.4.1.14988.1.1.1.3.1 on this Mikrotik device? Also, what NetXMS version you are using?

Best regards,
Victor