You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I updated a Bitbucket instance from 7.6.2 to 7.6.14 yesterday. Recognized later that the bundled Elasticsearch sub process has not been started by the start up scripts. That was the case until the upgrade, so elasticsearch has always been started by the parental Bitbucket process before.
I think I found the root cause:
- the installer file for the Bitbucket upgrade on Linux changed the /etc/rc.d/init.d/atlbitbucket file and calls "/opt/atlassian/bitbucket/7.6.14/bin/start-bitbucket.sh --no-search", which, of course, prevents the elasticsearch process from starting
Any idea why this has been introduced? I did not find anything in the release notes: https://confluence.atlassian.com/bitbucketserver/bitbucket-server-7-6-release-notes-1018780800.html
I additionally asked via support request and got this documentation link about the issue, just for completeness: https://community.atlassian.com/t5/Bitbucket-questions/Elasticsearch-not-starting-automatically-after-update-of/qaq-p/1995708#M80531