Liquibase locked, how to resolve? Using latest compreface.

[atv2016]

Describe the bug

compreface-admin | 2023-10-04 15:02:42.781 INFO 7 --- [ main] liquibase.lockservice : Waiting for changelog lock....
compreface-ui | 2023/10/04 15:02:51 [error] 27#27: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.

To Reproduce

Steps to reproduce the behavior:

Don't know

Expected behavior

Not to give that error

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Logs

Run those commands and attach result to the ticket:

docker ps

docker-compose logs

Additional context

Add any other context about the problem here.

[atv2016]

@pospielov Not sure how this happened - i think i need to unlock the postgres db ? How does one do this ?

[atv2016]

Ok i resolved this by doing:
docker exec -it containerid /bin/bash
pqsql -u psql
\c frs
UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null where ID=1;

and i could login again.

[ghzgod]

For anyone running postgresql in a container that isn't compreface I ran this command

docker exec -it POSTGRESQL_CONTAINER_NAME psql -U compreface -d compreface -c "UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null WHERE ID=1;"

[SgtBatten]

Thanks, this got me going again on unraid with dockercompose setup

Open terminal in the postgres container

Login as username postgres

psql -U postgres

open the database named frs

\c frs

Unlock the thing

UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null where ID=1;