Starting Bitbucket Server/Data Center with service script after upgrade using archive file starts older version
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After performing Bitbucket upgrade using archive file, starting Bitbucket using service scripts starts older version.
Environment
All
Diagnosis
When trying to start the Bitbucket service using a service script (systemd, init.d etc) after performing upgrade of your Bitbucket Server instance using manual archive file method, it starts the older version of Bitbucket instead of the new upgraded one.
Cause
When performing upgrade using the Bitbucket installer, the installer script takes care of updating the relevant service scripts with the path to the installation folder of the new Bitbucket version. However this will not be the case when performing the upgrade manually using archive file.
If there is a service script present for Bitbucket that has been installed either from a previous installer or by manual creation, make sure to update the service script to point to the new Bitbucket version installation directory when installing the new version using archive file.
Solution
Update the Bitbucket start and stop script path in the service file as shown below.
If you are using the Linux init.d service script, this will be located at /etc/init.d/atlbitbucket
Was this helpful?