We just published patch release 5 for version 5.2. It wasn't actually planned, but we fix quite a lot of issues while developing version 5.3, so we decided that it is worth backporting some of those fixes and improvements into 5.2 branch.
Full change log since previous patch release:
- Agent configuration file options can be passed from command line
- New AIX agent metrics: System.Memory.Physical.Client, System.Memory.Physical.ClientPerc, System.Memory.Physical.Computational, System.Memory.Physical.ComputationalPerc
- User ACL reports generated in XLSX format
- Improved driver for Ubiquity AirMax devices
- Running configuration logged after log rotation
- Configurable maximum size for cached routing tables
- New metric USB.ConnectedCount in WinNT subagent
- Fixed incorrect object status calculation after restarting server with resolved alarms
- Fixed bug in network map display in dashboard widget
- Fixed bug in calculation of physical CPU usage on AIX
- Fixed missing agent database table file\_integrity
- Fixed process matching by user name in process information metrics in WinNT subagent
- Fixed incorrect detection of Windows Server 2025
- Fixed issues:
- NX-2794 (Add more info to log message: Potential node x.x.x.x in zone x rejected (IP address is known as cluster resource address))
- NX-2800 (Agent crash on Windows ARM systems)
- NX-2819 (DCI data recalculation not working for TimescaleDB)
- NX-2822 (Alarms not appearing if nxmc has reconnected)
- NX-2825 (Tables missing PK, this breaks master-master replication (at least in Postgres))
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
Hi,
The problem is that "apt upgrade" automatically started nxdbmgr background-upgrade.
But there's currently no lock mechanism, so starting it manually ended up in it running two parallel processes of it.
Lock will be added in a future version. Currently just don't run nxdbmgr background-upgrade after the upgrade (you can check with ps command that it actually running).
Hi Filipp,
thanks for then explanation. So, i give the update a second try... :-)
Greetings
Marco
Quote from: Spheron on September 04, 2025, 12:09:30 PMIf 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):
There is one more problem - you already have duplicates in the idata_* tables.
Try this query to find them:
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 $$;
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
Quote from: Spheron on September 05, 2025, 09:36:46 AMThe script is running about 1h bevor i canceld it.
It was rather inefficient.
Try this one instead:
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
RAISE NOTICE 'Processing table %', tbl_name;
EXECUTE format('
WITH ranked AS (
SELECT ctid,
ROW_NUMBER() OVER (PARTITION BY item_id, idata_timestamp ORDER BY ctid) as rn
FROM public.%I
)
SELECT COUNT(*)
FROM ranked
WHERE rn > 1
', 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 $$;
And then to delete duplicates:
DO $$
DECLARE
node_record RECORD;
tbl_name TEXT;
deleted_count INTEGER;
total_deleted 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
RAISE NOTICE 'Processing table %', tbl_name;
EXECUTE format('
WITH duplicates AS (
SELECT ctid,
ROW_NUMBER() OVER (
PARTITION BY item_id, idata_timestamp
ORDER BY ctid
) as rn
FROM public.%I
)
DELETE FROM public.%I
WHERE ctid IN (
SELECT ctid
FROM duplicates
WHERE rn > 1
)', tbl_name, tbl_name);
GET DIAGNOSTICS deleted_count = ROW_COUNT;
IF deleted_count > 0 THEN
RAISE NOTICE 'Deleted % duplicate rows from table %', deleted_count, tbl_name;
total_deleted := total_deleted + deleted_count;
ELSE
RAISE NOTICE 'Table % has no duplicates', tbl_name;
END IF;
END IF;
END LOOP;
RAISE NOTICE 'Total duplicate rows deleted: %', total_deleted;
END $$;
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
Could be that during the execution of the first script it deleted all the duplicates.
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
Hey Alex, I'd imagine we should also be checking for dupes on the tdata tables too right?
Quote from: Alex Kirhenshtein on September 05, 2025, 12:39:21 PMQuote from: Spheron on September 05, 2025, 09:36:46 AMThe script is running about 1h bevor i canceld it.
Quote from: johnnyva on September 16, 2025, 07:39:49 AMHey Alex, I'd imagine we should also be checking for dupes on the tdata tables too right?
Yes, if you have table DCIs configured.
But this issue is already sorted in 5.2.6