NetXMS Support Forum

1) Yes, you need to configure DCIs with relevant OIDs. This typically is done in a template, for modular things like PSUs instance discovery can be used to autodetect things. Feel free to ask for more details.

2) Since v 5.something we have out-of-the-box templates for traffic monitoring, see under Templates->Interface traffic. They are not applied by default (to avoid surprise on large installations with thousands of network devices), so you need to add custom attribute "Template.InterfaceTraffic" with value "YES", you can just do it on Infrastructure Services and put "Inheritable" checkbox.

UPD: reproxy has no repository, but there's .deb package - you can just install that: https://github.com/umputun/reproxy/releases

Reproxy on linux needs it to be installed manually, as it's not easily available from package. On linux we might use something else in the future. So currently nginx is the way.

Supported parameters are basically Address and Port, Address supports "*" or "any" to bind to all interfaces. (https://github.com/netxms/netxms/blob/master/src/server/core/webapi.cpp#L410)

Rest of params are for reproxy which is not relevant if using nginx (https://github.com/netxms/netxms/blob/master/src/server/core/webapi_tls.cpp#L205)

Quote from: NosekTomas on February 17, 2026, 08:11:36 PMHi,
I'm starting to play around with NetXMS and I can't seem to connect the new application. Or rather, I can't get the WebAPI to work/open.

I used NetXMS a long time ago, and now I'm coming back to it. Back then, there was still the old Android application, which communicated via its mgmt port.

Unfortunately, I couldn't find any documentation on how to get this new application up and running; the documentation refers to the old version.

If I understand this thread correctly, the application requires the new WebAPI – the one that is set up as a module in netxmsd.conf (not the old one that was installed via a war file and tomcat).

Hi and welcome back

Mobile app expects the endpoint to be https, while server module produces only http. Prior to 6.0.2 recommendation was to put nginx in reverse proxy mode. In 6.0.2 now includes reproxy, which is started by server process. You need to generate certificate files and then the following server config should work:

[WEBAPI]
TLSEnable = yes
TLSCertificate = /opt/netxms/etc/server.crt
TLSCertificateKey = /opt/netxms/etc/server.key
TLSPort = 8443
Documentation is a bit behind because this is work in progress, but should be updated soon.

Should be supported. Pls try adding this to main section of server config:

DebugTags=ai.provider:8,ai.prov.openai:8,llm.chat:8,ai.assistant:8

and share server log file

There was some query just before CREATE TABLE idata_46970 which failed.
60.7 to 60.8 handles idata/tdata tables, doing this:

  1. Check if idata_<id> exists
  2. If the table is empty → DROP it
  3. If the table is not empty → RENAME it to idata_v5_<id>
  4. Create a new idata_<id> table using CreateIDataTable(id)

Pls check, do you have
idata_46970
idata_v5_46970
tables in the DB?

If idata_46970 is there, pls show output of
\d idata_46970

Was Postgres tuned, may be excessivly, e.g. too big shared_buffers or something?

dlauwers, twparker
can you run
nxdbmgr -t upgrade

This is to see what exactly it's doing there

If you check a container, there'll be Data Collection tab there which allows to search DCIs on child nodes.
Now, collector is basically a container, but with data collection. So one "Data collection" is for DCI search and the other for data collection like it is on a node. As for the naming, it could probably be a bit less confusing

Data collection is basically limited to script or web services, or to other sources if you do Source node override in DCI properties.

Just RPi

Yes, this seems to be a lock without the actual upgrade. Pls run nxdbmgr background-upgrade and force unlock.

Quote from: twparker on February 10, 2026, 04:52:14 PMI can see that the database upgrade is happening in the background, but the netxms-server service won't start.
"Your database has format version 60.7, but server is compiled for version 60.32"

Are you still in upgrade to 6.0.0, or you've restarted upgrade to 6.0.1?

...happening in the background - is it nxdbmgr background-upgrade running? If so, you need for it to finish and then run nxdbmgr upgrade again - it will upgrade schema further. This step could be a background one in 5.2, but when upgrading to 6.0 we need it to complete prior to subsequent db upgrade steps.

yes, that's background migration, server reads collected data both from non-migrated and migrated tables, so everything should work even during migration.
Would be interesting to know how long it takes on your system and how big it is (sh st output - number of nodes, dci count, size of the DB)

Command line should contain nxdbmgr

Yes, that's the idea of background upgrade that it runs while server is running. This way we minimize server downtime.

Yes, RPi is a bit low priority, needs fixing. Pls try if agent from this binary archive will run: https://netxms.org/download/releases/6.0/nxagent-6.0.1-linux-arm.tar.gz