Elasticsearch not starting automatically after update of Bitbucket to 7.6.14

[Stephan Krull]

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

[Christian Glockner · Accepted solution]

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

[Stephan Krull]

Hello!

I used the installer.

BR

Stephan

[Christian Glockner]

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

[Stephan Krull]

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?

[Christian Glockner]

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

[Stephan Krull]

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