Hi all! We just published minor patch release for version 3.8. Only server and agent on FreeBSD 13 are affected. Changes since previous patch release: Fixed potential data loss in InfluxDB driver Fixed invalid memory access in NXSL VM when using expression variables Fixed interface counters access by agent on FreeBSD 13 Fixed bug in CAS server access Fixed bug in report definition processing Fixed server deadlock during proxy load rebalancing Read system description before interface list during configuration poll Separate debug tag for SMTP sender Best regards, Victor

Thanks. I correct event policy.

Dockerfiles available for 3.8.66! https://github.com/Matthew-Beckett/netxms-dockerfiles/releases/tag/3.8.366

Thank you very much 

Save the date – April 29, 2021 at 5pm CET (11am EST). We will organize online Q&A session with NetXMS developers. Please contact @moshenska in our Telegram support channel or at [email protected] to sign up.

Hi all! We just published new patch release for version 3.8 (3.8.267). Only server and web API are affected. Changes since release 3.8.262: Fixed server crash during scheduled task processing Fixed issues:         NX-2009 (Add notification channel driver "Shell command")         NX-2035 (Instance discovery using ICMP.Targets list crashes server)         NX-2037 (Save IP address of client connecting via WebAPI to audit log) Best regards, Victor

Hi all! New patch release for version 3.8 - 3.8.262 - is just published. Changes since version 3.8.250: Fixed server crash when accessing NXSL class metadata Fixed agent crash when parsing log files Fixed file handle leak in log parser subagent DCI Editor filter now search by description, parameter, and DCI ID Long polling can be disabled in Telegram driver Fixed Log Parser Policy save with empty agent action field Fixed issues:         NX-1770 (Add ability to filter by DCI name in DCI list)         NX-2033 (Incorrect interface name displayed in MAC address table for Mikrotik routers)         NX-2036 (Filter in DCI editor should search both description and parameter) Best regards, Victor

Hi all! We just published next patch release for NetXMS 3.8 - version 3.8.350 (3.8.251 for Linux agents). Changes since previous patch release: Added notification channel driver for SNMP traps Event processing macro %K (alarm key) also works in rules following one that triggered alarm Improved Data Collection Editor and Policy Editor usability DCI instance used for custom attribute lookup when expanding %{} macro Fixed sorting for "Object query" dashboard element Fixed memory leak in server related to "Object query" dashboard element Fixed issues:         NX-2022 (Rack with custom height is incorrectly displayed)         NX-2028 (Use instance name for custom attribute search when expanding %{} macro)         NX-2029 (Line Chart General Time Period keeps reverting to "Back from now" when trying to use "Fixed time frame" option)         NX-2031 (HTTP proxy parameter configured in nxmc properties has no effect) Best regards, Victor

Hi all! New patch release for NetXMS 3.8 (version 3.8.226) is just published. Changed since previous release: Lower memory footprint of NXSL scripts Correct handling of agent policies by external subagents Added attribute "tunnel" to NXSL class "Node" Server runs configuration poll on node after agent upgrade File manager subagent does not register same root multiple times Fixed refresh issues in Object Details view Fixed visualization issues in switch port view Fixed incorrect root object filtering in dashboard elements "Event Monitor", "SNMP Trap Monitor", and "Syslog Monitor" Fixed issues:         NX-2014 (Create NXSL property on node object that gives reference to each type of proxy)         NX-2024 (Add "Max Wait Time" to Server.EventProcessors Internal Parameter Table) Best regards, Victor

Hi all! NetXMS 3.8 patch release 3.8.193 is just published. It is must have update for Timescale DB users as it fixes critical compatibility issue with Timescale DB 2.x. Full change log: Fixed Timescale DB 2.x compatibility issues New methods isDirectChild, isDirectParent, isChild, isParent in NXSL class "NetObj" New NXSL function GetCurrentTimeMs Fixed possible server crash when agent tunnel is closing Always use UTF-8 instead of current system character encoding for exported CSV files Fixed process handle leak in Windows agent when external parameter providers are used Westerstrand SNMP device driver can read device geolocation NXSL function PollerTrace works in autobind filter scripts and instance discovery filter scripts Improved diagnostic output for manually started polls Improved network map tooltip data update Best regards, Victor

Save the date – March 4, 2021 at 4pm CET. We will organize online Q&A session with NetXMS developers. Please contact @moshenska in our Telegram support channel or at [email protected] to sign up. P.S. If you have any complex questions, let us know in advance.

Hi all! New patch release for version 3.8 is just published (version 3.8.166). Changes since previous release: Improved driver for H3C (now HPE) switches Fixed intermittent problems with SNMP communications via proxy agents Fixed multiple file download in file manager in web UI Fixed excessive server memory consumption when transferring file from client to agent over slow link Fixed occasional high CPU usage by server process Deleted unused job_history table Fixed graph refresh Fixed object synchronization issue in web UI Fixed memory leak in server Fixed incorrect sorting by "Source" column in user management view Fixed intermittent client disconnects Fixed interface synchronization for network map element on dasbhboad Fixed issues:         NX-1989 (Compile NXSL in dci instance discovery filter and container autobind filter)         NX-1990 (Add filter in Script Library)         NX-1996 (Retriggered event when node comes out of maintenance is missing value for currentValue (%4) parameter)         NX-2005 (Add ability to have formatting in Telegram notifications)         NX-2011 (NXSL inList function returns int32 instead of boolean) Best regards, Victor

You should add it to config of agent that is used for web service query. By default it is local agent on NetXMS server machine. Best regards, Victor

ok, thank you)

Hi all! We just published NetXMS server version 3.7.145. It fixes single bug in interface and subnet hook scripts processing. Only server is affected. Best regards, Victor

Hi all! New patch release for NetXMS 3.7 (build 3.7.130) is just published. Changes since previous patch release: Per node SSH port configuration New user properties "email" and "phone number" Fixed broken reporting server connector Fixed issues:         NX-1081 (Some devices are not detected correctly by CATALYST-GENERIC driver)         NX-1663 (NXSL function GetDCIValue should read value from database if cache is not populated yet)         NX-1965 (Inconsistencies in address range add/edit dialog) Best regards, Victor

Can confirm, after update no more failed db queries. Egert

This happens when you have Java 8. Try to upgrade to Java 11. Best regards, Victor

You don't need to re-install netxms-release-latest.deb if you already did that - just run apt update apt upgrade Best regards, Victor

@staj said in NetXMS 3.6 released: Can you explain how https://github.com/openssl/openssl/issues/12859 affects nxagentd and the downgrade to TLS 1.1? If certificate has exportable private key then agent will get the private key and use standard OpenSSL mechanisms instead of CNG engine for session authentication. In that case TLS 1.3 will be used if server supports it. If private key cannot be exported then agent will switch to TLS 1.1 and use CNG engine for authentication. @staj said in NetXMS 3.6 released: Looking at the code, it will find a Certificate in the SYSTEM Personal Certificate based on matching Friendly Name, Email, Subject, Template, Common Name, Org or Device Serial (in that order)? How does one specify what the agent should consider a match? EDIT: Tunnel::createFromConfig and ParseTunnelList seems to have the answer: Record format is address[:port][,certificate[,password]] Records meaning the configured MasterServers, ControlServers and Servers. So I guess an example would be: MasterServers = 10.0.0.1,ADCSTemplNetXMS Assuming ADCSTemplNetXMS was the name of a Certificate Template (Eg: Certificate issued by ADCS)? Not exactly. Tunnel connections configured using ServerConnection parameters, so it will be ServerConnection = 10.0.0.1, certificate_matching_string Certificate matching string consists of selector and value separated by :. Possible selectors are: name - certificate's friendly name (display name) in store email - EMail portion of certificate DN subject - certificate's subject template - template OID (not template name!) cn - CN part of certificate's DN org - ORG part of certificate's DN deviceSerial - device serial number so for example for certificate with friendly name "NetXMS Server" it will be ServerConnection = 10.0.0.1, name:NetXMS Server If you are interested, relevant code is in file src/agent/core/cng_engine.cpp, function MatchWindowsStoreCertificate. Best regards, Victor