starting bitbucket hangs on "migrating home directory"

[Victor Tan]

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?

[Kurt Klinner]

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

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;

[Alexander Künzer]

me too, thanks!

[Lukas Haigner]

@Victor Tanyou just saved my day, thanks!

[LukaszK]

Worked for me as well! Many thanks Victor! 

[Mike Ellertson]

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

[Mike Ellertson]

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;

[yigang wang]

thanks 

[jjames]

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

[albertogisbert]

You save my day. Thanks!

[DP_Technology]

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]

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

[Michael Knopf]

This fixed my issue too on Bitbucket version 7.19.1

[Geoffrey Falade]

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]

Had to use false for the boolean.

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

[Augusto Leite Pinte De Carvalho]

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.

[Victor Tan]

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]

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