Server not starting after upgrading from 4.5.6 to 5.0.2

[deepb]

Hi,

I upgraded from 4.5.6 to 5.0.2 and NetXMS server refuses to start. I'm using MariaDB 10.4. 

Your database has format version 50.32, but server is compiled for version 50.39

Running  nxdbmgr.exe upgrade has no effect/output either.

C:\NetXMS\bin>nxdbmgr.exe upgrade
NetXMS Database Manager Version 5.0.2 Build 5.0-878-gccaeca5869 (UNICODE)

Upgrading database...
Upgrading from version 50.32 to 50.33

C:\NetXMS\bin>

Please help.

[alk]

Check windows event log, maybe nxdbmgr crashed

[deepb]

Windows event logs have the below MariaDB error:

Aborted connection 40 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets) 

Do I have to upgrade MariaDB?

Please help in resolving this issue.

[alk]

Check MariaDB logs, it looks like a database problem (maybe just out of space?)

[deepb]

No error in MariaDB...

2024-05-13 16:46:02 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe (initiated by: unknown): Normal shutdown
2024-05-13 16:46:02 0 [Note] Event Scheduler: Purging the queue. 0 events
2024-05-13 16:46:02 0 [Note] InnoDB: FTS optimize thread exiting.
2024-05-13 16:46:02 0 [Note] InnoDB: Starting shutdown...
2024-05-13 16:46:02 0 [Note] InnoDB: Dumping buffer pool(s) to C:\Program Files\MariaDB 10.4\data\ib_buffer_pool
2024-05-13 16:46:02 0 [Note] InnoDB: Instance 0, restricted to 16054 pages due to innodb_buf_pool_dump_pct=25
2024-05-13 16:46:02 0 [Note] InnoDB: Buffer pool(s) dump completed at 240513 16:46:02
2024-05-13 16:46:04 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-13 16:46:04 0 [Note] InnoDB: Shutdown completed; log sequence number 12673536826768; transaction id 626221754
2024-05-13 16:46:04 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: Shutdown complete

2024-05-13 16:46:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-13 16:46:04 0 [Note] InnoDB: Uses event mutexes
2024-05-13 16:46:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-05-13 16:46:04 0 [Note] InnoDB: Number of pools: 1
2024-05-13 16:46:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-13 16:46:04 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2024-05-13 16:46:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-13 16:46:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-13 16:46:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-13 16:46:07 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-13 16:46:07 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2024-05-13 16:46:07 0 [Note] InnoDB: Waiting for purge to start
2024-05-13 16:46:07 0 [Note] InnoDB: 10.4.25 started; log sequence number 12673536826768; transaction id 626221755
2024-05-13 16:46:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 10.4\data\ib_buffer_pool
2024-05-13 16:46:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-13 16:46:07 0 [Note] Server socket created on IP: '::'.
2024-05-13 16:46:07 0 [Note] Reading of all Master_info entries succeeded
2024-05-13 16:46:07 0 [Note] Added new Master_info '' to hash table
2024-05-13 16:46:07 0 [Note] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: ready for connections.
Version: '10.4.25-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2024-05-13 16:46:22 8 [Warning] Aborted connection 8 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)
2024-05-13 16:47:00 0 [Note] InnoDB: Buffer pool(s) load completed at 240513 16:47:00
2024-05-13 16:48:20 9 [Warning] Aborted connection 9 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)
2024-05-13 16:49:23 10 [Warning] Aborted connection 10 to db: 'netxms' user: 'netxms' host: 'localhost' (Got an error reading communication packets)

I didn't keep a database backup. I don't know what to do now!!

This upgrade has proved to be too costly for me.

[victor]

So the problem is in upgrade (similar to what was reported on other thread). We will publish 5.0.3 today or tomorrow, hopefully this will be fixed by that moment.

Best regards,
Victor

[victor]

We just fixed bug in database upgrade, we will start packing release 5.0.3 soon.

Best regards,
Victor

[victor]

Windows server binaries for version 5.0.3 already in archive, we will update web site and publish deb packages during the day.

Best regards,
Victor