Have you checked logs? What other troubleshooting have you done before asking for help here?
This is the log:
2023-06-21 14:29:14 INFO: Operating system name: Linux version: 5.15.0-1031-azure architecture: amd64
2023-06-21 14:29:14 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Eclipse Adoptium version: 17.0.6+10
2023-06-21 14:29:14 INFO: Memory limit heap: 982mb non-heap: 0mb
2023-06-21 14:29:14 INFO: Character encoding: UTF-8 charset: UTF-8
2023-06-21 14:29:14 INFO: Version: 5.7
2023-06-21 14:29:14 INFO: Starting server...
2023-06-21 14:29:14 INFO: HikariPool-1 - Starting...
2023-06-21 14:29:15 INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2023-06-21 14:29:15 INFO: HikariPool-1 - Start completed.
2023-06-21 14:29:15 INFO: Set default schema name to PUBLIC
2023-06-21 14:29:15 INFO: Clearing database change log checksums
2023-06-21 14:29:15 INFO: Waiting for changelog lock....
2023-06-21 14:29:25 INFO: Waiting for changelog lock....
2023-06-21 14:29:35 INFO: Waiting for changelog lock....
2023-06-21 14:29:45 INFO: Waiting for changelog lock....
2023-06-21 14:29:55 INFO: Waiting for changelog lock....
2023-06-21 14:30:05 INFO: Waiting for changelog lock....
2023-06-21 14:30:15 INFO: Waiting for changelog lock....
2023-06-21 14:30:25 INFO: Waiting for changelog lock....
2023-06-21 14:30:35 INFO: Waiting for changelog lock....
2023-06-21 14:30:45 INFO: Waiting for changelog lock....
2023-06-21 14:30:55 INFO: Waiting for changelog lock....
I looked at different topics on the forum but couldn't find the solution
And this error is sometimes in logs before restart:
ERROR: Main method error - Could not acquire change log lock. Currently locked by dev-haikusushi (10.0.0.4) since 6/21/23, 1:25 PM - LockException (... < DatabaseModule:95 < <gener:-1 < *:-1 < ... < MainModule:123 < ...)
This has been discussed many times on the forum, so you should probably try searching again.
I searched a bit more and If i understand correctly my database has been locked and I should do this: update DATABASECHANGELOGLOCK
set locked = 0. Im not familiar with h2 databases, should I follow what redge76 wrote in this topic https://www.traccar.org/forums/topic/how-to-remove-lock-databasechangeloglock-default-h2-database/?
You should understand why and it got locked. Then if the schema migration is ok, you can release the lock manually.
It locked because I restarted the server during migration, right? How can I check if the schema migration is ok?
Check schema changelogs and check if all the changes applied to your database tables.
I added some configuration parameters to traccar.xml file on my server and after the website wouldn't work: This site can’t be reached. I changed the file back to it default configuration but the website still doesn't work.
My traccar.xml file:
<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'> <properties> <entry key='config.default'>./conf/default.xml</entry> <!-- This is the main configuration file. All your configuration parameters should be placed in this file. Default configuration parameters are located in the "default.xml" file. You should not modify it to avoid issues with upgrading to a new version. Parameters in the main config file override values in the default file. Do not remove "config.default" parameter from this file unless you know what you are doing. For list of available parameters see following page: https://www.traccar.org/configuration-file/ --> <entry key='database.driver'>org.h2.Driver</entry> <entry key='database.url'>jdbc:h2:./data/database</entry> <entry key='database.user'>sa</entry> <entry key='database.password'></entry> </properties>