Installation of Traccar working with H2 database failed to work with MYSQL

K6 years ago

I did the installation of Traccar on ubuntu 16.4 and it's working correctly when using H2 database. but when I change the traccar xml config file to use the service fail after a minute and I have the message below when checking the service status. And I can no more have access on the web page.

root@BDSERV:/opt/traccar/conf# service traccar status
* traccar.service - traccar
   Loaded: loaded (/etc/systemd/system/traccar.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-11-21 04:31:38 UTC; 21h ago
  Process: 865 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=1/FAILURE)
 Main PID: 865 (code=exited, status=1/FAILURE)

Nov 21 04:31:38 BDSERV traccar[865]:         at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:236)
Nov 21 04:31:38 BDSERV traccar[865]:         at liquibase.Liquibase.clearCheckSums(Liquibase.java:1455)
Nov 21 04:31:38 BDSERV traccar[865]:         at org.traccar.database.DataManager.initDatabaseSchema(DataManager.java:310)
Nov 21 04:31:38 BDSERV traccar[865]:         at org.traccar.database.DataManager.<init>(DataManager.java:90)
Nov 21 04:31:38 BDSERV traccar[865]:         at org.traccar.Context.init(Context.java:292)
Nov 21 04:31:38 BDSERV traccar[865]:         at org.traccar.Main.run(Main.java:110)
Nov 21 04:31:38 BDSERV traccar[865]:         ... 1 more
Nov 21 04:31:38 BDSERV systemd[1]: traccar.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 04:31:38 BDSERV systemd[1]: traccar.service: Unit entered failed state.
Nov 21 04:31:38 BDSERV systemd[1]: traccar.service: Failed with result 'exit-code'.

The log file show the information below

2019-11-21 04:25:08  INFO: SELECT `LOCKED` FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:25:08  INFO: Waiting for changelog lock....
2019-11-21 04:25:18  INFO: SELECT ID,`LOCKED`,LOCKGRANTED,LOCKEDBY FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:25:18 ERROR: Main method error - Could not acquire change log lock.  Currently locked by BDSERV.ip-51-255-74.eu (5.196.186.112) since 11/21/19, 3:50 AM - LockException (... < DataManager:310 < *:90 < Context:292 < Main:110 < ...)
2019-11-21 04:26:37  INFO: HikariPool-1 - Starting...
2019-11-21 04:26:37  WARN: Registered driver with driverClassName=com.mysql.jdbc.Driver was not found, trying direct instantiation.
2019-11-21 04:26:37  INFO: HikariPool-1 - Start completed.
2019-11-21 04:26:37  INFO: Clearing database change log checksums
2019-11-21 04:26:37  INFO: SELECT COUNT(*) FROM BDTRACK.DATABASECHANGELOGLOCK
2019-11-21 04:26:37  INFO: SELECT COUNT(*) FROM BDTRACK.DATABASECHANGELOGLOCK
2019-11-21 04:26:37  INFO: SELECT `LOCKED` FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:26:37  INFO: Waiting for changelog lock....
2019-11-21 04:26:47  INFO: SELECT `LOCKED` FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:26:47  INFO: Waiting for changelog lock....
...
2019-11-21 04:31:18  INFO: Waiting for changelog lock....
2019-11-21 04:31:28  INFO: SELECT `LOCKED` FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:31:28  INFO: Waiting for changelog lock....
2019-11-21 04:31:38  INFO: SELECT ID,`LOCKED`,LOCKGRANTED,LOCKEDBY FROM BDTRACK.DATABASECHANGELOGLOCK WHERE ID=1
2019-11-21 04:31:38 ERROR: Main method error - Could not acquire change log lock.  Currently locked by BDSERV.ip-.eu (ipaddress) since 11/21/19, 3:50 AM - LockException (... < DataManager:310 < *:90 < Context:292 < Main:110 < ...)
Anton Tananaev6 years ago

You have locked the database, most likely by restarting or killing service during schema migration process.