NetXMS Support Forum

For SSH - please show how your object tool is currently configured.

For MikroTik - is it showing SNMP = Yes? What driver it currently uses (this is also visible in Overview tab).

There's currently no support for CAPsMAN

Downgrade from 6.0.4 to 5.2.8 x64 agent (using deploy package) results in "Problem with agent local database: could not open database" major event for me...

We somehow quietly published patch release 4 for version 6.0. Due to our participation in MWC 2026 last week packaging and publishing of 6.0.4 was very discreet. Changes since previous patch release:
- File delivery policy deployment uses separate agent connection to avoid interference with data collection
- NXSL removes trailing zeroes from floating point value representation (unless explicitly set as string)
- Database manager supports parallel table migration
- Internal node name resolver cache in syslog processor
- Fixed issues:
   - #2378 / NX-2171 (In Configuration-\>Object Tools-\>General-\>Icon, give more info about image size accepted)
   - #2920 / NX-2717 (Custom attribute conflict is not resolved back to normal)
   - #3128 / NX-2928 (Add --resolve parameter option to NetworkService.Status)
   - #3129 / NX-2929 (Left column of elements not displayed in interface Overview tab)
   - NX-2932 (File deployment from multiple policies should be serialized)
   - NX-2933 (External metric provider may leave orphaned processes on Windows)

Quote from: johnnyva on March 02, 2026, 11:04:34 PM@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade?  If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted?  Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?

Yes, conversion is a background task (but you should upgrade straight to 6.0.4), server will do conversion in background. Internally server renames idata tables, create new empty tables, and gradually moves data from old to new with conversion. So API will not see incorrect timestamps, but for some time after server start you will not see older data.

The same thing happens to me on all the graphs. It seems to depend not only on the number of data points displayed but also on the size of the viewing windows (the larger the window, the fewer missing data points...).

Jep - After seeing, that there was a problem, I've updated two of those Windows-Agents (the one from my deep-dive into Logs is one of them) to 6.0.4, but still doesn't work...

Hello @all,

perfomance view (see the attachment, please) seems a little bit buggy if i choose a view >= 2 days. I noticed that since V6.

Anyone else with the issue?


Greetings
Marco

Все еще актуально
Или таковую инфу только с самой базы запрашивать sql запросом?

Thanks Alex, I just restarted it today, so I will follow up in a couple of days when it blanks again.

Can you check memory consumption during these days? Feels like a memory / resource leak.