NetXMS Support Forum

Quote from: Egert143 on Today at 09:08:56 AMI was looking for the server installer for windows and saw that now support is needed for this. That is why i asked if it was no longer free.

is building windows installer for server from source complex task ?

Depends on your experience of course Build itself is straight-forward - there is Visual Studio solution file in the root of source tree, it will handle all the builds. Tricky part is to get all the dependencies (openssl, libcurl, libssh, libjq, libmodbus, libmosquitto, libpcre, database client libraries, breakpad, libmicrohttpd). Some of those are for specific components only, which you can exclude from build if you don't need them.

Most likely you have to install SQL Server Native Client which is needed for mssql.ddr to work.

Best regards,
Victor

We will try to reproduce that, but it likely will take some time.
I registered it a s a bug: https://track.radensolutions.com/issue/NX-2527

Hi,

delete file /usr/local/share/netxms/mibs/netxms.mib - it is old compiled MIB database and should not be there. Most likely leftover from running MIB compiler directly in /usr/local/share/netxms/mibs at some point.

Best regards,
Victor

Quote from: Egert143 on Today at 08:54:52 AMHello

Is NetXms no longer free starting with version 5?

Hi,

is is still free and open source, we do not have plans to change that. What was changed is that some of the binary builds that we consider of being more enterprise level are not provided for free on our web site, and only available through support contract. Those builds are agents for AIX and Solaris, and server for Windows. You still can build them from source code though.

Best regards,
Victor

❗️❗️❗️ Don't upgrade to 5.0.0 yet, there's a bug that damages instance discovery filter scrips. 5.0.1 is under way ❗️❗️❗️


We just published NetXMS version 5.0. This major release was mostly focused on improving network maps, wireless network monitoring, internal scripting language (NXSL), and new UI. And of course there is lot of smaller improvements and fixes.

Make sure to check list of breaking changes, as there are few.

Full change log is following:
-  Improved network maps
-  Added network map link styling script
-  Delegate access option that allows read access to network maps without full read access to objects on a map
-  Reworked monitoring of wireless access points and controllers
-  Major overhaul of sensor objects
-  Many NXSL function deprecated in favor of object methods
-  Improved NXSL classes and functions for date/time handling
-  Add option to check alarm details from alarm log view
-  Log parser rules can define metrics that are populated from match data
-  Special NXSL return codes for data collection and transformation scripts (DataCollection::ERROR, DataCollection::NOT_SUPPORTED, DataCollection::NO_SUCH_INSTANCE)
-  New NXSL function FindAccessPointByMACAddress
-  New NXSL function GetMappingTableKeys
-  "Stop" function in script executor view
-  Desktop client can reconnect automatically after short connectivity loss
-  New agent metric File.Hash.SHA256
-  New agent list and table Net.IP.Neighbors
-  Index property displayed in MIB browser
-  Root object can be set for object query
-  Improved SNMP trap processing performance
-  New log parser file option "removeEscapeSequences"
-  Added peer certificate verification in ticketing system connectors
-  Housekeeper scripts (NXSL and SQL)
-  Improved REST API
-  Introduces new object class "Collector"
-  Downtime log controlled by EPP

Fixed issues:
-  NX-797 (Automatic reconnect of management console)
-  NX-1790 (Drag-n-dropped object are positioned to wrong place when map is scrolled down or right)
-  NX-1870 (Representation of float DCI that gets string data as input)
-  NX-1935 (Introduce hook script on map regeneration with ability to set link names)
-  NX-2006 (Remove example event templates (code 4000-4011) from database)
-  NX-2076 (Raw value should be always displayed as string)
-  NX-2292 (Automatic maps should not include nodes that are connected through a node that was excluded by filter script)
-  NX-2323 (Make parameters in all events named)
-  NX-2343 (Several changes in NXSL syntax in v 5.0)
-  NX-2375 (Use "varchar(max)" instead of "text" on Microsoft SQL Server)
-  NX-2403 (Add support for AES-192 and AES-256 in SNMPv3)
-  NX-2444 (On demand background external metrics)
-  NX-2455 (Ability to check TLS.Certificate.* for protocols with STARTTLS command)
-  NX-2481 (Add ability to manually poll network map generation)
-  NX-2507 (Add ability to cancel timers from NXSL)
-  NX-2520 (Remove "Channel name" selector from "Send notification" dialog)
-  NX-2523 (New agent metric Process.MemoryUsage (percentage of memory used by process))
-  NX-2524 (Option to disable threshold without deleting it)
-  NX-2525 (Add the ability to specify multiplier values in threshold)
-  NX-2526 (When editing a template with a DCI without instance to use instance - DCI becomes unsupported)

Agent crashes within OpenSSL library (specifically within EVP_PKEY_CTX_new) and I do not see any obvious problems with calling code. This part was not changed for quite some time. Was it working on older versions or this is new setup? What exact version of openssl package you are using?

Best regards,
Victor

We just published patch release 6 for version 4.5. It fixes important bug in background task scheduler (one of the effects being external providers in agents running at incorrect intervals), as well as few other bugs reported since previous patch release. Full change log since version 4.5.5:
- Fixed bug in background task scheduler
- Fixed bug in reporting access control
- Fixed minor memory leak in server
- Fixed event storm detection event generation
- Fixed incorrect notification popup size calculation in user agent
- Fixed bug in NXSL function CreateUserAgentNotification
- Improved housekeeper throttling logic
- User-defined scripts for housekeeper
- Object context menu available in alarm view
- Call for DCI status change added to web API

We just published patch release 5 for version 4.5. Changes since previous patch release:

- Fixed scheduled file upload
- Fixed policy apply on object selection change
- Fixed custom attribute conflict propagation and conflict removal
- Fixed agent crash on empty output from external table provider
- Fixed bug in pin/popup agent file view
- Updated OPC UA subagent dependencies
- New agent metrics System.CurrentTime.ISO8601.Local, System.CurrentTime.ISO8601.UTC, and System.TimeZoneOffset
- Bundled zlib updated to latest version
- Print exception trace replaced by error logging
- Disable walk action on root object in mib browser
- Business service polls can be disabled or will not be executed if object is unmanaged
- Added peer certificate verification for notification channels
- Fixed issues:
   - NX-2511 (In repeating events, you can specify no more than 5 characters, sometimes more is needed)
   - NX-2516 (CURLAUTH_NEGOTIATE in not available in libCURL 7.29.0)

qtech-olt is an old driver module, now it is called qtech. So what happened is that server attempted to load driver module built for old version, which had now incorrect references to other libraries.
If you are building server from source, make sure that before doing "make install" (or copying binaries to target machine) you removed everything from <install_prefix>/lib/netxms (/usr/local/lib/netxms in your case).

Best regards,
Victor

We just published NetXMS version 4.5.4. It is minor patch release that fixes few important issues found in 4.5.3. Full change log:

- Improved Juniper driver
- Improved integration with ticketing system Redmine
- Fixed build errors on Solaris 11.4 with Solaris Studio 12.6
- Fixed memory leak in web UI (server side)
- Fixed some server performance issues
- Fixed issues:
-  NX-2492 (Custom attribute inheritance conflict not detected)
-  NX-2515 (Inherited object custom attributes not deleted from children)

Hi,

on what operating system and what client (standalone jar, from installer)? Also, Do you have dark theme in the OS?

Best regards,
Victor

This is quite strange. Do you have alarms with huge repeat counts?

Best regards,
Victor

Yes, it's better to stop it.

Best regards,
Victor

Hello!

It will use server time.

Just fixed typo, thank you!

Best regards,
Victor