run config.sh , but cannot configure database

Deleted user December 28, 2017

I wonder what I have missed , so need your help here:

installed jira software on centos7, run config.sh to setup database

  1. cannot use mssql as it always set as H2
  2. giving a dbconfig.xml to have the configuration, jira still not working due to database issue

2 answers

0 votes
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 28, 2017

Hi Quan,

When you run config.sh what error do you get when you try to set the MySQL database?  If you can provide a screenshot that would be helpful. 

If you're not getting an error do you see anything in your logs around the time you set the database?  Also, you state JIRA is not working due to the database issue.  What do the logs say when you start JIRA?

Cheers,

Branden

Deleted user December 28, 2017

not sure I get it right, here is the last part of the log:


2017-12-28 10:13:11,779 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-12-28 10:13:11,807 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-12-28 10:13:11,809 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-12-28 10:13:12,409 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-12-28 10:13:12,420 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Starting the JIRA Plugin System _________________

2017-12-28 10:13:12,420 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun
2017-12-28 10:13:14,375 JIRA-Bootstrap INFO [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed
2017-12-28 10:13:14,683 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (27): [tac.jira core.languages.da_DK, tac.jira core.languages.et_EE, tac.jira core.languages.pl_PL, tac.jira core.languages.sk_SK, tac.jira core.languages.sv_SE, com.atlassian.plugins.issue-status-plugin, tac.jira core.languages.no_NO, com.atlassian.soy.soy-template-plugin, com.atlassian.jira.jira-less-integration, tac.jira core.languages.cs_CZ, tac.jira core.languages.hu_HU, tac.jira core.languages.pt_BR, com.atlassian.jira.jira-languages.en_UK, tac.jira core.languages.ko_KR, tac.jira core.languages.is_IS, com.atlassian.jira.jira-languages.en_US, tac.jira core.languages.ru_RU, tac.jira core.languages.de_DE, tac.jira core.languages.es_ES, com.atlassian.plugins.less-transformer-plugin, com.atlassian.plugin.jslibs, tac.jira core.languages.fr_FR, tac.jira core.languages.ja_JP, com.atlassian.plugins.jquery, tac.jira core.languages.ro_RO, tac.jira core.languages.zh_CN, com.atlassian.auiplugin], 300 seconds remaining
2017-12-28 10:13:14,755 ThreadPoolAsyncTaskExecutor::Thread 5 WARN [c.a.p.s.scanner.util.ProductFilterUtil] Couldn't detect product, will use ProductFilter.ALL
28-Dec-2017 10:13:15.949 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [http-nio-8100]
28-Dec-2017 10:13:15.957 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
28-Dec-2017 10:13:15.963 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 7429 ms
2017-12-28 10:13:16,114 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2017-12-28 10:13:16,175 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2017-12-28 10:13:16,184 JIRA-Bootstrap INFO [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2017-12-28 10:13:16,199 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2017-12-28 10:13:16,199 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2017-12-28 10:13:16,221 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2017-12-28 10:13:16,222 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2017-12-28 10:13:16,239 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 180 MiB. Committed: 483 MiB. Max: 741 MiB
Non-heap memory : Used: 64 MiB. Committed: 66 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 244 MiB. Committed: 549 MiB. Max: 2005 MiB
---------------------------------------------------------------------------------

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 28, 2017

Sorry, what does "cannot use mssql" mean?  What is it doing that stops you using another database?

Deleted user December 28, 2017

actually, I was trying to config database thru config.sh , and I did see the options for databases, but cannot make the selection.  

Right,  I cannot use MSSQL because my entry not taken

some info from log:

2017-12-28 10:13:16,199 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.

2017-12-28 10:13:16,221 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue

2017-12-28 10:13:16,222 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 28, 2017

I'm sorry - "cannot make the selection" does not tell us what is wrong.

The log doesn't matter, it's the output from starting Jira after config.sh has been run, where we already know you've got a selection that isn't right.

Sunny Reddy July 1, 2022

Hi guys I have the same issue. Any suggestions? 

 

Our Jira is on windows server @Nic Brough -Adaptavist-  @somethingblue 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 1, 2022

I'd start by describing the actual problem, we can't help with "it doesn't work"

Sunny Reddy July 1, 2022

Hi @Nic Brough -Adaptavist-  Thanks for you quick reply.

 

We have restarted Jira and for some reason DB is not yet configured. I got this information from log. Our Jira is on Windows server. 

 

Jul-2022 14:15:52.049 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8081"]
01-Jul-2022 14:15:52.069 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
01-Jul-2022 14:15:52.099 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 17781 ms
2022-07-01 14:15:52,359+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian Jira 8.20.6\home\dbconfig.xml
2022-07-01 14:15:52,519+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian Jira 8.20.6\home\dbconfig.xml
2022-07-01 14:15:52,524+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian Jira 8.20.6\home\dbconfig.xml
2022-07-01 14:15:54,859+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian Jira 8.20.6\home\dbconfig.xml
2022-07-01 14:15:54,899+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger]
 
    _ Starting the JIRA Plugin System _______
 
2022-07-01 14:16:07,930+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian Jira 8.20.6\home\dbconfig.xml
2022-07-01 14:16:08,060+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2022-07-01 14:16:08,065+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Jira pre-database startup checks completed successfully.
2022-07-01 14:16:08,155+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2022-07-01 14:16:08,165+0000 JIRA-Bootstrap INFO      [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2022-07-01 14:16:08,210+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
2022-07-01 14:16:08,230+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 1, 2022

This is a bit of an odd one to explain, but it's the logging that is not helpful, not an actual bug.

The log says "The database is not yet configured" and immediately after, "Startup is complete. Jira is ready to serve.", but that's misleading.  The second message really should be "give me a minute, then go to the base url of Jira where I'll be asking you more getting-started questions"

Given that you've now let it have a few minutes to complete the start up (including building and populating all the tables in the empty database), what do you now get when you visit the url with a browser?  And in the log when you try to visit?

Sunny Reddy July 1, 2022

@Nic Brough -Adaptavist-  When I hit the URL .. it displays Can't reach this page. Jira took too long to respond.  

 

Logs - Logs which I pasted earlier. 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 2, 2022

After you have given it a couple of minutes to get started, what does the log say when you try to visit the site?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events