NetXMS Support Forum

Pls give some details. 
Is you NetXMS installed on Windows or Linux?
Do you use WEB UI? Have you tried the desktop UI?

Quote from: nichky on July 30, 2025, 12:41:16 PMhave u resolv it?

Looks like original post was 7 years ago. Since then external process execution was reworked, there is some mechanism that should terminate external processes on timeout, but I am not sure if this happens during shutdown. 

Are you experiencing some issues now? With what NetXMS version?

Database configuration step of the installer just modifies C:\NetXMS\etc\netxmsd.conf file. When this happens, the product is already installed, so you can skip this step and modify the configuration file directly. 

Once the file has correct credentials, you can go to C:\NetXMS\bin folder and run 
nxdbmgr init
This should initialize the DB, after that you can start NetXMS Core service using Windows Services. 

#140 is relate to new nxdbmgr functionality - it now can do in-place conversion of Postgres DB to Timescale. 

But this here is a different bug - I've created a ticket for it: https://track.radensolutions.com/issue/NX-2819
This issue affects only recalculation of historic values, but new values should be transformed correctly. 

If you've been using windows event syncronization, then 

VACUUM FULL WIN_EVENT_LOG; 
query might help, but it also needs additional disk space for it to run (https://www.postgresql.org/docs/current/sql-vacuum.html). 

If do don't need any records from this table, then
TRUNCATE WIN_EVENT_LOG;
will clean all records and instantly reclaim disk space

На Download странице есть упоминание об этом: https://netxms.com/downloads/

Windows сборки сервера имеют ограничение в 250 нод. На Линукс платформах ограничения нет и не планируется. 

You can just do "Execute script" on your node and try the following script from there:

r = $node.executeSSHCommand("ping 8.8.8.8 repeat 3 timeout 1");
println(typeof(r));
println(r);
It will print the result of executeSSHCommand() function.

One probable issue is that ssh communication goes through the agent that runs along with the server. So this agent should have
SubAgent = ssh
in it's configuration file (make sure you restart the agent after making the changes).

To debug you can add
DebugLevel = 6
to agent configuration file - agent log should give some information the moment when you execute your script.

Hi, 

For Huawei the information might be here: https://support.huawei.com/hedex/hdx.do?docid=EDOC1100333029&id=EN-US_CONCEPT_0176370110

Can you show walk output for
1.3.6.1.4.1.2011.5.25.40.4.1.14.1

Hi, 

Quite a few things changes between these two version, one of them is that for performace reasons interfaces are synchronized only when needed. In most places this works quite transparently and they are received from the server as needed, but in object tree the search is actually a filter and finds only objects that are syncronized. 
There's a setting that changes this behavior, it's in client's properties, Objects->Full object synchronization on startup

Still not resolved, created bugtracker ticket so it won't be forgotten
https://track.radensolutions.com/issue/NX-2813

Changes were made in the code, please try v.5.2.4 

Yes, looks that there's still a bug with webapi packaging, will check with developers. 
Webui should now be available for download (but, just in case, you can use any 5.2 webui or desktop ui with 5.2.4)

New Android client uses new WEB API that is a server module. 

Quick setup guide:
- add "Module=webapi,Y" to netxmsd.conf, module listens on port 8000 by default. You can change it:
[WEBAPI]
ListenerPort=12345

Please note, it's unencrypted HTTP!
- add nginx, reproxy, traefic - or any other ssl offloading app in front of it.
- connect to the APi endpoint.

But for testing you can skip this and just use HTTP

Hi, 

A few changes were made in the code, including better logging and special handling if 0.0.0.0/0 subnet was received during network discovery. This will be included in next patch release that should be in the coming days. 

PING3 is something niche and yes, looks that it's being auto-detected incorrectly. You can put PING3 into NetworkDeviceDrivers.BlackList server configuration parameter, this will prevent the auto-detection