I am testing an upgrade from Bitbucket Server 4.14 to 5.2.2 on Windows. After the upgrade, Bitbucket fails to start because of a lack of permisions on the bitbucket.properties file. The ACLs are the same before and after the upgrade:
Granting the atlbitbucket account read access allows Bitbucket to start. Does this account require any other permissions? Why the change in required access in the new version?
Like all other content of the Bitbucket Home directory, all files should be owned by the user the Bitbucket service runs under, atlbitbucket by default.
I'm not sure why this was different before the upgrade and why it didn't work anymore after the upgrade, I'm afraid, but I'm glad you were able to find out yourself how to resolve this!
Premier Support Engineer
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs