Critical - Bitbucket server down

[Hovig Deveijan]

We just performed an upgrade to 5.11.1 primarily to take advantage of a plugin that removes the approval should user make any commits post approval.

Upgrade succeeded, however the bitbucket service starts and stops.  Nothing useful was showing up in the event viewer and we need to get this operational ASAP for our development team.

Please help!

[Caterina Curti · Accepted solution]

Hi @Hovig Deveijan,

Are there any errors in the atlassian-bitbucket.log (in the $BITBUCKET_HOME/log) folder?

Can you share them here?

Thanks,

Caterina - Atlassian

[Hovig Deveijan]

Hi Caterina, thanks for the quick reply.  Yes there are.  I am seeing a lot of the following:

Caused by: java.io.FileNotFoundException: C:\atlassian\bitbucket_data\shared\bitbucket.properties (Access is denied)

I saw that the server.xml changed to bitbucket.properties, however we never had a server.xml in bitbucket (only showed up in jira). Also, the server upgrade instructions stated to copy over customizations of which we had none.

[Hovig Deveijan]

The file has no permissions (not sure how this happened).  After taking ownership of it an allowing inheritance things seem to be spinning up.

I think we might be good.  But I do have to admit, the upgrade was not smooth.  Typically this is a one click process, but we had to specify the destination and lookup the home folder path which was not easy to locate in your online instructions (even w/google)

[Caterina Curti]

Glad to hear that Bitbucket Server is now up.

I would like to know more details about the upgrade to better understand what may have gone wrong.

Can you share the following?

- previous running version (if relevant)

- upgrade method (installer or archive)

- the documentation that has been used and was not clear

Cheers,

Caterina

[Hovig Deveijan]

4.10 (previous version).  We did a manual install of 5.10 first (the installer wasn't easily available so we must have gotten this from archive).  Immediately after we installed 5.11 but in either case both had failed.

The documentation was followed verbatim so I wouldn't say it wasn't clear, it was just simply missing an instruction to make sure that the properties file does not have zero permissions.  This obviously shouldn't be required of customers, so it sounds like it's a bug with the installer from 4.10 -> 5.10/5.11

[Hovig Deveijan]

Also, the installation process should include a simple upgrade.  Requiring customers to specify a destination (in which I'm guessing customers accidentally install this to a different path than original install), and home directory seems unnecessary.  It was not straightforward on how to find the home path.  I know where to look now (in configuration settings).  The google results weren't straightforward and install guide provided relative paths which doesn't help assuming someone else installed this on the server or if the defaults were originally chosen and home path not known..