We've looked at this issue https://confluence.atlassian.com/bitbucketserverkb/troubleshooting-connection-issues-for-elasticsearch-826900037.html and since we are seeing HTTP 401 Errors which is cause #2 we tried following the stops to stop and start the bitbucket webapp by calling the stop-server.sh and start-server.sh but there are a number of issues which prevent this solution from working.
1. The pid files do not exist
2. Sometimes even when the /var/atlassian/application-data/bitbucket/log/search/elasticsearch.pid file exists the stop-server.sh script reports that the file does not exist.
3. When they are created manually and then the stop-server.sh is called the bash session is terminated and then in our case the Kubernetes pod readiness probe determines that the bitbucket server is done and the pod is redeployed.
Given that the pid files do not exist which is a requirement for the troubleshooting process, what modifications should be made when running Bitbucket in docker and the elastic search (search in bitbucket) is not working due to 401 errors?
Here is the image info
Image ID: docker-pullable://atlassian/bitbucket-server@sha256:737d3e0016a0744f703846f61861bfd98a70873c1a95929e23906b17fc770905
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events