1

I'm trying to setup Jira on a vm. I want to move from the embedded H2 database to my own mysql database.

I'm currently running mysql 5.7.x on ubuntu 16.04. However when I try to connect Jira with this server I get the following error message:

Unknown system variable 'storage_engine'

I already tried a number of things to fix this. First off in my mysql.cnf file I added default-storage-engine = InnoDB This didn't do anything for the error.

On my Jira vm I went into /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/database-defaults

and changed it to 

databaseUrl=jdbc:mysql://localhost/jira?autoReconnect=true&characterEncoding=utf8&useUnicode=true&sessionVariables=default-storage-engine=InnoDB

as well as

databaseUrl=jdbc:mysql://localhost/jira?autoReconnect=true&characterEncoding=utf8&useUnicode=true

Again nothing changed for the error. I also went into the dbconfig.xml file and removed the sessionVariables=storage-engine=InnoDB part from the url. Again this didn't change anything.

I've also tried changing it to sessionVariables=default-storage-engine=InnoDB

Again no luck.

Does anyone have an idea how to get it to work? I don't want to create another sql setup just to run sql 5.6.x to be honest. I hope someone knows the solution to this.

Improve this question
7
  • 3
    What did Atlassian support say?
    – EEAA
    Sep 7, 2016 at 14:38
  • @EEAA To be honest I didn't even think about that. I've just been trying to figure it out myself
    – NoSixties
    Sep 7, 2016 at 14:47
  • Atlassian support has been moderately to willingly helpful to us - give them a shout.
    – J E Carter II
    Sep 7, 2016 at 14:51
  • Yup, agreed. In my experience they're quite helpful, as long as you're not trying to deviate from how they think things should be done.
    – EEAA
    Sep 7, 2016 at 14:52
  • I'm contacting support right now. However lira currently doesn't support 5.7.x so I hope they are willing to suggest work arounds
    – NoSixties
    Sep 7, 2016 at 14:53

1 Answer 1

Reset to default
1

This question is answered in the atlassian community website.

The workaround is to uninstall MySQL 5.1 and install MySQL 5.6

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .