nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error after Bitbucket 7.18.3 upgrade.

Khang Pham_ujflk3

I am relatively new to administering Bitbucket and would like some input. I have just upgraded bitbucket from 6.10 to 7.18.3. The upgrade itself seems okay, however upon starting the bitbucket service, I noticed that there are 2 logs which caught my eye and wondering if these are of any concern:

1. /opt/atlassian/bitbucket/7.18.3/elasticsearch/bin/elasticsearch: line 43: bin/elasticsearch-keystore: Permission denied

Is anyone able to clarify what the elasticsearch-keystore does? I have checked the permissions on it and confirmed it has the same permissions as the user starting the bitbucket service.

2. The current open files limit is set to less than 6192
Attempting to increase limit...
/opt/atlassian/bitbucket/7.18.3/bin/_start-webapp.sh: line 63: ulimit: open files: cannot modify limit: Operation not permitted

I believe this is used for admin to set resource usage, however not too sure what particular error indicates.

Anyone able to explain the 2 errors and possible fix for them? Should these be of any concern?

I've tried looking for these errors in the KBs but not much luck.

Accepted answers

Nic Brough -Adaptavist-

Elastic is the search system underneath bitbucket. The file you're looking at holds keys for encrypted access.

The errors you are getting are happening because your server is not set up correctly. The Linux user running the service does not have the right permissions.

This usually happens when someone starts the service while being root, instead of starting it as the user dedicated to running bitbucket, then stops it, and restarts it as the right user. The process run as root takes ownership of files and directories, making them inaccessible to the actual owner.

You should be able to fix this by stopping bitbucket and using chown -R user:group /opt/atlassian/bitbucket

For your second error, it might be a hangover from the first, but if it is not, then you'll need to increase the file limit for the user running bitbucket. Edit the /etc/security/limits.conf file

Craig Steadman

Change into the folder and double check the rights on the files and also see if the will execute manually. The line 43: bin/elasticsearch-keystore: Permission denied error cleared up for me after give the files execute rights.

All comments

Nic Brough -Adaptavist-

Elastic is the search system underneath bitbucket. The file you're looking at holds keys for encrypted access.

The errors you are getting are happening because your server is not set up correctly. The Linux user running the service does not have the right permissions.

You should be able to fix this by stopping bitbucket and using chown -R user:group /opt/atlassian/bitbucket

For your second error, it might be a hangover from the first, but if it is not, then you'll need to increase the file limit for the user running bitbucket. Edit the /etc/security/limits.conf file

Khang Pham_ujflk3

Hi Nic,

The permissions on Bitbucket installation are the default permissions set by the Bitbucket installer being atlbitbucket:atlbitbucket under /opt/atlassian/bitbucket. I have also confirmed the start-bitbucket.sh permissions is set as atlbitbucket:atlbitbucket.

When I ran the start script, I performed sudo -u atlbitbucket ./start-bitbucket.sh to start the service. This should've started the bitbucket service as atlbitbucket but unfortunately, the error still occurs once the service starts. Is there anything else I need to check for this?

Craig Steadman

Check the execute permissions on the files in elasticsearch/bin folder

chmod 750 /opt/atlassian/bitbucket/7.xx.x/elasticsearch/bin/*

note: set your version in the command string above

Khang Pham_ujflk3

Hi @Craig Steadman

I just changed the permissions in the elasticsearch/bin folder as you suggested to all execute, and ran the service again. Unfortunately, still getting the same 2 errors.

Khang Pham_ujflk3

Any other ideas @Nic Brough -Adaptavist- I can check?

Craig Steadman

Khang Pham_ujflk3

The permissions are correctly assigned to the elasticsearch. After stopping the service and running it manually, it gave me a java error, but after starting the bb service again, the line 43: bin/elasticsearch-keystore: Permission denied error is no longer appearing!