Puzzling liquibase error after upgrading to traccar 4.13, openjdk-11

Jon Williams3 years ago

I recently performed an upgrade from 4.11 to 4.13, which also necessitated an upgrade in java (I went from oracle-8-jre to openjdk-11).

The upgrade appears to have worked - Traccar server starts up and I can see historical route data via the web front-end

On inspecting the log files I can see some errors with liquibase however (see below)

2021-06-24 10:01:43  INFO: HikariPool-1 - Starting...
2021-06-24 10:01:46  INFO: HikariPool-1 - Start completed.
2021-06-24 10:01:47  INFO: Clearing database change log checksums
2021-06-24 10:01:48  INFO: Successfully acquired change log lock
2021-06-24 10:01:51  INFO: Successfully released change log lock
2021-06-24 10:01:51  INFO: Successfully acquired change log lock
2021-06-24 10:01:51  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2021-06-24 10:01:51  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2021-06-24 10:02:01  INFO: Reading from PUBLIC.DATABASECHANGELOG
2021-06-24 10:02:05  INFO: Reading from PUBLIC.DATABASECHANGELOG
2021-06-24 10:02:05  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2021-06-24 10:02:05  INFO: Successfully released change log lock
2021-06-24 10:02:11  INFO: Operating system name: Linux version: 4.19.66-v7+ architecture: arm
2021-06-24 10:02:11  INFO: Java runtime name: OpenJDK Server VM vendor: Debian version: 11.0.6+10-post-Debian-1bpo91
2021-06-24 10:02:11  INFO: Memory limit heap: 224mb non-heap: 0mb
2021-06-24 10:02:11  INFO: Character encoding: UTF-8 charset: UTF-8
2021-06-24 10:02:11  INFO: Version: 4.13
2021-06-24 10:02:11  INFO: Starting server...

Should I be worried? On the one hand everything appears to be working OK, but I dont want to ignore a problem.

Thanks for all assistance!

Anton Tananaev3 years ago

No, you shouldn't worry about it.

Jon Williams3 years ago

Thank you for the prompt reply Anton.

I'm assuming I have not done anything dumb - but please dont be afraid to tell me if I have.

Anton Tananaev3 years ago

Nah, I think we also see the same message. Note that log level is INFO, so it's not technically an error. Just some informational message from the library. We don't use json or yaml change logs anyway. We use XML.