We had a server that crashed during a ligthning storm. I had to recover it from a backup, but now it looks like the database is not working as it should. Can anyone see what I should do (all the units are gone)?:
2021-07-07 14:38:42 INFO: HikariPool-1 - Starting...
2021-07-07 14:38:45 INFO: HikariPool-1 - Start completed.
2021-07-07 14:38:45 INFO: Clearing database change log checksums
2021-07-07 14:38:52 INFO: Successfully acquired change log lock
2021-07-07 14:38:53 INFO: Creating database history table with name: PUBLIC.DATABASECHANGELOG
2021-07-07 14:38:53 INFO: Successfully released change log lock
2021-07-07 14:38:53 INFO: Successfully acquired change log lock
2021-07-07 14:38:53 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2021-07-07 14:38:53 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2021-07-07 14:39:01 INFO: Reading from PUBLIC.DATABASECHANGELOG
2021-07-07 14:39:04 INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2021-07-07 14:39:04 INFO: Table tc_attributes created
2021-07-07 14:39:04 INFO: Table tc_calendars created
2021-07-07 14:39:04 INFO: Table tc_commands created
2021-07-07 14:39:04 INFO: Table tc_device_attribute created
2021-07-07 14:39:04 INFO: Table tc_device_command created
...
2021-07-07 14:39:07 INFO: Columns announcement(VARCHAR(4000)) added to tc_servers
2021-07-07 14:39:07 INFO: ChangeSet changelog-4.11::changelog-4.11::author ran successfully in 0ms
2021-07-07 14:39:07 INFO: Column tc_events.servertime renamed to eventtime
2021-07-07 14:39:07 INFO: ChangeSet changelog-4.13::changelog-4.13::author ran successfully in 0ms
2021-07-07 14:39:07 INFO: Successfully released change log lock
2021-07-07 14:39:16 INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2021-07-07 14:39:22 INFO: Operating system name: Windows Server 2016 version: 10.0 architecture: amd64
2021-07-07 14:39:22 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.9+11-LTS
2021-07-07 14:39:23 INFO: Memory limit heap: 1024mb non-heap: 0mb
2021-07-07 14:39:23 INFO: Character encoding: Cp1252 charset: windows-1252
2021-07-07 14:39:23 INFO: Version: 4.13
2021-07-07 14:39:23 INFO: Starting server...
2021-07-07 14:39:25 INFO: jetty-10.0.3; built: 2021-05-20T21:15:05.272Z; git: 60d766fc285ea66840ebc5be4598d43ec325055d; jvm 11.0.9+11-LTS
Looks like your database was empty. Are you sure you restored it?
Hi Anton
Yes there was a strange problem with the database files, I've finally solved it.
It is a HyperV server and I restored the hole server / virtual HDD. The problem was when the restored server startet up. I ended up with extracting the databasefiles manual from the backup and copy them to the restored server after I stopped the Traccar service. After some very long minutes, everything was up and running again!
Thanks for your help!
We had a server that crashed during a ligthning storm. I had to recover it from a backup, but now it looks like the database is not working as it should. Can anyone see what I should do (all the units are gone)?: