NetXMS Support Forum

Try to cancel configuration wizard and run initialization manually (using nxdbmgr init) - it may provide more diagnostic information. You can also try to create user and database manually and choose "use existing database" option in configuration wizard.

Best regards,
Victor

Hi,

make sure that if you are using Windows authentication you have used * as login name and current user has access rights to the database, or if you are using SQL authentication (using login and password) that mixed mode authentication is enabled on SQL Server. Another possible issue could be using IP address (event loopback) with TCP/IP connector not enabled on SQL Server side.

Best regards,
Victor

Limits are 1023 characters for DCI parameter name and 255 characters for instance name.

Best regards,
Victor

Hi,

that could indicate that node representing NetXMS server is no longer considered to be local server. You can check that in server debug console - type command

show obj NetXMSServer

and check isLocalMgmt flag value. If this is the case try to find if new node was created to represent NetXMS server.

Best regards,
Victor

Hi,

currently it's not possible. I've added feature request for ability to pass extra parameters to generated event: https://track.radensolutions.com/issue/NX-1643

Best regards,
Victor

Hi,

this will require changes in NetXMS SNMP code. I've added feature request for that: https://track.radensolutions.com/issue/NX-1642

Best regards,
Victor

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