Server won't start after upgrade to 5.8

Deboraha year ago

Hi,

My server won't start after doing the upgrade.
The logs tell me this:

2023-06-06 08:51:25  INFO: Operating system name: Linux version: 6.1.28-v8+ architecture: arm
2023-06-06 08:51:26  INFO: Java runtime name: OpenJDK Server VM vendor: Raspbian version: 11.0.18+10-post-Raspbian-1deb11u1
2023-06-06 08:51:26  INFO: Memory limit heap: 950mb non-heap: 0mb
2023-06-06 08:51:26  INFO: Character encoding: UTF-8 charset: UTF-8
2023-06-06 08:51:26  INFO: Version: 5.8
2023-06-06 08:51:26  INFO: Starting server...
2023-06-06 08:51:27  INFO: HikariPool-1 - Starting...
2023-06-06 08:51:29  INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2023-06-06 08:51:29  INFO: HikariPool-1 - Start completed.
2023-06-06 08:51:30  INFO: Set default schema name to PUBLIC
2023-06-06 08:51:30  INFO: Clearing database change log checksums
2023-06-06 08:51:31  INFO: Waiting for changelog lock....
2023-06-06 08:51:41  INFO: Waiting for changelog lock....
2023-06-06 08:51:51  INFO: Waiting for changelog lock....
2023-06-06 08:52:01  INFO: Waiting for changelog lock....
2023-06-06 08:52:11  INFO: Waiting for changelog lock....
2023-06-06 08:52:21  INFO: Waiting for changelog lock....
2023-06-06 08:52:31  INFO: Waiting for changelog lock....
Deboraha year ago

I solved it. I saw in another post that the error refers to the corrupted DB.
Restoring a backup fixed it

Silverweba year ago

how exactly did you solve the problem? can not fix the same trouble. thx

Deboraha year ago

I simply retrieved the database backup of the "data" folder and it started working again

simplementesea year ago

It's an old thread, it's on the forum. It's not damaged. Crashes on update. you just have to unlock it

update DATABASECHANGELOGLOCK set locked=0 WHERE ID=1