<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NetXMS 3.0 patch release 1 (version 3.0.2284)]]></title><description><![CDATA[<p dir="auto">Hi all!</p>
<p dir="auto">NetXMS patch release 1 (version 3.0.2284) is out. It fixes some issues in initial 3.0 release:</p>
<ul>
<li>Fixed Windows agent bug: socket handles inherited by child processes</li>
<li>Fixed FreeBSD 12 build errors</li>
<li>Fixed bug in reading network interface stats on Solaris 11</li>
<li>HTTP/2 included into default pattern in netsvc and portcheck subagents for HTTP/HTTPS protocol check</li>
<li>Fixed broken "Find IP address" function in management console</li>
<li>New default tile server for geo maps</li>
<li>Fixed bug in database migration to TimescaleDB</li>
<li>Fixed network map view crash if map has more than 9 links between two objects</li>
<li>Fixed incorrect handling of password expiration warning in Oracle database driver</li>
<li>Fixed file handle leak in server</li>
<li>Unused capture groups in NXSL regexp matching not reset to NULL</li>
<li>Regexp matching operation in NXSL returns array of capture groups on success</li>
<li>Agent returns correct version (without build hash) in Agent.Version parameter</li>
<li>Interface alias correctly set on interface object creation</li>
<li>Fixed minor memory leak in server</li>
</ul>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/topic/6173/netxms-3.0-patch-release-1-version-3.0.2284</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 17:14:06 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6173.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 18 Sep 2019 18:54:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NetXMS 3.0 patch release 1 (version 3.0.2284) on Thu, 19 Sep 2019 11:58:54 GMT]]></title><description><![CDATA[<p dir="auto">NXSL issue is fixed in version 3.0.2287 (only server has to be upgraded).</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/26578</link><guid isPermaLink="true">https://forum.netxms.org/post/26578</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 19 Sep 2019 11:58:54 GMT</pubDate></item><item><title><![CDATA[Reply to NetXMS 3.0 patch release 1 (version 3.0.2284) on Thu, 19 Sep 2019 05:48:13 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/victor" aria-label="Profile: victor">@<bdi>victor</bdi></a> said in <a href="/post/26568">NetXMS 3.0 patch release 1 (version 3.0.2284)</a>:</p>
<blockquote>
<ul>
<li>Regexp matching operation in NXSL returns array of capture groups on success</li>
</ul>
</blockquote>
<p dir="auto">The above is currently causing issues if you have logical operators combined with regular expressions in statements like the following:</p>
<pre><code>if ( ( $node-&gt;snmpOID ~= "^\.1\.3\.6\.1\.4\.1\.1991\..*" ) &amp;&amp; ( $node-&gt;snmpOID != ".1.3.6.1.4.1.1991.1.3.52.2.4.1.1" ) ) return true;
</code></pre>
<p dir="auto">This will fail with an error "Condition value is not a number".</p>
<p dir="auto">If you have scripts with if statements utilising regular expressions and logical operators together, you should wait for a patched version (which is being worked on already).</p>
]]></description><link>https://forum.netxms.org/post/26573</link><guid isPermaLink="true">https://forum.netxms.org/post/26573</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Thu, 19 Sep 2019 05:48:13 GMT</pubDate></item></channel></rss>