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,463,710
Community Members
 
Community Events
176
Community Groups

starting bitbucket hangs on "migrating home directory"

running version 5.5.1 on windows 2012 server.  server was rebooted and when I start the bitbucket service, it got stuck in "migrating home directory".  been like this for several hours.  What should I do?

3 answers

3 votes

@Victor Tan

 

Hi Victor, sound like https://community.atlassian.com/t5/Bitbucket-questions/Problem-with-bitbucket-startup/qaq-p/708444

 

Can you provide more details out of the log file (the whole stacktrace for example)

 

BR

Kurt

Not sure if it is the same issue but I fixed it buy doing an update on the database table.

 

UPDATE DATABASECHANGELOGLOCK SET LOCKED=0, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
Like # people like this

@Victor Tanyou just saved my day, thanks!

Worked for me as well! Many thanks Victor! 

Worked for me too.  Thanks!  I was afraid I would need to re-install!

BTW, on Bitbucket v5.15.0 and running on Postgres, had to use the following sql command:

UPDATE DATABASECHANGELOGLOCK SET LOCKED=False, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
Like # people like this

Thanks for that one SQL line: I've been stuck for over a day!

Like Mike_Ellertson likes this

You save my day. Thanks!

Same for me, unexpected lock and this fix worked well on the upgrade from 6.1.2 to 6.9.1 of our server. Just delivered the upgrade on time, ooooh. Thanks a lot.

Worked for Bitbucket 7.2.1 after a vmware snapshot left the database locked.

This fixed my issue too on Bitbucket version 7.19.1

Rather than blindly updating this table, can someone explain why this occurred and why this fix is reasonable? At the surface, it feels like a band-aid fix that may have undesirable effects, but could have a completely reasonable explanation.

Had to use false for the boolean.

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

 

We had this issue during servers reboot (bitbucket 7.17.5 and PostgreSQL).

The errors was not clear in logs. Difficult to debug it. 

Solved with the DATABASECHANGELOGLOCK update.

after waiting for a very long time, finally got this error.

 

A fatal error has occurred

The following problem occurred, which prevents Atlassian Bitbucket from starting:

  • SpringMVC dispatcher [springMvc] could not be started

 

in the log

 

Error creating bean with name 'sharedHomeLockAcquirer' defined in class path resource [stash-context.xml]:

I got this error as well Victor. How did you resolve it?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events