Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Install Confluence Server with Mysql 8 fails

kjhall55 March 19, 2021

Install of confluence 7.11.0 server using mysql 8.0 on Centos 8 fails with error:

error code [1419]; You do not have the SUPER privilege and binary logging is enabled

According to the install instructions, binary logging must be on, but other sources indicate that when binary logging is on, the SUPER privilege is required by default for certain operations.  There is no mention of this in the Confluence setup doc, and sources report that setting SUPER privilege is not desirable from a security perspective.  Is there a recommended method for setting this up?

 

 

2 answers

0 votes
Spunkie April 17, 2021
set global log_bin_trust_function_creators=1;
Steve Shaw
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 1, 2021
Like wrenitinfrastructure likes this
0 votes
Aaron Andrade
Contributor
March 30, 2021

@kjhall55 Did you figure this out? I am having the same issue with version 7.11.1.

kjhall55 March 30, 2021

I ended up giving the ID "SUPER" privilege, that fixed it, but I wasn't happy about it.  The instructions for setting up Confluence (and Bitbucket, and Jira) with mysql are outdated and just plain wrong in places.  It's obvious Atlassian would prefer you use postgresql, I just didn't want to have another database service running on that machine, there are other apps there that use mysql.

Aaron Andrade
Contributor
March 31, 2021

We tested that out in our stage environment and it did work. I opened up a support ticket with Atlassian: https://getsupport.atlassian.com/servicedesk/customer/portal/14/CSP-290482.

kjhall55 April 1, 2021

There are other issues with configuring with MySQL, the documentation is badly outdated..  For example, it specifies using the following to configure the user access to the database:

GRANT ALL PRIVILEGES ON <database-name>.* TO '<confluenceuser>'@'localhost' IDENTIFIED BY '<password>';

 But that doesn't work, "IDENTIFIED BY" seems to be deprecated in current versions of MYSql 8, you need to do the GRANT first without the password, then do ALTER to set the password.

Ran into similar issues with Jira and Bitbucket, in Bitbucket particularly, the latest version of the database connector (8) does not work, you need to use version 5.

These are the issues I remember during the setup, I did finally get everything working, but it was a long slog.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.11.0
TAGS
AUG Leaders

Atlassian Community Events