Installation fail. Got HTTP ERROR 500. A fatal error occured during initialisation Edited

[Alexandr Kirilov]

I really hope that Atlassian support will not ignore this message or reply half of the year after (like 3 times before) ...

I've got error at time of installing Server. The error happening just in time of installation. In logs I found this:

2019-04-29 17:48:44,372 http-nio-8080-exec-17 INFO anonymous 1068x9x1 obgpe 172.16.30.10 /secure/SetupDatabase.jspa [c.a.jira.startup.JiraStartupLogger]

Database configuration OK

___ Database Configuration _________________

Loading entityengine.xml from : file:/custom/jira/server/atlassian-jira/WEB-INF/classes/entityengine.xml
Entity model field type name : mysql
Entity model schema name :
Database Version : MySQL - 5.6.43-log
Database Driver : MySQL Connector Java - mysql-connector-java-5.1.47 ( Revision: fe1903b1ecb4a96a917f7ed3190d80c049b1de29 )
Database URL : jdbc:mysql://address=(protocol=tcp)(host=mysql56.server)(port=3306)/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB
Database JDBC config : mysql jdbc:mysql://address=(protocol=tcp)(host=mysql56.server)(port=3306)/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB

2019-04-29 17:48:44,399 http-nio-8080-exec-17 ERROR anonymous 1068x9x1 obgpe 172.16.30.10 /secure/SetupDatabase.jspa [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked.
com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. Unable to resolve component: interface com.atlassian.plugin.SplitStartupPluginSystemLifecycle
at com.atlassian.jira.component.pico.ComponentManager$PluginSystem.earlyStartup(ComponentManager.java:676)
at com.atlassian.jira.component.pico.ComponentManager.earlyStartPluginSystem(ComponentManager.java:238)
at com.atlassian.jira.upgrade.PluginSystemLauncher.start(PluginSystemLauncher.java:45)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.runPostDbSetupRunnables(DatabaseConfigurationManagerImpl.java:283)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.activateDatabase(DatabaseConfigurationManagerImpl.java:276)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.activateDatabase(DatabaseConfigurationManagerImpl.java:240)
at com.atlassian.jira.web.action.setup.SetupDatabase.doExecute(SetupDatabase.java:212)
... 1 filtered
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
... 7 filtered
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
... 49 filtered
at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
... 31 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
... 24 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
... 25 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

[Darryl St_ Pierre]

Alexander,

You've posted to the Atlassian Community pages, which are not necessarily monitored by Atlassian staff (although sometimes they will jump in). If you're looking for an answer from Support, you should contact them here: https://support.atlassian.com/contact/#/

[Taranjeet Singh]

@Alexandr Kirilov See if this similar Community post and the suggested resolution helps resolving your problem: https://community.atlassian.com/t5/Jira-questions/JIRA-Startup-Failed-JIRA-has-been-locked/qaq-p/334982

[Alexandr Kirilov]

It's not related ... This troubles happening only on MySQL 5.6 for 5.7 all is OK