NetXMS Support Forum

Hi all!

NetXMS version 3.6 is just released. We plan that it will be last release in 3.x branch, but depending on progress with 4.0 development and requests from our customers and community we may also introduce 3.7 in a month or two.
Changes since previous release:
- Object categories
- Support for externally provisioned agent certificates
- New instance discovery method "internal table"
- Added option to validate server certificate on agent
- Fixed column sorting in Web Service Definition view
- Support for IPv6 in NXSL functions AddrInSubnet and AddrInRange
- New NXSL function GetServerQueueNames
- New NXSL functions for object search: FindObjectByGUID, FindNodeByAgentId, FindNodeByIPAddress, FindNodeByMACAddress, FindNodeBySysName
- nxdbmgr option to migrate log tables in background
- Windows event log synchronization, server side parsing and agent side filtering
- Added option not to save to database Windows event log and syslog filtered by server parser
- Maximum number of client sessions can be configured
- Added support for SNMP data types FLOAT, DOUBLE, INTEGER64, UINTEGER64
- Correct decoding of values inside OPAQUE SNMP varbinds
- Added view for object tools with output executed on multiple nodes
- Added synchronous methods and completion callbacks for object creation in Java API
- Fixed nxdbmgr crash on import
- New built-in agent action Agent.RotateLog
- Server performance optimization for handling large number of agent connections
- Performance optimization of SNMPv3 processing
- NXSL performance optimization
- Improved handling of external parameter providers in agent
- Added background polling option for external tables in agent
- Authentication method for LDAP users can be changed
- Support for mobile devices with NTCB/FLEX protocol
- Geolocation control for nodes, sensors, and mobile devices
- Fixed screenshot issues on Windows 10 with DPI scaling
- Fixed errors on graph properties modification
- Fixed sorting in summary table when one column has different data types
- Fixed issues:
   NX-904 (Sensitive info should be hidden in Audit Log)
   NX-1294 (Completed Scheduled Task Re-scheduling)
   NX-1416 (NetXMS Agents shutdown does not end ExternalParametersProviders)
   NX-1823 (Using SSH login and password in object tools)
   NX-1905 (Log Parser policy in Template Agent Policies does not automatically include Events in Export Configuration Tool)
   NX-1907 (Add server configuration option to disable outdated SSL/TLS versions)
   NX-1911 (Separate object name for use on maps)
   NX-1931 ("Do not store" option for syslog)
   NX-1933 (Update descriptions and units for server configuration variables)
   NX-1951 (Moving a DCI to container deletes the DCI)
   NX-1962 (Save time of last configuration poll across server restart)

Best regards,
Victor

Попробуйте принудительно поставить драйвер H3C, выставив custom attribute под названием snmp.driver в значение H3C.

На Linux сервер использует вызов gethostbyaddr для получения имени хоста по адресу. Вроде как на его работу влияет /etc/host.conf и /etc/nsswitch.conf - можно посмотреть что можно сделать в /etc/host.conf.

К сожалению это не настройки, надо менять код генерации карт. Добавил как feature request: https://track.radensolutions.com/issue/NX-1976

Added it to our bug tracker: https://track.radensolutions.com/issue/NX-1975

Hi!

It is likely bug in upgrade procedure. We've seen it on few systems but was not able to identify root cause. Just delete duplicate entries in object tool configuration.

Best regards,
Victor

Hi,

sounds quite strange. Could you illustrate your problem with some screenshots?

Best regards,
Victor

Hi!

Most likely problem is with UNICODE. By default NetXMS is build in UNICODE mode, so it uses wchar_t for all characters. I suppose that your program built as non-UNICODE, so it actually passes char to functions from libappagent that actually expects wchar_t. I'd recommend to build app agent separately with UNICODE disabled and link that version with your application.

For example, you can configure NetXMS sources like this:


./configure --with-sdk --disable-unicode --prefix=/opt/nxsdk

and then build you application adding

-I /opt/nxsdk/include -L /opt/nxsdk/lib -lappagent -lnetxms


You can get slightly more diagnostic from app agent by setting nxlolg debug callback:

    nxlog_set_debug_writer(DebugWriter);
    nxlog_set_debug_level(9);


With debug writer similar to this:

static void DebugWriter(const TCHAR *tag, const TCHAR *format, va_list args)
{
    if (tag != nullptr)
        printf("[%s] ",tag);
    vprintf(format, args);
    printf("\n");
}


Attached is functional example for reference. I've compiled it as following:
g++ -o demoapp demoapp.cpp -I /opt/nxsdk/include -L /opt/nxsdk/lib -lappagent -lnetxms

Sample app output:

victor@xps13:~/Source/appagentdemo$ LD_LIBRARY_PATH=/opt/nxsdk/lib ./demoapp
Initializing AppAgent...
Starting AppAgent...
Application agent startedApp started
NamedPipeListener(appagent.DEMOAPP): waiting for connection
NamedPipeListener(appagent.DEMOAPP): accepted connection by user victor


nxappget output:

victor@xps13:~$ /opt/netxms/bin/nxappget DEMOAPP DemoApp.Metric1
OK
victor@xps13:~$

Hope this helps!

Best regards,
Victor

Hi,

what version you are using, and what component - session agent or user agent? I remember dealing with that (or similar) issue at some point in the past...

Best regards,
Victor

Yes, you have to get node object first. Global variables $node and $object refer to current node. You can use function FindObject to get other objects. This function accepts either object ID or name. For example, if you want to print alarms for node named "netxms-server":

node = FindObject("netxms-server");
for(a : node->alarms)
{
println(a->message);
}


Best regards,
Victor

3.5.136 is now available in repository.

Best regards,
Victor

Packages on download page were updated to version 3.5.152 due to packaging issues. Functionality wise this version is identical with 3.5.136.

You can mark option "tool generates output" in object tool configuration and use println in script for sending output back to client.

Best regards,
Victor

Hi all!

NetXMS agent was updated to version 3.5.136 - it fixes possible agent crash when accessing agent thread pool metrics.

Best regards,
Victor

Hi,

do you monitor thread pools on agent? If yes, try to temporarily disable those DCIs. Recently we've discovered bug that can lead to agent crash after querying data for thread pool WEBSVC.

Best regards,
Victor

P.S. We started build 3.5.136 - it should be published in few hours and probably will fix that.