NetXMS Forum

We just published patch release 2 for version 6.0. Changes since previous patch release: Added wireless controller bridge for UniFi controllers (PR #255) Small fixes in background conversion of collected data Improved AI assistant guardrails Added internal metrics for monitoring AI providers usage Added TLS support in web API using monitored reproxy process Fixed issues:   - NX-1658 (Drag and Drop confirmation prompt)   - NX-2495 (Do not treat disk I/O error as file rotation in log file monitoring)   - NX-2900 (Business Service check script editor should have hint)   - NX-2907 (ssh.nsm can not be loaded on Windows)   - NX-2913 (Cluster DCI is not populated to nodes under cluster)   - NX-2919 (Push DCI from agent log parsing may come in wrong order)   - NX-2925 (Proxy selector should show only relevant objects)

Hello, PostgreSQL is using it's default settings for a system with 16GB of RAM. I googled the recommended sizes for shared_buffers, effective_cache_size, work_mem, maintenance_work_mem, max_connections, and the current settings for those parameters are less than the recommended for a dedicated PostgreSQL server. Currently shared_buffers is at 2GB, work_mem is at 3MB, max_connections is 100, effective_cache_size is 7GB, maintenance_work_mem is 1GB. I'm probably going to have to adjust the settings around to see what fixes it. I might have to reduce the number of worker processes. Currently the set maximum is 27, and the top command confirms there are a lot of them.

Thanks for al the hard work. Using Netxms over a decade ! I just did the update to 6.0.1 from 5.2.4. I use silent management client installer with /VERYSILENT (deploy with MDM) Is there a option to let the management run in the notification aria if the user closes the management cliënt? (so that the user still is connected, and can get notification?) Use auto-login? (every start the users has to enter the Active directory password) Maybe update the silent install documentation for the management cliënt? (only available for the agent)

Hi Filipp, it worked!! Background Update has completed the task ... :~$ nxdbmgr background-upgrade NetXMS Database Manager Version 5.2.8 Build 5.2-506-g7d4137c08a Background upgrade is locked by another process Are you sure you want to start background upgrade? (Yes/No) yes Running background upgrade procedure for version 52.24 Background upgrade procedure for version 52.24 completed ...and the update to V6.0.1 worked without any error messages... Many thanks for the support... Greetings Marco

Thanks for the explanations. Now I understand... best... Detlev

Just RPi

fixed

Hi team, I wanted to inquire if we are expecting any improvements to the map view in NetXMS to enhance clarity, similar to what we see in WeatherMap. For reference, please check the map views in both NetXMS and WeatherMap. In WeatherMap, we get clear visibility into how much traffic is coming from which direction, with different colors for each direction based on traffic percentage. However, in NetXMS, it shows only one link color, making it unclear whether it's representing the inbound or outbound direction—this is handled much more clearly in WeatherMap. Additionally, data source labels cannot be placed differently in NetXMS, which further creates confusion regarding traffic direction. It would be great if we could incorporate similar features to improve usability. Please let me know your thoughts or if there's any timeline for such enhancements. dhaval lad [image: weathermap_map.jpg] [image: netxms_map.jpg]

На первом этапе дискавери сервер высылает пачку ICMP запросов на много адресов сразу (NetworkDiscovery.ActiveDiscovery.BlockSize - по умолчанию 1024), ждет ответов и рассылает следующую пачку. Так что список ответивших адресов он собирает достаточно быстро. Дальше там два этапа - первоначальный сбор данных о каждом адресе - это делают паралельные треды (в количестве ThreadPool.Discovery.MaxSize) и потом есть один тред, который анализирует эти данные и решает что делать (один, потому что у одного девайса может быть несколько адресов, а мы не хотим насоздавать несколько нод). В Debug Console по команде show queues показывается Node discovery poller, но это сумма очередей каждого из этих этапов. В 6.0 размер этих очередей скорее всего будет виден по-отдельности, когда-нибудь в будущем этот тикет может будет сделан: https://track.radensolutions.com/issue/NX-2616

Highlighters need to be implemented in code to be present in this list. Currently not a single one is present. What's you file format that you'd want to highlight, how complicated it is?

I've heard of two approaches - via web api and using pvesh command line utility. Both can be used - web services are supported in NXSL and there's now external data provider in agent that can parse json data (and pvesh provides json output). https://www.netxms.org/documentation/adminguide/agent-management.html#externaldataprovider I'd suggest you to check what data proxmox provides via these two interfaces, as these may differ and also may depend on proxmox's version. I can help with template developing, specifically with instance discovery part.

@filipp-sudanov said in nxmc 5.2.8 standalone jar core dump: The reason seems to be with the framework used to build the GUI. Here's Anthropic's Claude's comment on this, pls give us update if any of this helps: ● This is a SWT/GTK compatibility crash on ARM64 (Raspberry Pi 5). The segfault occurs in GTK's native code when rendering the          Infrastructure view. Here are potential fixes:                                                                                                                                                                                                                              Quick Fixes to Try Hi Filipp, Thanks for the feedback. Given that I am using KDE then that may further explain the issues as there is not much by way of GTK installed on this machine, though the core libraries are present. I will try the suggestions and revert. Best, Alex

The error is "Data too long for column 'lldp_id' at row 1". NetXMS found some new snmp device, for some reason the value for lldp_id column is too long and is not fitting into 255 chars. It would be good to understand which exactly is that device on your network. You can enable debug for poll.discovery tag by issuing debug poll.discovery 6 in Tools -> Server Debug Console. Then you should see some IP address being polled prior to the SQL error in the log. Once you know the IP address, please do a walk for 1.0.8802.1.1.2.1.3 branch and share the output. You can use nxsnmpwalk for that

We have this information in Audit log, but if you need it in Event Log - there's Hook::login script in script library that you can use for that. Make sure that this script returns true, otherwise it will prevent users from logging in. To see what attributes are available in this script you can try this - it will log details to server log: for (a : $user.__class.attributes) trace(0, "$user." .. a .. " = " .. $user.__get(a)); for (a : $session.__class.attributes) trace(0, "$session." .. a .. " = " .. $session.__get(a)); return true; Then you can use PostEvent() or PostEventEx() to create the event (https://netxms.org/documentation/nxsl-latest/#func-postevent), drop us a line if you need more help with scripting.

There are no arm installer (yet), but you can download standalone jar file, install java, and launch jar file directly

function GetTree(nodeID) { obj = FindObject(nodeID); if (obj == null) return; children = obj.children; for (n : children) { if (classof(n) == "Node") { ifaces = n.interfaces; for (iface : ifaces) { if (iface.description ~= "WAN") { println("Node: " .. n.name .. ", Interface: " .. iface.name .. ", Description: " .. iface.description .. ", IP: " .. iface.ipAddr); } } } // Рекурсия ВЫНЕСЕНА за пределы условия - обходим все контейнеры GetTree(n.id); } } GetTree(2); Основные изменения: function вместо sub — современный синтаксис obj.children вместо GetObjectChildren(obj) . вместо -> для доступа к свойствам .. для конкатенации строк (вместо , в println) Рекурсия вынесена за пределы условия classof(n) == "Node"

если появляются - значит instance discovery фильтр всё еще проходит. DCI удаляются автоматически, если для них фильтр вернул false. По умолчанию - через 7 дней. @argonauts said in FileSystem.Total: Как мне удалить все DCI, что я наплодил с созданием DCI под instance discovery? Со временем они появляются обратно ::)

I have managed to resolves this by resetting it in the database then restarting the netxms service