Great, thanks for the reply and for fixing it.
I get this after running the sql
C:\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 6.0.2 Build 6.0-504-g549db2d3a0
Upgrading database...
Core database schema is up to date
Database upgrade succeeded
Anyone have any ideas please?
I also do not have a 'PendingOnlineUpgrades' in my metadata table, see below.
Bit more info
C:\NetXMS\bin>nxdbmgr -t upgrade
NetXMS Database Manager Version 6.0.2 Build 6.0-504-g549db2d3a0
Upgrading database...
Upgrading from version 60.33 to 60.34
Rolling back last stage due to upgrade errors...
Database upgrade failed
>>> SELECT var_value FROM metadata WHERE var_name='PendingOnlineUpgrades'
C:\NetXMS\bin>
Hi all,
Just updating from 6.0.1 to 6.0.2, get the error below?
Any ideas please
C:\NetXMS\bin>nxdbmgr.exe check
NetXMS Database Manager Version 6.0.2 Build 6.0-504-g549db2d3a0
Checking database (excluding collected data):
Your database has format version 60.33, this tool is compiled for version 60.34.
Use "upgrade" command to upgrade your database first.
Database check aborted
C:\NetXMS\bin>nxdbmgr.exe upgrade
NetXMS Database Manager Version 6.0.2 Build 6.0-504-g549db2d3a0
Upgrading database...
Upgrading from version 60.33 to 60.34
Rolling back last stage due to upgrade errors...
Database upgrade failed
Finished in about 15 minutes, db is around 8GB, not sure how many nodes
2026.02.10 11:35:45.590 *I* [dc.v5migrate ] Migrating recent data from v5 tables (106 idata, 3 tdata)
2026.02.10 11:50:21.154 *I* [dc.v5migrate ] Recent v5 data migration completed (109 tables migrated)
Thanks for the quick reply, yes, school boy error, it was admin cmd access.
currently sat at:
2026.02.10 11:35:45.590 *I* [dc.v5migrate ] Migrating recent data from v5 tables (106 idata, 3 tdata)
Thanks for the update, I'm still having issues with my one though.....
I restored the db back to the version 5.2.8 before i updated to 6.0.0
I've then run the new version 6.0.1 but the core service will not start, log file says:
2026.02.10 08:47:19.444 *E* [db] Your database has format version 52.23, but server is compiled for version 60.32
If i then try 'nxdbmgr check' i get:
C:\NetXMS\bin>nxdbmgr check
NetXMS Database Manager Version 6.0.1 Build 6.0-469-g5e68d5db1d
Error loading configuration file
Any ideas please?
Hi Victor,
Talked to you yesterday on Telegram and you directed me to this post, I've try this now but it failing to upgrade, see attached, any ideas please?
Thanks.
C:\NetXMS\bin>nxdbmgr check
NetXMS Database Manager Version 6.0.0 Build 6.0-444-gb145606172
Checking database (excluding collected data):
Your database has format version 60.7, this tool is compiled for version 60.30.
Use "upgrade" command to upgrade your database first.
Database check aborted
C:\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 6.0.0 Build 6.0-444-gb145606172
Upgrading database...
Upgrading from version 60.7 to 60.8
Converting table idata_100
SQL query failed ([Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot define PRIMARY KEY constraint on nullable column in table 'idata_100'.):
ALTER TABLE idata_100 ADD CONSTRAINT pk_idata_100 PRIMARY KEY (item_id,idata_timestamp)
Converting table tdata_100
SQL query failed ([Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot define PRIMARY KEY constraint on nullable column in table 'tdata_100'.):
....
.....
ALTER TABLE tdata_446 ADD CONSTRAINT pk_tdata_446 PRIMARY KEY (item_id,tdata_timestamp)
Converting table idata_450
SQL query failed ([Microsoft][ODBC Driver 18 for SQL Server][SQL Server]The transaction log for database 'NETXMS' is full due to 'ACTIVE_TRANSACTION' and the holdup lsn is (106450:128624:1).):
UPDATE idata_450 SET idata_timestamp = idata_timestamp * 1000
Rolling back last stage due to upgrade errors...
Database upgrade failed
C:\NetXMS\bin>
Hi Victor,
Thanks for the reply, I'm unsure on network issues, it's small, around 50 switches.
Will increases the poll count to 3 and see.
Thanks
Nick
Hi Victor,
Please see below for one client, went unreachable, major at 09:58:23, back to normal 10:00:42
Thanks
Nick
2023.05.31 09:56:11.912 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:56:11.912 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 09:57:16.994 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:57:18.292 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=2 RTT=0
2023.05.31 09:58:22.612 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:58:23.800 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=2 RTT=0
2023.05.31 09:59:33.326 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:59:33.326 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=2
2023.05.31 10:00:42.308 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:00:42.308 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:01:52.415 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:01:52.415 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=1
2023.05.31 10:02:57.539 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:02:57.539 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:04:02.641 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:04:02.641 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:05:07.675 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:05:07.675 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
Hi Victor,
Sorry I didn't see you had commented.
I've upped my poll count from the default of 1 to 2 but i'm still getting these messages?
See below
Hi, Does anyone know please??
Can I ask if this is still an issue please, our system will report in this order for example for most devices on a regular basis?
09:41:32 - SYS_ICMP_UNREACHABLE
09:41:32 - SYS_NODE_MAJOR
09:42:34 - SYS_ICMP_OK
09:42:34 - SYS_NODE_NORMAL
