MariaDB 10.4.7 not supported

[RBDev]

The target database is MariaDB 10.4.7. This database is not supported; it has known issues when used with Bitbucket. Please use a supported database. Refer to the Bitbucket documentation for more information about which databases are supported.
com.atlassian.stash.internal.db.DefaultDatabaseManager.validateConfiguration(DefaultDatabaseManager.java:226)
com.atlassian.stash.internal.db.DefaultDatabaseManager.prepareDatabase(DefaultDatabaseManager.java:183)
com.atlassian.stash.internal.maintenance.SpringMaintenanceTaskFactory.setupTask(SpringMaintenanceTaskFactory.java:151)

What to do? I can't rollback database. 

[Petr Vaníček]

Hi @RBDev ,

Same as @Nic Brough -Adaptavist- - I don't think you have any other option than rollback database. There is not difference (only more work) if original DB server or you will create new one.

So follow up what @Nic Brough -Adaptavist- wrote, because I don't think you have time to just wait if and when there will be any release of Bitbucket in short near future with support of your version.

[robydev]

Hi Petr. Thanks for your replay. It seems they can't tell when the fix is going to be available. In this case I'm better of setting up a new server with an old mariadb version.

[Nic Brough -Adaptavist-]

I'm afraid "I can't rollback" is no good.

You have to move to a database that works with Bitbucket, which means moving back to a supported version.  Install the older version, and restore from the backup you took before you upgraded the database server. 

I'm assuming you took a backup, as it is something you should always do.  If you did not, then you may have to look into how to revert the database back in the Maria docs, or check to see if Bitbucket had a backup.

[RBDev]

as already mentioned. I can't change the database server. I could spin another with old version db temporary but I prefer not to.

is there work going on to sort out this issue with version 10.4? Any release date?

[Nic Brough -Adaptavist-]

As I said already, you do not have a choice.  Well, you do - it's either "throw  all your data away", or "move (back) to a database that works"

"I can't" is irrelevant, whomever broke your system should not have done it, and should be tasked with repairing the damage they have caused.

[Nic Brough -Adaptavist-]

For the second question (sorry, I should have included this before), yes, Atlassian are moving to support later versions of various databases.

They never give release dates, as they release "when it's done", not "when someone sticks an arbitrary date out there without understanding what needs doing".

But that won't solve your problem.  It will put you in a place where you can use the new database version, but you will a) need to upgrade and b) start from a working installation on the supported database version.

[robydev]

"you do not have a choice" yes I do. wait for the next release with a fix or build a new server with an old database.

"I can't is irrelevant" No its not. I can't change my live database. ai have multiple apps accessing it and some require mariadb latest version.

"Atlassian are moving" Great, that's a start. Now we need a release date.

"They never give release dates" maybe they should start using Jira.

"But that wont solve your problem" It will if the compatibility issue with mariadb 10.4 is fixed

[Nic Brough -Adaptavist-]

I am sorry, it seems that my explanations are not clear to you.

You have no decisions or choices here.  You must move to using a supported (or at least working) database in order to get back to a working system.  If you do not move, you can not use your system.

"you do not have a choice" and "I can't is irrelevant" are not statements that I make lightly, I would be a lot happier if I could say the opposite.  But I can not.  You must move back to using a workable system.

You insist that you have a choice.  You are right there, but it's not a choice you think it is.  You need to choose between a system that does not work and one that does.  This flows back into your choice of database as well. You must use one that works

I'm not going to tell you to use a supported database - ideally, you should, because then you can ask Atlassian and others for help if it goes wrong, but that's not the point here, the point is you have no choice but to use a database that works.  You have broken tour system by choosing to use one that does not.

Even if Atlassian released a new version of Jira that supported your database tomorrow, you still need to go back, just so your old version can be read and upgraded.

[Mr J]

Hey there, you're right, from the look of things, BitBucket Server does not support MariaDB 10.4.7. Their supported version only goes up until 10.3.7 based on their Supported Platforms.

The only thing I can think of would be to downgrade MariaDB by restoring from a full backup, as it seems it's the only method that is supported, and has the highest chance of success - Downgrading between Major Versions of MariaDB. Fingers crossed you have a copy of the database pre-upgrade stored somewhere, which you can use to restore using these methods.

[RBDev]

Thanks for the replay. Unfortunately my db server is shared with other apps. rollback is not an option.

[Jonathan Vezinat]

absolutely ridiculous.............

[Erik Biermann]

Hi,

a litte bit "dirty" but it is possible to change the returned version string (MariaDB >= 10.2).

https://mariadb.com/kb/en/version/

e.g.: --version=5.7.9 // my.cnf -> [mysqld] version=5.7.9

After that you can start Bitbucket and it will work - but I don't know if and which problems will occur.