Unable to create indexes on Bitbucket during starting.

Question

After updating my docker to the latest version of Bitbucket I can not start it anymore. The log shows me that a failure happened while creating the indexes but without any futher informations:

019-08-16 21:42:45,375 INFO  [Caesium-1-1]  c.a.b.i.s.i.jobs.StartupChecksJob Running startup jobs for search
2019-08-16 21:42:45,973 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Failed to create indexes: ''[Unknown error, Unknown error, Unknown error, Unknown error]''
2019-08-16 21:42:45,974 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Unable to synchronize the mapping in Elasticsearch

Does anybody had already the problem like this and maybe know how to solve it?

Many thanks

Silvan

boxstart · Answer

I had exactly the same problem after updating from Docker Bitbucket Server 6.3 to Docker Bitbucket Server 7.2.x. Tried all other options, but the following worked for me.

https://community.atlassian.com/t5/Bitbucket-questions/Bundled-elasticsearch-does-not-work-at-all-for-bitbucket-server/qaq-p/942796

This solution consists of copying the password from <bitbucket docker volume>/shared/search/buckler/buckler.yml to the settings for Elasticsearch in Bitbucket administration (Admin > Server Settings > Search > Elasticsearch password).

Silvan Meienberger_7zjvq4 · Answer

Hi Stephen

Thank you very much for you reply. Unfortunately from the first Link the Resolution #1 and #2 did not trigger the reindex. My solution was to delete the docker-container with all files and restore my files afterwards.

Regards

Silvan

Stephen Sifers · Answer

Hello Silvan and welcome to the Community!

Thanks for including details into the steps prior to your Bitbucket index problems. This type of issue can be a few things, we’ll focus on the most common ones first. You may either have corruption of your index which will need to be recreated. This can be done by following this: Rebuild the bundled Elasticsearch indexes for Bitbucket Server. Alternatively, another issue may be a connection issue with Bitbucket and the Elasticsearch itself. To troubleshoot a connection issue with the index please see Troubleshooting Connection Issues for Elasticsearch.

Please let us know if these assisted with the issue or if it’s still present.

Regards,
Stephen Sifers