NetXMS Support Forum

Hi all!

NetXMS version 2.2.3 is out! Changes since previous release:

- Additional information about captured Windows Event Log event passed to the server
- Improved server startup time
- Automatic termination of related alarms when DCI is deleted
- Added attribute "isSTP" to NXSL class "Node"
- File I/O functions in NXSL (disabled by default)
- Sub-second interval between packets can be configured in PING subagent (down to 10 milliseconds)
- Fixed issues:
        NX-1149 (Pass EventRecordID with matched Windows event log record)
        NX-1258 (Option to pass event data from Windows event log to NetXMS event)
        NX-1259 (Added NXSL function - FindAlarmByKeyRegex)
        NX-1363 (Automatic deployment of agent policies)
        NX-1364 (Automatically create nodes for unbound agent tunnels)
        NX-1367 (Fix HP aCC compiler warnings)
        NX-1383 (Minimal interval before generating data collection script error events)
        NX-1389 (If library script saved with compilation errors it disappears from script list)
        NX-1392 (Reload log parser without agent restart)
        NX-1393 (PostgreSQL deadlock on updating raw_dci_data table)
        NX-1398 (Windows Server 2016 not detected correctly)
        NX-1399 (Some SQL queries fail when using MariaDB driver because of MariaDB bug CONC-281)

Best regards,
Victor

Hi,

likely old node was not deleted completely. Try to login with user "system", find that node, and delete it.

Best regards,
Victor

Seems to be packaging error. We will check.

Best regards,
Victor

Hi,

it seems that you have wrong version of client application. Make sure you have correct version, and in case you unpack it on top of old version, try to remove old version completely and unpack into clean folder.

Best regards,
Victor

Hi,

I didn't try it myself, but few things you may want to check:

1. what Eclipse version you are using? UI built on Eclipse 3.8.2.
2. Is there any errors in UI log (usually $HOME/.nxmc/data/.metadata/.log)?
3. You should use Java 7 or higher.

Best regards,
Victor

In agent configuration file (nxagentd.conf) on your NetXMS server make sure you have line

SubAgent = ssh.nsm

This will load SSH subagent. For SSH DCIs connection chain is following:

server --- NXCP protocol ---> agent with SSH subagent --- SSH protocol ---> target system

where agent can be on same machine as server or any different machine. This is why server do not connect directly over SSH but use agent instead.

Best regards,
Victor

Hi,

we somehow missed isSTP flag. Just added it to node class, will be available in 2.2.3 release.

Best regards,
Victor

Hi,

trusted nodes settings are used only when you set "source node" in DCI. It is irrelevant for SSH proxy settings. You don't need to create action for data collection - you correctly configured your DCI with SSH as data source.
Make sure that SSH subagent is loaded and can connect to target (you can set debug level to 6 and check agent log for messages with prefix SSH).
When you say your test DCI is not working - do you get data collection error, unsupported, or just empty value?

Best regards,
Victor

Hi,

it is in source code - but all text messages are in separate language files, so it is possible to translate UI without actual source code change. What language you are interested in? If you are willing to work on translation we can prepare language files for you.

Best regards,
Victor

Hi,

as you are building for development branch, you have to install dependency packages manually to your local repository from source tree. Do the following (from source tree root):


cd src/libnxjava/java/base/netxms-base
mvn clean
mvn install
cd ../../../../client/java/netxms-client
mvn clean
mvn install


Now you should have both dependencies installed.

Best regards,
Victor

I have added it to our tracker (https://track.radensolutions.com/issue/NX-1397). Will take a look at it as time permits.

Best regards,
Victor

Hi,

from UI you can open history view, select desired data range, and export data to CSV file. Or you can automate export (and do much more complicated things) using nxshell script. It's Python scripts with access to NetXMS API. Some examples can be found here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations

Best regards,
Victor

Да, в самом Windows. Вроде называлось так "encoding used by non-UNICODE programs". Ну и возможно что настройки правильные, просто надо при просмотре лога выбрать правильную кодировку.

Скорее всего это русские буквы. Если Windows русский, то названия счетчиков тоже по русски пишутся. Лог файл пишется в той кодировке, которая выставлена для non-UNICODE приложений.

Hi,

I suggest to either truncate alarms table completely (but you will lose all alarm history) or delete alarms older than certain time before starting netxmsd. You can do this by running query

DELETE FROM alarms WHERE last_change_time < ?;

Replace placeholder with actual time stamp. It is in UNIX time format, you can use this calculator to get value: https://www.epochconverter.com/.

Best regards,
Victor