NetXMS Support Forum

I've pushed 6.2.0-2, which have workaround for this issue.
Note: workaround only handles stock images, if any custom was uploaded and then deleted directly on the filesystem - upgrade will fail.

List of stock files:
092e4b35-4e7c-42df-b9b7-d5805bfac64e
1ddb76a3-a05f-4a42-acda-22021768feaf
7cd999e9-fbe0-45c3-a695-f84523b3a50c
904e7291-ee3f-41b7-8132-2bd29288ecc8
b314cf44-b2aa-478e-b23a-73bc5bb9a624
ba6ab507-f62d-4b8f-824c-ca9d46f22375
bacde727-b183-4e6c-8dca-ab024c88b999
f5214d16-1ab1-4577-bb21-063cfd45d7af
f9105c54-8dcf-483a-b387-b4587dfd3cba


Simplest approach for missing custom images - create empty file, e.g. "touch /var/lib/netxms/images/...".

Hello Alex,

thanks for the description. I tried that today, but running out of storage... :-(

Is there an function in nxdbmgr or any other tool for deleting all DCI Data in tables, so the tables has less amount of data so i can do the migration?

Greetings
Marco

Комрад на en части форума подсказал решение "на месте"
https://www.netxms.org/forum/index.php?msg=35566

litte workaround until the problem is official fixed:

download the 6.2.0 source package and extract all files (without Makefile*) from the 'images' subfolder of the archive to /var/lib/netxms/images

drop the column image_data in your database instance. in my case, with MySQL:
ALTER TABLE `images` DROP `image_data`;

running the "nxdbmgr upgrade" command again

Доброго дня

Ububntu 24.04.4 LTS
Обновился с 6.1.4 до 6.2.0 с apt. Сервис обновился, база - падает с ошибкой при апгрейде с nxdbmgr upgrade. До обновления check проводился.

NetXMS Database Manager Version 6.2.0 Build 6.2-471-gce46095f23

Upgrading database...
Upgrading from version 62.12 to 62.13
Cannot read image file "/var/lib/netxms/images/092e4b35-4e7c-42df-b9b7-d5805bfac64e"
Rolling back last stage due to upgrade errors...
Database upgrade failed
В логах
*E* [db                 ] Your database has format version 62.12, but server is compiled for version 62.30

Hello, I am trying to upgrade my NetXMS server from version 6.1.4 to 6.2.0 using the apt package manager and I am encountering the following issue when I attempt to upgrade the database before restarting the service. The service does not start after the upgrade because the database still has not been upgraded.

username@hostname:~$ sudo nxdbmgr upgrade
NetXMS Database Manager Version 6.2.0 Build 6.2-471-gce46095f23

Upgrading database...
Upgrading from version 62.12 to 62.13
Cannot read image file "/var/lib/netxms/images/092e4b35-4e7c-42df-b9b7-d5805bfac64e"
Rolling back last stage due to upgrade errors...
Database upgrade failed
username@hostname:~$

Thanks so much for your reply！
Here is the result：

root@XMNMS01:~# /usr/bin/nxsnmpwalk -v 2c -c stonewell2000 10.61.10.9 1.3.6.1.4.1.2011.5.25.42.4.1.19.1.2
huaweiDatacomm.42.4.1.19.1.2.0 [Hex-STRING]: 80 00 E4 DC CC 1A 59 61
root@XMNMS01:~# /usr/bin/nxsnmpwalk -v 2c -c stonewell2000 10.61.10.10 1.3.6.1.4.1.2011.5.25.42.4.1.19.1.2
huaweiDatacomm.42.4.1.19.1.2.0 [Hex-STRING]: 80 00 E4 DC CC 1A 59 61
root@XMNMS01:~# snmpwalk -v 2c -c stonewell2000 10.61.10.9 1.3.6.1.4.1.2011.5.25.42.4.1.19.1.2
Created directory: /var/lib/snmp/cert_indexes
iso.3.6.1.4.1.2011.5.25.42.4.1.19.1.2.0 = Hex-STRING: 80 00 E4 DC CC 1A 59 61
root@XMNMS01:~# snmpwalk -v 2c -c stonewell2000 10.61.10.10 1.3.6.1.4.1.2011.5.25.42.4.1.19.1.2
iso.3.6.1.4.1.2011.5.25.42.4.1.19.1.2.0 = Hex-STRING: 80 00 E4 DC CC 1A 59 61
root@XMNMS01:~#

Could you please also do SNMP walk on 1.3.6.1.4.1.2011.5.25.42.4.1.19.1.2 on both switches?

For XML error - I don't see it in current development version log, so changes are that it's already fixed, pls double-check when v.6.2 is out.

For MIB error - I guess MIB compiler is failing on some specific MIB file. You can try removing some of your MIB files until you find which one is causing the issue (you can remove half of them, recomplie, then another half, etc...). Or you can just share your whole MIB file collection.

Make sure that IP address in node's Properties -> Communications is correct.
Then run Configuration Poll on that node.

If it's still not working, try enabling debug, from Tools -> Server Console:

debug syslog 6

and check server log lines when your device sends something.