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

Thank you this information Victor. I'm glad to help you to improve this app. Mortymer

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 capture_netxmsd_threads.sh

That fixed it. Old config was all on 1 line with semi-colon to separate the 2 variables. Removing semi-colon and placing on separate lines works

The csv importer v 1.1.2 was built with NetXMS v2 client libraries, this is why it didn't work. I have updated it and released 1.1.3, which is built with support for NetXMS v3.

In the SQL query output that you sent above you can see lines like this: <formatString>%*s</formatString> %*s should be replaced to some other format, where letter comes right after % character. NetXMS server should be stopped when editing the database. Care should be taken when editing the database, it's recommended to do database backup prior to editing. Alternatively you can wait when NetXMS 3.1 will be out - hopefully this will happen by the end of next week.

Hello, Sudanov. The nxagent.conf file is configured and running according to the documentation (active as log), but I still can't view/create an response time, Bytes received, time DNS resolution, load/download time, TCP time and connection, latency, availability chart. See the examples attached Thanks Cássio [image: Example CA BROADCOM EHEALTH MANAGER.PNG] [image: Example PRTG.PNG]

Hello, yes i´m talking about Sys_IF_Down.   Now we are testing snmp trap configuration for the interface disable events and it seems the best way.

Hello, When I used the last script I had no result. I checked the access_points table and I found many same rows. Screenshot attached. What do you think about this. The Node 842 is a Mikrotik router. I used this script to check how many duplicated records I have. select count(*), ap.node_id, ap.mac_address, ap.vendor, ap.model, ap.serial_number, ap.ap_state, ap.ap_index from access_points ap group by ap.node_id, ap.mac_address, ap.vendor, ap.model, ap.serial_number, ap.ap_state, ap.ap_index I attached the results. Any idea or suggestion? Thank you for any help! Regards, Mortymer [image: heidisql.PNG] [image: heidisql-2.PNG]

Hi, source address for connection is determined only by routing. NetXMS server itself does not specifically select source IP address. If routing is correct then it should work. For network service checks to work you should have "portcheck" sub-agent loaded in local agent (the one running on NetXMS server itself). Make sure that it is loaded. Also you may increase debug level for agent and check what is going on when server requests service check. Best regards, Victor

Hi, icon represents object status, which is calculated not only from alarms but also from underlying objects (so interface in critical state will still make node critical even if alarm is terminated). Maybe we can introduce additional indicator to show outstanding alarms. This will preserve current logic and give clear indication that something new was happened. Best regards, Victor

Currently $dci is not supported when a script is called from event processing. For SYS_THRESHOLD_EVENTs DCI ID is passed as 5-th parameter of $event: trace(1, "Script on SYS_THRESHOLD_EVENT: DCI ID: ".$event->parameters[5]+0); trace(1, "Script on SYS_THRESHOLD_EVENT: DCI name: ".GetDCIObject($node,($event->parameters[5]))->name); trace(1, "Script on SYS_THRESHOLD_EVENT: Interface name: ".GetDCIObject($node,($event->parameters[5]))->relatedObject->name);

Server console is not analyzing double quotes - enquoted arguments are just passed to the script as string having quotes on both ends, that's why it's not matching.

Now, for my final update: After some hours of digging, I found out that NGINX was the reason for the entire problem: It was not configured to pass the POST data to the proxied API server. Thus, there is no problem with the original API code - I guess that the scenario, as stated in my second update, may be related to the entity's content being empty, once it is read (Somewhere, I read about it being a stream, rather than a storage variable, but I'm not 100% sure about that) Anyway, I apologize for causing this false alarm and thank you for your support. Keep up the good work on this tool Best regards, fbu

Thanks Victor Worked!! Regards Clifford Dsouza

Thanks, After log in with system user, I've found the template and deleted it.

Hi Filipp, Great !! The problem is solved. I created a user in Postgres with ownership to the required schema. I configured this user in system DNS as well as in server configuration of netXMS while installing. It created all the tables in the specified schema instead of public schema. The problem is solved. Thanks you so much. Best regards, Ravi

We've managed to replicate similar behavior that could be related to what is happening on your system - when node is removed from template, the .xml does not get deleted from that node. You can follow resolution progress here: https://track.radensolutions.com/issue/NX-1704