BitBucket server upgrade from pre-version 5 to 5.8.0 error

[Graham Walker]

Hi

I recently upgraded my fully functioning Bitbucket server from 4.13.0 to 5.7.0 (and most recently to 5.8.0). However, I am using a Linux (unbuntu) server and I am not particularly familiar with linux. I upgraded and everything seemed to be running successfully. However I did not restart the server and having restarted today I found that there is now an error.

The web startup gives me:

A fatal error has occurred

The following problem occurred, which prevents Atlassian Bitbucket from starting:

• The database, as currently configured, is not accessible.

The ubuntu console tells me that the server is ignoring unsupported logging configuration file (it appears that "logging.yml" is not supposed to be used but rather "log4j2.properties").

But if I look in the log file, I get told that Tomcat connector is either misconfigured or not listening.

I have a reverse-proxy configured on Apache2 web server. It was using "server.xml" for configuration. I have tried to transfer the settings to the "bitbucket.properties" file. I haven't changed anything in the mod-proxy configuration files for apache ... can anyone help me with this? I am not using SSH ...

Many thanks

[Graham Walker · Accepted solution]

As an update, I discovered that version 5 of bitbucket moved the connector from <Bitbucket installation>/lib to <BibucketHome>/lib

Now solved ... but can I recommend that a note is added similar to the note for 'server.xml' to 'bitbucket.properties' so that the administrators don't spend 24 hours trying to work this out (particularly if not experienced like myself!)

A link to the article that helped me!

https://community.atlassian.com/t5/Bitbucket-questions/BitBucket-Server-says-com-mysql-jdbc-Driver-is-not-available/qaq-p/613794

[Christian Glockner]

Hi Graham,

I'd suggest looking at the Bitbucket Server logs, which you'll find in <BitbucketHome>/log. If you're having trouble locating the relevant error, stop Bitbucket, delete the logs in that directory and start Bitbucket again, and then read from the bottom up - there should be some sort of exception relating to the database.

Cheers,

Christian

Premier Support Engineer

Atlassian