Hi,
trying to install JSD server edition 4.9 on linux using a MySQL 5.7 server - getting the error when trying to setup the database via webpage (express vs custom) - choosing custom since we have an existing MySQL 5.7 server
The MySQL 5.7 server has global character set of 'latin1' - which is different than what the install docs specify...
However, the target database was created with character_set of utf8mb4 (create database 'jirasd' character set collate utf8mb4_bin ; and then => show create database jirasd )
So apparently MySQL 5.7 can support databases with their own character sets/collations?
But the jira sd server installation step (custom, where u enter in db info: hostname, port, database name, user, password) - keeps getting error "This MySQL instance is not properly configured"
looking in the atlassian-jira.log - there are a bunch of WARN statements (no errors tho)
020-05-28 15:49:26,408+0000 http-nio-8080-exec-12 WARN anonymous 949x241x1 1rgachx 127.0.0.1 /secure/SetupDatabase.jspa [webresource] cyclic plugin resource dependency has been detected with: com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, stack trace: [jira.webresources:jira-setup, jira.webresources:_polyfills, com.atlassian.frontend.atlassian-frontend-runtime-plugin:core-js, com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, com.atlassian.auiplugin:aui-core, com.atlassian.auiplugin:common-runtime]
2020-05-28 15:49:26,408+0000 http-nio-8080-exec-12 WARN anonymous 949x241x1 1rgachx 127.0.0.1 /secure/SetupDatabase.jspa [webresource] cyclic plugin resource dependency has been detected with: com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, stack trace: [jira.webresources:jira-setup, jira.webresources:_polyfills, com.atlassian.frontend.atlassian-frontend-runtime-plugin:core-js, com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, com.atlassian.auiplugin:aui-core]
2020-05-28 15:49:26,408+0000 http-nio-8080-exec-12 WARN anonymous 949x241x1 1rgachx 127.0.0.1 /secure/SetupDatabase.jspa [webresource] cyclic plugin resource dependency has been detected with: com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, stack trace: [jira.webresources:jira-setup, jira.webresources:_polyfills, com.atlassian.frontend.atlassian-frontend-runtime-plugin:core-js, com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, com.atlassian.auiplugin:aui-core, com.atlassian.auiplugin:split_aui.splitchunk.0d131bcbf1]
2020-05-28 15:49:26,408+0000 http-nio-8080-exec-12 WARN anonymous 949x241x1 1rgachx 127.0.0.1 /secure/SetupDatabase.jspa [webresource] cyclic plugin resource dependency has been detected with: com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, stack trace: [jira.webresources:jira-setup, jira.webresources:_polyfills, com.atlassian.frontend.atlassian-frontend-runtime-plugin:core-js, com.atlassian.plugins.atlassian-plugins-webresource-plugin:context-path, com.atlassian.auiplugin:aui-core, com.atlassian.auiplugin:split_aui.splitchunk.444efc83be]
any ideas of how to finalize the setup/installation?
Thanks
My guess is that it looks at the mySQL instance setting and not just the DB and that is why you are getting an error and that could explain why when you change the DB version it will work.
yep - that would probably explain it - but i guess i'm kind of stuck as far as installing 4.9 - i'll open a support ticket as well - wasn't sure if anyone else ran into this one and if there was some workaround for the webpage db setup step in the installation...
thanks again, i'll mark this as closed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Brant,
yep - i think most of the settings are good - except for the one about character_set_server
character_set_server=utf8mb4
in our case, this is set to latin-1
however, the question is whether or not this has to be a global setting for the entire MySQL 5.7 server - or if this can be just for the jiraSD database (which was created using utf8mb4 character set and collation utf8mb4_bin ) - so in other words, can we run jiraSD server in this mode?
Not sure - but also it seems the dbconfig.xml is somehow used by the "Jira" user which runs the actual jiraSD java process on the linux server - and inside that dbconfig.xml are some parameters/settings(?) that are passed to the mysql jdbc connector? Could those maybe be "tweaked" so that the utf8mb4 settings are satisfied? In other words - as I am told/understand it - the my.cnf is a global settings that can be easily overridden by a user's own copy of my.cnf in their home dir - thus some of those settings are fall backs if a user doesn't specifically override them?
in our test/eval server, we were able to specify utf8mb4 in the global my.cnf - but in production case - doesn't appear to be an option...
Thanks again,
Wyan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
also - just to add - if we choose "MySQL 5.6" (instead of the MySQL 5.7" in the drop down) - then the "test connection" is green/works... - I don't think it would be a good idea to choose that and click next...
but not for MySQL 5.7 - error is "This MySQL instance is not properly configured. Please follow the documentation for MySQL 5.7+ setup."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure that you are following all the steps in this documentation: https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-mysql-5-7-966063305.html?_ga=2.19134715.2131631236.1590507752-2108615180.1583600299
Most individuals do not make the required changes to the mysqld section of the my.cnf. Sometimes it needs to be made to the mysqld.cnf file depending on your install.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.