NetXMS Support Forum

Hi,

this should be fixed in installer version 3.9.178.

Best regards,
Victor

Hi all!

We just published patch release for version 3.9 that fixes some critical issues found after initial 3.9 release.Version number is 3.9.178 or 3.9.176 for deb packages (difference is only in Windows installer, hence why deb packages were not changed).

Changes since initial release:

- Added option to push DCI data using Web API
- Fixed bug in file transfer to agent on Windows
- Fixed agent crash if file template is used in logwatch subagent
- Fixed object tools in alarm browser
- Server configuration tree logged on startup
- Server installer on Windows has database initialization task unchecked when upgrading from pre 3.9 version
- Fixed issues:
        NX-2094 (Error ORA-01476 in Oracle subagent)
        NX-2097 (Server and agent cannot load configuration if it is a symbolic link)

Best regards,
Victor

Could you please provide screenshot of "Interfaces" tab for few such devices?

Best regards,
Victor

Hi,

it's packaging error. I just uploaded updated installers for agent and server, please try to download again.

Best regards,
Victor

Hi all!

NetXMS version 3.9 is released. It is minor release that provides lot of improvements over 3.8 and likely last one before major release 4.0. Full change log since 3.8:

- Predefined object queries
- LDAP synchronization filter
- User's email and phone number synchronized with LDAP
- Bind9 subagent rewritten in C++ and uses HTTP API
- New NXSL function replace
- Added Geolocation.History.RetentionTime server configuration parameter and geolocation history clearing by housekeeper
- Added percentage value to pie chart
- Added drill down object for tube and pie charts
- Network map link color can be defined by script
- Added method to get all tooltip data of the network map in one request
- New NXSL functions to make web service custom requests (GET, POST, PUT, PATCH, DELETE)
- JQ used for json parsing in web service requests
- NXSL function assert() accepts second argument - diagnostic message
- If agent configuration contains errors agent starts anyway and reports configuration load failure
- Agent configuration tree logged on startup
- Fixed broken "Responsible Users" object property page
- Object management endpoints in web API
- Source build configuration script do not throw error if libjq, libcurl, libssh, libmosquitto, or OpenLDAP are not available unless they are explicitly required
- Cambium ePMP driver can read geo coordinates from device
- Improved InfluxDB driver
- Fixed issues:
        NX-408 (Alarm log columns Ack by/Resolved by/Terminated by contain "admin" if not set)
        NX-1548 (Allow monitoring of dynamic number of logs via Logwatch)
        NX-1899 (Add description filter to Summary Table column definition)
        NX-1903 (REST API AdHoc Summary Table - add ability to filter dci on description instead of just dciName)
        NX-1964 (Windows installer unable to create user on MySQL 8 )
        NX-1995 (Create object endpoint for REST API)
        NX-2030 (Use last known coordinates when re-adding node to network map)
        NX-2046 (Get remote file fingerprint using file manager)
        NX-2059 (Predefined object queries)
        NX-2061 (Add changing file owner and changing file permissions functionality to file delivery policy)
        NX-2063 (Detect conversion from group to super group in Telegram notification channel)
        NX-2070 (Add notification log and server action execution log)
        NX-2073 (Generate event when duplicate MAC address is detected on the network)
        NX-2074 (DCI Table Last Value Column Widths are very large)
        NX-2082 (File upload should support resume and consistency checks)
        NX-2083 (Alarm list scrolls when alarms being added or removed)
        NX-2086 (Notification channel driver for Google Chat)
        NX-2087 (Incorrect values reported by WindowsFirewall.State)
        NX-2088 (PostgreSQL driver reporting internal error "pResult is NULL in DrvExecute")

Best regards,
Victor

Hi!

I hope we will be able to make it part of 4.0 release (likely in autumn). It's not a firm commitment though and will be dependent on time and resource availability.

Best regards,
Victor

How did you specify server address? Try to use local IP address (127.0.0.1) instead of server name (I assume SQL server is on same machine).

Best regards,
Victor

Hi,

you have to enable TCP/IP for both client and server. Those are relevant documentation pages: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol?view=sql-server-ver15 and https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-client-protocols?view=sql-server-ver15.

Best regards,
Victor

2.2.15 is an extremely old version. I highly recommend upgrading to current 3.8, there are very good chance that this issue is long fixed.

Best regards,
Victor

Консоль требует 11 джаву, а стоит похоже 8.

Да, custom attributes можно менять только с помощью скриптов. Еще можно использовать persistent storage, там выставление знащений можно сделать пеямо в правиле без скрипта, но для считывания скрипт все равно понадобится.

Мы постараемся успеть включить NX-2030 в релиз 3.9.

Очень странно что не генерируется обратное событие. Можете показать лог событий для ноды вокруг момента, когда условие возвращается в норму?
И какая это версия NetXMS?

Hi,

try to set property sessionTimeout for nxmc.war to 28800 (is is 8 hours in seconds). There are multiple ways to set property for web UI application:

1. In nxmc.properties file - it should be somewhere in class path.
2. In JVM options - should be prefixed with nxmc., so you will have to specify -Dnxmc.sessionTimeout=28800 in JVM options.
3. In environment variables, prefixed with NXMC and converted to uppercase, in your scenario it will be NXMC_SESSIONTIMEOUT=28800

Best regards,
Victor

Hi,

NXSL function "replace" was added only in 3.9 branch, which is not released yet.

As for original geolocation issue - geolocation object constructor expects two floating point numbers as latitude and longitude. You have to manually convert d m' s" format into degrees.

Best regards,
Victor