Traccar server stopped working after WHM update

akiosdev4 years ago

My traccar server stopped working after a cpanel/whm update

the logs are spamming these messages:

 ERROR: Main method error - Could not acquire change log lock.  Currently locked by traccar (172.17.0.2) since 8/30/20 1:34 PM - LockException (... < DataManager:310 < *:90 < Context:292 < Main:137 < ...)
2020-08-30 13:58:01  INFO: HikariPool-1 - Starting...
2020-08-30 13:58:01  INFO: HikariPool-1 - Start completed.
2020-08-30 13:58:02  INFO: Clearing database change log checksums
2020-08-30 13:58:02  INFO: SELECT COUNT(*) FROM scootrac_traccar.DATABASECHANGELOGLOCK
2020-08-30 13:58:02  INFO: SELECT COUNT(*) FROM scootrac_traccar.DATABASECHANGELOGLOCK
2020-08-30 13:58:02  INFO: SELECT `LOCKED` FROM scootrac_traccar.DATABASECHANGELOGLOCK WHERE ID=1
2020-08-30 13:58:02  INFO: Waiting for changelog lock....
2020-08-30 13:58:12  INFO: SELECT `LOCKED` FROM scootrac_traccar.DATABASECHANGELOGLOCK WHERE ID=1
2020-08-30 13:58:12  INFO: Waiting for changelog lock....
2020-08-30 13:58:22  INFO: SELECT `LOCKED` FROM scootrac_traccar.DATABASECHANGELOGLOCK WHERE ID=1
2020-08-30 13:58:22  INFO: Waiting for changelog lock....
2020-08-30 13:58:32  INFO: SELECT `LOCKED` FROM scootrac_traccar.DATABASECHANGELOGLOCK WHERE ID=1
2020-08-30 13:58:32  INFO: Waiting for changelog lock....

ps: I also noticed that the docker container changed the IP address for some reason, and I had to put the new IP address on allow list for remote access, but still doesnt work.

akiosdev4 years ago

UPDATE:

this new error message from docker logs:

Exception in thread "main" java.lang.RuntimeException: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by traccar (container-ip-address-here) since 8/30/20 1:34 PM
Anton Tananaev4 years ago

Have you tried searching the forum? This issue has been discussed multiple times before.

akiosdev4 years ago

so the best solution is really to set the variable to 0 manually in the database through a SQL command?

Anton Tananaev4 years ago

The best solution is to audit your database schema to make sure it's correct... and then set it to 0.