NetXMS Support Forum

Quote from: Victor Kirhenshtein on March 12, 2026, 12:10:30 PMI just fixed that, we will publish patch release 6.0.5 soon.

Great, thanks Victor... 

Hi Filipp,

i'm using the V6.0.4 NetXMS Client.

Greetings
Marco

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

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

Hi Filipp,

nxdbmgr ist not running

:~$ ps fax | grep nx
    507 ?        Ssl    1:02 /usr/bin/nxagentd -S
  42549 pts/0    S+     0:00              \_ grep nx


...but nxdbmgr shows, that Background Update ist locked...


:~$ 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)


Should I run "nxdbmgr background-upgrade" anyway?

Greetings
Marco

Hi Filipp,

thanks for the fast reply. How can i recognize then background prozess?

ps fax shows me only this in combination with netxms:

 
    507 ?        Ssl    0:36 /usr/bin/nxagentd -S
 
    986 ?        Ssl    4:16 /usr/bin/netxmsd -S

603 ?        Ss     0:00 /usr/lib/postgresql/15/bin/postgres -D /var/lib/postgresql/15/main -c config_file=/etc/postgresql/15/main/postgresql.conf
    659 ?        Ss     0:06  \_ postgres: 15/main: checkpointer
    660 ?        Ss     0:00  \_ postgres: 15/main: background writer
    667 ?        Ss     0:01  \_ postgres: 15/main: walwriter
    668 ?        Ss     0:00  \_ postgres: 15/main: autovacuum launcher
    669 ?        Ss     0:00  \_ postgres: 15/main: logical replication launcher
    990 ?        Ss     0:20  \_ postgres: 15/main: netxms netxms 127.0.0.1(46052) idle
    991 ?        Ss     0:20  \_ postgres: 15/main: netxms netxms 127.0.0.1(46062) idle
    992 ?        Ss     0:19  \_ postgres: 15/main: netxms netxms 127.0.0.1(46064) idle
    993 ?        Ss     0:19  \_ postgres: 15/main: netxms netxms 127.0.0.1(46066) idle
    994 ?        Ss     0:17  \_ postgres: 15/main: netxms netxms 127.0.0.1(46078) idle in transaction
  12165 ?        Ss     0:16  \_ postgres: 15/main: netxms netxms 127.0.0.1(33932) idle



Other question: Can i run "nxdbmgr background-upgrade" while running the NetXMS server or must i stop the server?

Greetings
Marco

Hello @all,

want to update NetXMS from V5.2.8 to V6.0.1. After the Update NetXMS cannot upgrade DB:

Upgrading database...
Upgrading from version 52.24 to 53.0
Upgrading from version 53.0 to 53.1
Upgrading from version 53.1 to 53.2
Upgrading from version 53.2 to 53.3
Upgrading from version 53.3 to 53.4
Upgrading from version 53.4 to 53.5
Upgrading from version 53.5 to 53.6
Upgrading from version 53.6 to 53.7
Upgrading from version 53.7 to 53.8
Upgrading from version 53.8 to 53.9
Upgrading from version 53.9 to 53.10
Upgrading from version 53.10 to 53.11
Upgrading from version 53.11 to 60.0
Upgrading from version 60.0 to 60.1
Upgrading from version 60.1 to 60.2
Upgrading from version 60.2 to 60.3
Upgrading from version 60.3 to 60.4
Upgrading from version 60.4 to 60.5
Upgrading from version 60.5 to 60.6
Upgrading from version 60.6 to 60.7
Upgrading from version 60.7 to 60.8
Pending online upgrades must be completed before this step
Rolling back last stage due to upgrade errors...
Database upgrade failed

Background upgrades pending. Please run mnxdbmgr background-upgrade when possible.


So i rolled back the server to the latest snapshot...

After that i tried to upgrade the db with the following commands. Everytime i startet the upgrade, the "nxdbmgr background-upgrade" says the background update is locked by another process...

Also i don't understand, that "nxdbmgr check" says, its the latest db version, but if i run the "nxdbmgr background-upgrade" it want to upgrade the db version 52.24...

Please help, i'm a little bit lost... What have i to do to fix the db problem...

Many thanks
Marco

-------------------------------------

:~$ nxdbmgr check
NetXMS Database Manager Version 5.2.8 Build 5.2-506-g7d4137c08a

Checking database (excluding collected data):
* Zone object properties                                               [PASSED]
* Node object properties                                               [PASSED]
* Node to subnet bindings                                              [PASSED]
* Interface object properties                                          [PASSED]
* Interface bindings                                                   [PASSED]
* Network service object properties                                    [PASSED]
* Network service bindings                                             [PASSED]
* Cluster object properties                                            [PASSED]
* Cluster member nodes                                                 [PASSED]
* Access point object properties                                       [PASSED]
* Template mapping                                                     [PASSED]
* Business services                                                    [PASSED]
* Business service prototypes                                          [PASSED]
* Object properties                                                    [PASSED]
* Container membership                                                 [PASSED]
* Event processing policy                                              [PASSED]
* Network map links                                                    [PASSED]
* Data tables                                                          [PASSED]
* Orphaned data tables                                                 [PASSED]
* DCI configuration                                                    [PASSED]
* Raw DCI values table                                                 [PASSED]
* DCI thresholds                                                       [PASSED]
* Table DCI thresholds                                                 [PASSED]
* Business service checks - service bindings                           [PASSED]
* Business service tickets - service bindings                          [PASSED]
* Business service tickets - check bindings                            [PASSED]
* Business service tickets - hierarchy                                 [PASSED]
* Business service checks - state                                      [PASSED]
* Business service downtime                                            [PASSED]
* Assets                                                               [PASSED]
* Asset to node links                                                  [PASSED]
* Node to asset links                                                  [PASSED]
Database doesn't contain any errors
Database check completed

WARNING: Background upgrades pending. Please run nxdbmgr background-upgrade when possible.

-------------------------------------

:~$ sudo 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)

-------------------------------------

:~$ nxdbmgr upgrade
NetXMS Database Manager Version 5.2.8 Build 5.2-506-g7d4137c08a

Upgrading database...
Core database schema is up to date
Database upgrade succeeded

WARNING: Background upgrades pending. Please run nxdbmgr background-upgrade when possible.

-------------------------------------

:~$ 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

-------------------------------------


Hello @all,

is it possible to log the user sessions (User, Client name, Client Adress, ...) to the NetXMS event log?

Greetings
Marco

Hi Filipp,

Quote from: Filipp Sudanov on September 05, 2025, 04:43:15 PMCould be that during the execution of the first script it deleted all the duplicates.

I think, the duplicates was created while the update of NetXMS to V5.2.5. But, in cause of my revert to a VM snapshot with NetXMS V5.2.4, there are no duplicates in tables. I run the scripts above against the V5.2.4 Version of the tables (after i restored the snapshot of the VM)...

Greetings
Marco

Hi Alex,

thanks for the new script... Started it an the result is:


psql:showduplicate1.sql:39: HINWEIS:  Total duplicate rows found: 0


So, at earlier post you said i had duplicates, but the script says there are none... Whats the truth? :-)

Greetings
Marco

Hi Alex,

thanks for the hint. I try the script via psql with (showduplicate.sql is your script):

psql -h localhost -U netxms -p 5432 -a -f showduplicate.sql

But the only output is the script himself, there are noch other outputs:

xxx@xxx:~$ psql -h localhost -U netxms -p 5432 -a -f showduplicate.sql
Passwort für Benutzer netxms:
DO $$
DECLARE
    node_record RECORD;
    tbl_name TEXT;
    dup_count INTEGER;
    total_duplicates INTEGER := 0;
BEGIN
    FOR node_record IN SELECT id FROM nodes
    LOOP
        tbl_name := 'idata_' || node_record.id;
        IF EXISTS (
            SELECT 1
            FROM information_schema.tables
            WHERE table_schema = 'public'
            AND table_name = tbl_name
        ) THEN
            EXECUTE format('
                SELECT COUNT(*) FROM public.%I
                WHERE ctid NOT IN (
                    SELECT MIN(ctid)
                    FROM public.%I
                    GROUP BY item_id, idata_timestamp
                )', tbl_name, tbl_name) INTO dup_count;
            IF dup_count > 0 THEN
                RAISE NOTICE 'Table % has % duplicate rows', tbl_name, dup_count;
                total_duplicates := total_duplicates + dup_count;
            END IF;
        END IF;
    END LOOP;
    RAISE NOTICE 'Total duplicate rows found: %', total_duplicates;
END $$;

The script is running about 1h bevor i canceld it.

Am I on the right way to run the script?

Greetings
Marco

Hi Filipp,

thanks for then explanation. So, i give the update a second try... :-)

Greetings
Marco 

Hello @all,

after Upgrade to V5.2.5 i get the hint to run nxdbmgr background-upgrade from installer:


Upgrading database...
Upgrading from version 52.20 to 52.21
Upgrading from version 52.21 to 52.22
Database upgrade succeeded

WARNING: Background upgrades pending. Please run nxdbmgr background-upgrade when possible.
NetXMS MIB Compiler  Version 5.2.5 (5.2-431-g1b87ea4f16)
Copyright (c) 2005-2025 Raden Solutions




If i run then nxdbmgr background-upgrade i get the following errors:

DROP INDEX idx_tdata_7035
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »idata_7046« nicht erlaubt):
ALTER TABLE idata_7046 ADD PRIMARY KEY (item_id,idata_timestamp)
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7046« nicht erlaubt):
ALTER TABLE tdata_7046 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7052_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7052_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7052« nicht erlaubt):
ALTER TABLE tdata_7052 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »idata_7089« nicht erlaubt):
ALTER TABLE idata_7089 ADD PRIMARY KEY (item_id,idata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_tdata_7089« existiert nicht):
DROP INDEX idx_tdata_7089
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »idata_7096« nicht erlaubt):
ALTER TABLE idata_7096 ADD PRIMARY KEY (item_id,idata_timestamp)
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7096« nicht erlaubt):
ALTER TABLE tdata_7096 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7127_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7127_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7127« nicht erlaubt):
ALTER TABLE tdata_7127 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7128_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7128_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7128« nicht erlaubt):
ALTER TABLE tdata_7128 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7130_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7130_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7130« nicht erlaubt):
ALTER TABLE tdata_7130 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7132_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7132_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7132« nicht erlaubt):
ALTER TABLE tdata_7132 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7152_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7152_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7152« nicht erlaubt):
ALTER TABLE tdata_7152 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7159_id_timestamp« existiert nicht):
DROP INDEX idx_idata_7159_id_timestamp
SQL query failed (42P16 FEHLER:  mehrere Primärschlüssel für Tabelle »tdata_7159« nicht erlaubt):
ALTER TABLE tdata_7159 ADD PRIMARY KEY (item_id,tdata_timestamp)
SQL query failed (42704 FEHLER:  Index »idx_idata_7163_id_timestamp« existiert nicht):

The server seems to be running, but i have restored my VM to the last snapshot... To many errors in output.. :-)

Have anyone else this messages when running  nxdbmgr background-upgrade? We use Debian 11 / Postgres for NetXMS.

Greetings
Marco

 
Hello @all,
 
i have a DCI which collect Date/Time via Powershell every hour. For Example here the last Values from the history of this DCI:
 
"Timestamp","Value","Raw value"
"08.08.2025 06:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 05:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 04:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 03:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 02:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 01:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"08.08.2025 00:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 23:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 22:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 21:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 20:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 19:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 18:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 17:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 16:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00"
"07.08.2025 15:25:56","03.08.2025 18:00:00","03.08.2025 18:00:00" 


I created a Threshold to get an alarm if the value NOT change in the last 24h:

Function: "Diff with previous value" 
Sample: 24
Operation: "> : greater than"
Value: 0
Activation Event: <Type Warning>
Dectivation Event: <Type Normal>
 
But the threshold throws no alarm, even if change the sample count to 1 or 2.
 
Is this the false threshold function to compare a string? But in the NetXMS Documentation for Thresholds this function should work with strings...

---
Diff with previous value
Delta between the last and previous values will be used. If DCI data type is string and the last and previous values match, system will use 0, and if they don't - 1.
---- 
 
Where are my fault?  I am thankful for any hint...
 
Greetings
Marco
 
 
 

Hi Filipp,

you are my hero!!! 

Thanks for the infos. I truncate the table and postgres frees up the storage space...

Many thanks!

Greetings
Marco