NetXMS Support Forum

Hi,

yes, this is known issue fixed in 2.2.13 (crash because of improperly loaded scheduled task).

Best regards,
Victor

Hi,

yes, there is a bug in server (buffer overflow). Just fixed it with commit 0b33902b23047427b5d15ca9b70c75ed5571affa. You can rebuild server from source or wait for release 2.2.15 with the fix.

Best regards,
Victor

Hi,

log file does not suggest that service is not started. Try to run with debug level 9. If netxmsd process disappears after start, try to run it under gdb and provide stack trace (output of bt command in gdb).

Best regards,
Victor

Did netxmsd process gone or it is running but became unresponsive? If latter, please make sure that you have gdb installed and run attached script. It will capture thread stack traces within netxmsd and save them into /tmp. Please provide generated trace file.

Best regards,
Victor

Hi,

seems to be a bug in the server. What version you are using? Is there core dump for server process?

Best regards,
Victor

We have discovered critical bug in version 2.2.14 related to zone object loading from database. It is fixed in updated server package (version 2.2.14-5). Update is needed only for installations with zoning enabled.

Best regards,
Victor

Hi all!

NetXMS version 2.2.14 is officially released. Changes since previous release:

- Local cache on agent side for data pushed with nxapush
- Support for statsite sink format in nxapush
- Updated default MIB collection
- nxget command line option to print table as delimited text
- Drill down dashboard or network map for "Gauge" dashboard element
- Added trigonometric functions (sin, cos, tan, asin, acos, atan, sinh, cosh, tanh) to NXSL
- Improved configuration import
- Implemented parameter Process.WkSet on AIX
- Additional system information parameters on Windows
- Added NXSL hook for subnet creation
- Interface object properties can be changed inside interface creation hook
- Improvements in web service API
- Support for migration to and from TimescaleDB in nxdbmgr
- Fixed issues:
        NX-1537 ("Hidden" flag for DCI)
        NX-1574 (Add hasActiveThreshold attribute/method to DCI object accessible in NXSL)
        NX-1576 (Add $2 to instance DCI script hint)
        NX-1577 (Rename server configuration parameter 'TopologyExpirationTime' to 'Topology.AdHocRequest.ExpirationTime')
        NX-1580 (Updated FOUNDRY MIB // Updated CPQHOST MIB)
        NX-1586 (Comments field when putting node into maintenance mode)
        NX-1588 (Object load error can cause server crash)
        NX-1590 (SecondsToUptime function: Incorrect display in some cases)
        NX-1593 (Create separate access right for configuration import)
        NX-1603 (Windows Server 2019 is being detected as Windows Server 2016)
        NX-1604 (ICMP sub-agent automatic targets may be deleted immediately after creation)
        NX-1605 (MariaDB driver - TLS connections don't work)
        NX-1608 (Support for PtP subnets /31 and /127)
        NX-1614 (Improvements to DNS monitoring / resolving)

Best regards,
Victor

Hi,

that's definitely a bug, we will check it.

Best regards,
Victor

Hi,

it looks like a bug (likely related to handling 64 bit integers), but we didn't have time to check it yet. Somebody from the team will take a look at it shortly. You may also register issue in out tracker - that will help not forget about this issue.

Best regards,
Victor

Hi,

make sure that netxmsd is not running, then run

nxdbmgr unlock

to remove database lock.

Best regards,
Victor

Hi,

yes, idea is that you add this attribute on each node where default threshold value should be overridden. You cannot exclude certain DCIs from being applied as part of template.

Best regards,
Victor

Hi,

that's quite unusual behavior for SNMP agent to return error on whole packet due to one invalid OID, but server definitely should be modified to handle such response correctly. Is it possible to provide us remote access to one such device for debugging? If not, could you provide full packet capture (output of tcpdump -w)?

Best regards,
Victor

Hi,

do you see correct value in "Last values"? Do you have data type for DCI set to 64 bit integer?

Best regards,
Victor

Hi,

please check if there is any errors logged in UI log (usually it is in $HOME/.nxmc/data/.metadata/.log).

Best regards,
Victor

Hi,

we are using libtre as regexp engine, their regexp syntax is described here: https://laurikari.net/tre/documentation/regex-syntax/.

There are two options for testing regexps and parsers:

1. Create simple NXSL script like below:

if ($2 match $1)
{
println "Matched";
println "  CG1 = " . $1;
println "  CG2 = " . $2;
println "  CG3 = " . $3;
println "  CG4 = " . $4;
println "  CG5 = " . $5;
}
else
{
println "Not matched";
}


and run it from command line:

victor@hp8570w ~/tmp $ /opt/netxms/bin/nxscript regex.nxsl 'Error\s(.*)' 'Error 44'
NetXMS Scripting Host  Version 3.0.1690
Copyright (c) 2005-2018 Victor Kirhenshtein

Matched
  CG1 = 44
  CG2 = Error 44
  CG3 =
  CG4 =
  CG5 =
victor@hp8570w ~/tmp $


2. Use nxlptest tool (I'm not sure though if it is included into deb packages). It allows you to run specific log parser from command line overriding trace level and file name specified in the parser. For example, if I want to test parser on my syslog I can do it like this:

/opt/netxms/bin/nxlptest -D9 -t9 -f /tmp/syslog /opt/netxms/etc/syslog_parser.xml

It will run parser from /opt/netxms/etc/syslog_parser.xml with maximum diagnostic output reading data from /tmp/syslog instead of /var/log/syslog as defined in the parser.

Best regards,
Victor