You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a constant log errors after updating the confluence, hoging the server
2022-01-19 08:53:18,084 ERROR [Caesium-1-1] [migration.agent.queue.QueueBroker] error An error occurred when getting the next batch for consumer type: CONFLUENCE_IMPORT. Message: javax.persistence.PersistenceException: Failed to update database schema
Caused by: javax.persistence.PersistenceException: Failed to update database schema
Caused by: liquibase.exception.LockException: Could not acquire change log lock. Currently locked by atlassian-confluence-server_7.9.3 (172.17.0.2) since 1/19/22 8:07 AM
And this is on a lot of tables not just the one given for example. And i have few times done in postgree on confluence db:
UPDATE MIG_DB_CHANGELOG_LOCK SET LOCKED=false, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
and after i do this the logs still say it is locked eventhough i see that select of the table says it is updated ok and no change after update.
How can we solve this?
Thank you!
Here's the KB Article for the observed error
Let me know if you have already tried this one
Thanks,
Pramodh
UPDATE MIG_DB_CHANGELOG_LOCK SET LOCKED=false, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
many times...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alen Loncaric We're running into this issue. Were you able to resolve?
ran the above command as well; still nothing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.