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

starting bitbucket hangs on "migrating home directory"

Victor Tan April 30, 2018

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
Kurt Klinner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 30, 2018

@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

Victor Tan April 30, 2018

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
Alexander Künzer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 3, 2018

me too, thanks!

Lukas Haigner August 10, 2018

@Victor Tanyou just saved my day, thanks!

LukaszK
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 3, 2018

Worked for me as well! Many thanks Victor! 

Mike Ellertson December 20, 2018

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

Mike Ellertson December 20, 2018

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
yigang wang
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2019

thanks 

jjames
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 29, 2019

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

Like Mike_Ellertson likes this
albertogisbert
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 22, 2019

You save my day. Thanks!

DP_Technology
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 16, 2020

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.

MartinB
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2020

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

Michael Knopf December 21, 2021

This fixed my issue too on Bitbucket version 7.19.1

Geoffrey Falade May 9, 2022

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.

Mike Quentel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2022

Had to use false for the boolean.

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

 

0 votes
Augusto Leite Pinte De Carvalho March 3, 2022

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.

0 votes
Victor Tan April 30, 2018

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]:

Frank Troglauer May 28, 2020

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events