<![CDATA[NetXMS 2.2.5 released]]>UPDATE: this version change event log, alarms, syslog, and SNMP trap log tables, and will take significant amount of time to complete on large installations (>100mil records). We are working on the solution. In the meantime either postpone upgrade, or plan some downtime (up to couple of hours).

Hi all!

NetXMS version 2.2.5 is out. Changes since previous release:

  • Agent tunnel falls back to unbound mode in case of agent certificate validation failure
  • Zone information added to alarm log, event log, SNMP trap log, and syslog
  • Agent returns correct free memory value on Windows
  • Parameter System.Memory.Physical.Cached supported on Windows
  • Fixed issues:
            NX-333 (Add windows service descriptions for both server and agent)
            NX-622 (Alerts will not be generated in certain conditions: events, that persist after maintenence and node down after unreachable)
            NX-640 (File manager should show file owner and permissions)
            NX-716 (Server configurator on Windows should be marked as require-administrator)
            NX-922 (Service check template objects disappears after server restart)
            NX-1097 (Configuration option to ignore alarm's helpdesk state when doing resolve or terminate)
            NX-1157 (configure --with-dist fails if OpenSSL is not installed)
            NX-1397 (Implement Windows Update information parameters for Windows 10 and Windows Server 2016)
            NX-1415 (Windows 10 upgrades break agent tunnels)
            NX-1417 (File.Size parameter not working for Windows pagefile.sys)
            NX-1418 (Sort scripts in Execute Server Script dropdown)
            NX-1419 (AgentTunnels.ProcessUnbound scheduled task should be hidden)
            NX-1420 (Do not use unmanaged devices with SNMP for MAC resolving)
            NX-1421 (Configuration poll for node without SNMP and agent always read ARP cache from all SNMP devices in subnet)
            NX-1427 (Max manual Y values for graphs limited to 2147483647)
            NX-1431 ("Don't Fragment" option for ping sub-agent)
            NX-1433 (LDAP timeout blocks internal user database)
            NX-1434 (Return from function from within foreach loop in NXSL can cause unexpected runtime error)
            NX-1436 (Write hostname to agent log on startup)
            NX-1442 (Generic device driver cannot read interface list if device does not support ifNumber MIB object)
            NX-1446 ( Only one agent policy editor can be opened, if another policy is opened for editing, previous is closed without saving)

Best regards,
Victor

]]>https://forum.netxms.org/topic/5574/netxms-2.2.5-releasedRSS for NodeFri, 13 Nov 2026 07:25:01 GMTSun, 13 May 2018 15:11:39 GMT60<![CDATA[Reply to NetXMS 2.2.5 released on Sat, 19 May 2018 07:25:09 GMT]]>@victor said in NetXMS 2.2.5 released:

We had an issue with version number not being updated, and correct packages were uploaded on Monday. This is pure cosmetic issue though.

For agent issue, please show all System.Memory.Physical.* values.

Best regards,
Victor

hi victor,
ran some test and it seems fine.

BR,
Lindeamon

]]>https://forum.netxms.org/post/24315https://forum.netxms.org/post/24315Sat, 19 May 2018 07:25:09 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Fri, 18 May 2018 12:57:28 GMT]]>Still have an issue with agent crash without any logs about crash when polling DCI "PhysicalDisk.Model(0)".
iGodunoff already mentioned it in 2.2.2 release topic.

And I think I have some thoughts about it. Like example, vmware virtual machine do not crash, when polling DCI it shows:

HDD 0 model = VMware Virtual SATA Hard Drive

But in physical workstation in version 2.1 it had a value with some garbage

HDD 0 model = KINGSTON SV300S37A120G                  ,Ӕ瞒墑⿧瞖뚱獊⿧瞖뚉獊

Maybe it is a cause?

]]>https://forum.netxms.org/post/24307https://forum.netxms.org/post/24307Fri, 18 May 2018 12:57:28 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Thu, 17 May 2018 18:25:56 GMT]]>Did the upgrade and ran in to a bunch of DCI changed to unsupported alarms. All of the DCIs in question were supplied by external parameters from files in /etc/nxagentd.conf.d/. After some digging it seems that ConfigIncludeDir no longer defaults to /etc/nxagentd.conf.d/ but has to be set manually in /etc/nxagentd.conf.

A bit confusing when the log states Additional configs was loaded from /etc/nxagentd.conf.d on agent start even before adding ConfigIncludeDir.

]]>https://forum.netxms.org/post/24300https://forum.netxms.org/post/24300Thu, 17 May 2018 18:25:56 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Tue, 15 May 2018 17:36:06 GMT]]>We had an issue with version number not being updated, and correct packages were uploaded on Monday. This is pure cosmetic issue though.

For agent issue, please show all System.Memory.Physical.* values.

Best regards,
Victor

]]>https://forum.netxms.org/post/24277https://forum.netxms.org/post/24277Tue, 15 May 2018 17:36:06 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Tue, 15 May 2018 17:01:19 GMT]]>hi victor,

something is not right...
finished the installation of v2.2.5 and the management console is stating "admin@x.x.x.x (2.2.4). i have checked and management console is v2.2.5
i have opened the server console and again "...V2.2.4 Ready".
the agent is identified as v2.2.5 but the fix for the free physical memory is not applied and i see that the free physical memory is not correct. i have 16GB ram, used 1.7GB, free 14.4GB and cached 10.1GB. in the "System.Memory.Physical.Free" i see 4.7GB which is the subtraction of cached mem from free mem.

what is going on ?
Lindeamon

]]>https://forum.netxms.org/post/24276https://forum.netxms.org/post/24276Tue, 15 May 2018 17:01:19 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Tue, 15 May 2018 15:59:23 GMT]]>Hi Victor
That fixed it.
Thanks for your fast helpDani

]]>https://forum.netxms.org/post/24274https://forum.netxms.org/post/24274Tue, 15 May 2018 15:59:23 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Tue, 15 May 2018 14:53:04 GMT]]>Hi,

try to remove libraries from previous installation or run make install instead of simple make.

Best regards,
Victor

]]>https://forum.netxms.org/post/24271https://forum.netxms.org/post/24271Tue, 15 May 2018 14:53:04 GMT<![CDATA[Reply to NetXMS 2.2.5 released on Tue, 15 May 2018 14:15:22 GMT]]>Hi Victor
Thanks for this update. I tried to update the existing server installation (V2.2.4) on linux 64bit from sources.
While make I get the following error:

make[5]: Leaving directory `/usr/src/netxms-2.2.5/src/server/tools/nxdbmgr'
Making all in nxminfo
make[5]: Entering directory `/usr/src/netxms-2.2.5/src/server/tools/nxminfo'
  CXX      nxminfo-nxminfo.o
  CXXLD    nxminfo
../../libnxsrv/.libs/libnxsrv.so: undefined reference to `SNMP_Variable::getValueAsMACAddr() const'
collect2: error: ld returned 1 exit status
make[5]: *** [nxminfo] Error 1
make[5]: Leaving directory `/usr/src/netxms-2.2.5/src/server/tools/nxminfo'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/usr/src/netxms-2.2.5/src/server/tools'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/netxms-2.2.5/src/server'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/netxms-2.2.5/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/netxms-2.2.5'
make: *** [all] Error 2

Can you please help?
thanksDani

]]>https://forum.netxms.org/post/24268https://forum.netxms.org/post/24268Tue, 15 May 2018 14:15:22 GMT