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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,956
Community Members
 
Community Events
176
Community Groups

Elasticsearch not starting automatically after update of Bitbucket to 7.6.14

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

2 answers

1 accepted

0 votes
Answer accepted

Hi Stephan,

Did you use the installer to install 7.6.14 or did you use the zip or tar file?

Cheers,

Christian

Premier Support Engineer

Atlassian

Hello!

I used the installer.

BR

Stephan

Is there any chance you selected to install Data Center when running the installer? In that situation it would expected that ES is not started together with Bitbucket.

Cheers,

Christian

Premier Support Engineer

Atlassian

True, I chose Data Center because that is the license that we run. And we run the package in standalone mode. So it is a feature, not a bug?

Yep, that's expected because with a multi-node DC deployment you'll need to have your own installation of Elasticsearch on a separate machine.

Cheers,

Christian

Premier Support Engineer

Atlassian

Like Stephan Krull likes this

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events