Fatal Error on start up after upgrade

[IT Manager]

Initially had 5.0.1 when we first got Bitbucket last year. We are upgrading our servers so I migrated everything to the new server and installed a new instance of 5.0.1. Worked fine and confirmed repos were still there but after I upgraded to 5.11 I get the error below.

• Bitbucket Home [D:\Atlassian\ApplicationData\Bitbucket] exists but is not writable by Bitbucket

• SpringMVC dispatcher [springMvc] could not be started

I read that it was a permission thing but the default user (atlbitbucket) account already has full control. 

Any ideas on how to proceed?

[Caterina Curti · Accepted solution]

Hi @IT Manager,

It is true that the error indicates a permission issue (see also this article).

Since the atlbitbucket has full access, I would start by checking the following:

- Is there a difference when starting Bitbucket using the service or the start-bitbucket.bat script? See Starting and stopping Bitbucket Server.

- How was the original installation and the upgrade performed? Using the installer or the archive?

- Does the user matches the requirements from the Running Bitbucket Server with a dedicated user page?

Are there any other error or warnings in the atlassian-bitbucket.log?

Cheers,

Caterina - Atlassian

[IT Manager]

Issue seems to be worse now. I uninstalled and tried to re-install several times. Following the instructions here - https://confluence.atlassian.com/bitbucketserverkb/how-to-uninstall-bitbucket-server-828789036.html.

Difference is when I re-install 5.0.1 it doesn't recognize my home folder. It goes through initial setup and goes to the "Create Login" screen instead of what it originally did which was ask for a login.

I'm not really sure what to do at this point and feel like I'm going to need some hand-holding.

[IT Manager]

Shortly after posting this reply I decided to give it another go.... 5.0.1 worked. I could see my repos and history just fine. Scared to try and upgrade... Did it anyway since I just want to move on to another project.

Same error.

- No difference when I starting the service manually or through the start-bitbucket.bat script.

- Used installer.

- User matches requirements.

- Logs - 

***************************
APPLICATION FAILED TO START
***************************

Description:

The Tomcat connector configured to listen on port 7990 failed to start. The port may already be in use or the connector may be misconfigured.

Action:

Verify the connector's configuration, identify and stop any process that's listening on port 7990, or configure this application to listen on another port.

Comparing with the successful 5.0.10 launch... It fails right away.

From the 5.0.10 log:

2018-06-20 15:19:54,286 INFO  [main]  c.a.b.i.b.BitbucketServerApplication Started BitbucketServerApplication in 10.199 seconds (JVM running for 15.699)

From the 5.11.1 log:

2018-06-20 16:02:16,545 ERROR [main]  o.a.catalina.core.StandardService Failed to start connector [Connector[HTTP/1.1-7990]]

Could the 5.0.10 version be interfering with the 5.11.1? If so... How do I fix?

[Caterina Curti]

Hi @IT Manager,

We have created a support request on your behalf for this issue.

Please let us know here if you did not receive it or have any problem accessing it.

Cheers,

Caterina - Atlassian

[Caterina Curti]

Hey @IT Manager,

Checking the support ticket, it looks like the root cause was a Windows permission issue and everything is good now.