Upgrading to 5.8 results to startup failure

memesaregooda year ago

Hello,

We've upgraded Traccar from 5.7 to 5.8, and it fails to start now.
Error log:

2023-06-09 10:59:12  INFO: Operating system name: Linux version: 5.15.0-71-generic architecture: amd64
2023-06-09 10:59:12  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Private Build version: 17.0.6+10-Ubuntu-0ubuntu122.04
2023-06-09 10:59:12  INFO: Memory limit heap: 6144mb non-heap: 0mb
2023-06-09 10:59:12  INFO: Character encoding: UTF-8 charset: UTF-8
2023-06-09 10:59:12  INFO: Version: 5.8
2023-06-09 10:59:12  INFO: Starting server...
2023-06-09 10:59:12  INFO: HikariPool-1 - Starting...
2023-06-09 10:59:13  INFO: HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@3ecedf21
2023-06-09 10:59:13  INFO: HikariPool-1 - Start completed.
2023-06-09 10:59:13  INFO: Set default schema name to public
2023-06-09 10:59:13  INFO: Clearing database change log checksums
2023-06-09 10:59:13  INFO: Successfully acquired change log lock
2023-06-09 10:59:13  INFO: Successfully released change log lock
2023-06-09 10:59:13  INFO: Successfully acquired change log lock
2023-06-09 10:59:15  INFO: Reading from public.databasechangelog
2023-06-09 10:59:15  INFO: Reading from public.databasechangelog
2023-06-09 10:59:15  INFO: Using deploymentId: 6297555892
2023-06-09 10:59:16  INFO: Reading from public.databasechangelog
2023-06-09 10:59:16 ERROR: ChangeSet changelog-5.8::changelog-5.8::author encountered an exception.
2023-06-09 10:59:16  INFO: Update command encountered an exception.
2023-06-09 10:59:16  INFO: Successfully released change log lock
2023-06-09 10:59:16  INFO: Successfully released change log lock
2023-06-09 10:59:16  INFO: Command execution complete
2023-06-09 10:59:16 ERROR: Main method error - ERROR: column "geofenceids" of relation "tc_devices" does not exist - PSQLException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < MainModule:123 < ..

Rolling back to 5.7 helps and everything has returned back to normal, however we can't seem to upgrade to 5.8.
A separate test instance, however, was upgraded without any issues.

What would be the recommended course of action?

Thank you

Nikolay a year ago
memesaregooda year ago

Thanks for the info, however the upgrade procedure was done according to the article. This has no use for us now.

Anton Tananaeva year ago

I don't see database schema migration in your log, which means that either you're not showing the right fragment from the log or you didn't do the upgrade correctly.

Cris Amendea year ago

Had the same issue this morning.
Logging into the database and manually changing the name of column geofenceIds in tc_devices to geofenceids fixed the issue.
Having said that, could still be that the upgrade was not done correctly...

Macana year ago

I have the same issue, did you solve it ?

memesaregood10 months ago

Please read Cris Amende's message carefully.

HellComment3 months ago

had same issue going from 5.3 to 5.12.. I had to manually change the database field as Cris mentioned.