Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,582
Community Members
 
Community Events
177
Community Groups

Crowd bootstrap error

Hello,

starting Crowd 3.3.3 I receive this fatal error currently.

Error while trying to initialise Crowd Container. liquibase.exception.LockException: Could not acquire change log lock. Currently locked by p200300E1D3E1734340F1C8E8C421456A.dip0.t-ipconnect.de (2003:e1:d3e1:7343:40f1:c8e8:c421:456a%enp0s31f6).

Crowd tomcat starts well w/o error message. Even shut down works out. But Crowd itself does not run anymore as the error shows above. It takes a long time after calling url to see this error message.

Does anybody have an idea how to fix? Thanks a lot in advance.

2 answers

1 accepted

0 votes
Answer accepted

Issue resolved by 'informal solution'.

Since testing instance appears to be identical, Crowd  installation folder as crowd-home and atlassian-crowd-x.x.x have been copied both from one to another user. Thanks to Unix :) Furthermore, chown and updating paths of Crowd  settings files.

Restart tomcat and it worked well.

This bug appeared simply because of having stupidly pressed Crtl + C at tomcat start. Thanks to ms win incorrigible behaviour.  

Good!

0 votes

Hi! 

Could you try that article? 

https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-does-not-start-could-not-acquire-change-log-lock-779171307.html

As I see you need to try reset lock. BTW, could you double check the status of your RDBMS ? 

 

Cheers,

Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events