V5.3 error after upload database v.5.2, traccar not work
Have you tried existing solution from a number of thread about the same problem?
no, please you have a link?
Just one example out of many:
https://www.traccar.org/forums/topic/liquibase-waiting-for-changelog-lock/
Anton i have used this command update DATABASECHANGELOGLOCK set locked = 0;
NOT WORK
log
2022-08-31 21:25:12 INFO: Version: 5.3
2022-08-31 21:25:12 INFO: Starting server...
2022-08-31 21:25:13 INFO: HikariPool-1 - Starting...
2022-08-31 21:25:14 INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@1c65121
2022-08-31 21:25:14 INFO: HikariPool-1 - Start completed.
2022-08-31 21:25:15 INFO: Clearing database change log checksums
2022-08-31 21:25:16 INFO: Successfully acquired change log lock
2022-08-31 21:25:17 INFO: Successfully released change log lock
2022-08-31 21:25:17 INFO: Successfully acquired change log lock
2022-08-31 21:25:17 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-08-31 21:25:17 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-08-31 21:25:21 INFO: Reading from traccar.DATABASECHANGELOG
2022-08-31 21:25:22 INFO: Reading from traccar.DATABASECHANGELOG
2022-08-31 21:25:22 INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-08-31 21:25:22 INFO: Successfully released change log lock
2022-08-31 21:25:22 ERROR: Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)
2022-08-31 21:25:35 INFO: Operating system name: Linux version: 4.15.0-191-generic architecture: amd64
2022-08-31 21:25:35 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.15+10-LTS
2022-08-31 21:25:35 INFO: Memory limit heap: 483mb non-heap: 0mb
2022-08-31 21:25:35 INFO: Character encoding: UTF-8 charset: UTF-8
2022-08-31 21:25:35 INFO: Version: 5.3
2022-08-31 21:25:35 INFO: Starting server...
2022-08-31 21:25:35 INFO: HikariPool-1 - Starting...
2022-08-31 21:25:37 INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@1c65121
2022-08-31 21:25:37 INFO: HikariPool-1 - Start completed.
2022-08-31 21:25:38 INFO: Clearing database change log checksums
2022-08-31 21:25:38 INFO: Successfully acquired change log lock
2022-08-31 21:25:39 INFO: Successfully released change log lock
2022-08-31 21:25:39 INFO: Successfully acquired change log lock
2022-08-31 21:25:39 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-08-31 21:25:39 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructorFor update database from version 4.15 to 5.2 no problem, its works
You should probably revert to the backup first because the migration has been partially done, so you're stuck in an invalid state.
first backup from 5.2 and after update backup on versione 5.3?
Doesn't matter. You shouldn't need to upgrade one by one.
YOU: You should probably revert to the backup first because the migration has been partially done, so you're stuck in an invalid state.
Please What steps do I have to follow to do what you say?
What backup do you have? Revert the database to that and start Traccar again.
backup from version 4.15, I did the database restore with command mysql -u root -p traccar < traccar.sql, but it doesn't work, in version 5.2 everything ok, in 5.3 it doesn't work
Have you run it on the original backup? What's the error? What you provided last time is not the original log. You get "Duplicate column name 'fixedemail'" only if the migration already failed once.
ok,thank you
solutions?