Error 503 after start. ("Waiting for changelog lock..." at logs)

Modified on Tue, 4 Apr, 2023 at 7:43 AM

This is related to a database lock. Service cannot get the access to the database.

You can see logs by running:

docker-compose logs -f

Cause: this issue can be caused by unexpected service restart due to infrastructure or severe network malfunction.

Solution: Follow the steps described below:
You can see all the services by running:

docker-compose ps

1. Stop all services that are not DB related, e.g. :

docker-compose stop allure-gateway allure-uaa allure-report

2. Now we need to find out the ID of the container where our desired base is located:

docker ps

3. Now we can access to database:
(psql -h <host> -U <user> <database>)

docker exec -it <containder id> psql -h 127.0.0.1 -U report report

4. Get the content of the table containing locks data:

select * from databasechangeloglock;

5. Delete the lock preventing a service to start:

update databasechangeloglock set locked=false, lockgranted=null, lockedby=null where id=1;

6.Start the services stopped on the step #1.