NetXMS Support Forum

Sorry, didn't notice that you are running server on AIX. This script won't work there. I will check how to capture thread stack traces there.

Best regards,
Victor

Yes, just clear old libs, that's the only solution.

Best regards,
Victor

Hi,

it seems that server hangs during startup. Can you try to capture threads with attached script (you'll need gdb installed on the system)?

Best regards,
Victor

Hi,

why do you empty /usr/local/lib? It seems that your NetXMS libraries are under /opt/netxms/lib64 (at least some version is there and linker catch it).

Best regards,
Victor

Hi,

most of the configuration is in the database. Database schema will be updated by database manager as needed. Server configuration file usually contains only database access and log configuration, and you can just copy it to new machine - there are no differences in syntax.

Best regards,
Victor

We are participating in Gitex Technology Week 2018 exhibition, which will take place in Dubai, from 14th until 18th of October.
You can find us at stand G1-25. Please join us there to check out our products, ask any questions regarding IT or payment infrastructure monitoring, or just for a random chat.

Мы делали миграцию для клиента именно в такой связке (Windows + MS SQL -> Linux + PostgreSQL), правда несколько лет назад. Все прошло успешно. Приведенной выше инструкции должно быть достаточно. В nxdbmgr были ошибки, но в 2.2.9 все должно быть исправлено.

In nxshell you can so whatever is possible from UI. Object modifications should be done via NXCSession.modifyObject method - you set necessary fields in object modification data object and then call modifyObject.

Best regards,
Victor

Hi all!

NetXMS 2.2.9 is out. Changes since previous release:

- New NXSL functions: Base64Decode, Base64Encode, EventCodeFromName, EventNameFromCode
- Original event name passed to alarm timeout event as 5th parameter
- Added information tooltips in switch port view
- Improved performance of active network discovery
- Minimum, maximum, and moving average for ICMP response time in ping subagent
- Fixed issues:
        NX-1463 (Web UI does not work under Tomcat 9)
        NX-1475 (Deselected "Create helpdesk ticket on alarm creation" is not being saved in EPP)
        NX-1486 (NXSL function CreateDCI should allow creation with default retention and poll intervals)
        NX-1489 (Unreliable MariaDB Connector/C version detection in workaround for MariaDB bug CONC-281)
        NX-1494 (Release 2.2.8 failed to compile on macOS)
        NX-1496 (Add agent parameters System.Memory.Physical.Available and System.Memory.Physical.AvailablePerc on FreeBSD)
        NX-1501 (In test mode $dci variable is not set)
        NX-1502 (Configuration poll resets SNMP version on node)
        NX-1503 (Access denied error on attempt to take screenshot even if user has take screenshot access right)
        NX-1504 (Server crash after compiling library script with syntax error)
        NX-1505 (Assignment in NXSL "global" statement ignored if variable already declared as global)
        NX-1510 (Agent list Net.InterfaceNames not supported on FreeBSD)

Best regards,
Victor

Hi,

what Java version you are using? Desktop client may not be compatible with Java 10 and higher.

Best regards,
Victor

Hi,

you can create script DCI with the following script:


// Read default gateway from DCI
gw = GetDCIValueByName($node, ".1.3.6.1.2.1.4.21.1.7.0.0.0.0");
if (gw == null)
return null;

// Find node which will be ping source
pingSourceNode = FindNodeObject($node, "netxms");
if (pingSourceNode == null)
return null;

// Return ping RTT from ping source node
return AgentReadParameter(pingSourceNode, "ICMP.Ping(" . gw . ")");


This script reads default gateway address from existing DCI and then use agent parameter ICMP.Ping to ping it from another node. Name of ping source node should be set in FindNodeObject function call.

Best regards,
Victor

Hi,

just sent upload link in PM.

Best regards,
Victor

So rest of connections were not discovered. I see that all discovered connections were discovered using spanning tree information. This is less reliable method and used by server as last resort. Is it possible to turn on LLDP or CDP on your switches? It will greatly improve discovery accuracy. If not possible, make sure that you have spanning tree protocol enabled on all switches.

Best regards,
Victor

Seems that they are not published. However, you can find javadoc archives in Maven Central: http://central.maven.org/maven2/org/netxms/netxms-client/2.2.6/netxms-client-2.2.6-javadoc.jar

Best regards,
Victor

Hi,

I cannot reproduce this issue. Could be packaging error. How do you run nxshell and what package you are using?

Best regards,
Victor