nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

All comments

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

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)

Kurt

Victor Tan

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

<span>UPDATE</span> DATABASECHANGELOGLOCK <span>SET</span> LOCKED<span>=</span><span>0</span><span>,</span> LOCKGRANTED<span>=</span><span>null</span><span>,</span> LOCKEDBY<span>=</span><span>null</span> <span>where</span> ID<span>=</span><span>1</span><span>;</span>

Alexander Künzer

me too, thanks!

Lukas Haigner

@Victor Tanyou just saved my day, thanks!

Frank Troglauer

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

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.

Xavier_b4j0mu

If anybody still running into this issue and DATABASECHANGELOGLOCK fix isnt working, it might be worth checking your NFS configuration. In my case, the issue was that bitbucket could not reach our NFS host because NFSv3 dynamically assigns ports for services like LOCKD(This was the culprit service). Here are the steps I took:

Check the messages in /var/log. In my case I saw this message -- kernel: lockd: NFS-HOST not responding, still trying.
Then I ran the diagnostic steps in this article - https://support.atlassian.com/bitbucket-data-center/kb/bitbucket-data-center-fails-to-start-with-a-lock-file-shared-lock-cannot-be-created-in-home-directory-error/#diagnosis. Sure enough, flock command was hanging.
Next, I went to my NFS host and ran the following command -- rpcinfo - p NFS-HOST. From the output I could see a port for the lockd service. Once I opened this port, and restarted bitbucket, it started successfully.

Robert Bzdafka

This was our issue as well. Had to remount NAS share with "nolock" option. Immediately fixed the issue.