Why is JIRA stuck on the Database Checklist Launcher?

[Patrick Toma]

I have installed JIRA and pointed it to my Oracle 11G database, following all the steps as outlined in the documentation. It seems to be hanging on the Database Checklist Launcher but provides no further log info as to what might be happening. Did I miss something?

Thanks in advance,

Patrick

======================================

dbconfig.xml:

<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>

<name>defaultDS</name>

<delegator-name>default</delegator-name>

<database-type>oracle11g</database-type>

<schema-name></schema-name>

<jdbc-datasource>

<url>jdbc:oracle:thin:@orac6n1.pd.wdh.intuit.com:1521:JIRA01</url>

<driver-class>oracle.jdbc.OracleDriver</driver-class>

<username>********</username>

<password>*********</password>

<pool-size>15</pool-size>

</jdbc-datasource>

</jira-database-config>

catalina.out:

Using CATALINA_BASE: /apps/tomcat

Using CATALINA_HOME: /apps/tomcat

Using CATALINA_TMPDIR: /apps/tomcat/temp

Using JRE_HOME: /usr

Using CLASSPATH: /apps/tomcat/bin/bootstrap.jar

[root@scm03 logs]# ls

catalina.2012-03-13.log catalina.out host-manager.2012-03-13.log localhost.2012-03-13.log manager.2012-03-13.log

[root@scm03 logs]# cat catalina.out

Mar 13, 2012 9:26:26 AM org.apache.catalina.core.AprLifecycleListener init

INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.6.0_18/jre/lib/amd64/server:/usr/java/jdk1.6.0_18/jre/lib/amd64:/usr/java/jdk1.6.0_18/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

Mar 13, 2012 9:26:26 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8080

Mar 13, 2012 9:26:26 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 505 ms

Mar 13, 2012 9:26:26 AM org.apache.catalina.core.StandardService start

INFO: Starting service Catalina

Mar 13, 2012 9:26:26 AM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.35

Mar 13, 2012 9:26:26 AM org.apache.catalina.startup.HostConfig deployDescriptor

INFO: Deploying configuration descriptor jira.xml

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/apps/apache-tomcat-6.0.35/lib/slf4j-log4j12-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/apps/apache-tomcat-6.0.35/webapps/jira/WEB-INF/lib/slf4j-log4j12-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

2012-03-13 09:26:27,941 main INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from /apps/jira-home/dbconfig.xml

2012-03-13 09:26:28,176 main INFO [atlassian.jira.startup.JiraStartupLogger]

****************

JIRA starting...

****************

2012-03-13 09:26:28,194 main INFO [atlassian.jira.startup.JiraStartupLogger]

___ Environment _____________________________

JIRA Build : 5.0#713-sha1:aec58e27a0d402341b1f1be2fc8c0204a0b070f6

Build Date : Wed Feb 15 00:00:00 PST 2012

JIRA Installation Type : EAR/WAR

Application Server : Apache Tomcat/6.0.35 - Servlet API 2.5

Java Version : 1.6.0_18 - Sun Microsystems Inc.

Current Working Directory : /apps/apache-tomcat-6.0.35/logs

Maximum Allowable Memory : 455MB

Total Memory : 122MB

Free Memory : 87MB

Used Memory : 35MB

Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 1211776(1183K) committed = 2555904(2496K) max = 50331648(49152K)

Memory Pool: PS Eden Space : PS Eden Space: init = 33554432(32768K) used = 32788048(32019K) committed = 33554432(32768K) max = 167772160(163840K)

Memory Pool: PS Survivor Space : PS Survivor Space: init = 5570560(5440K) used = 2410056(2353K) committed = 5570560(5440K) max = 5570560(5440K)

Memory Pool: PS Old Gen : PS Old Gen: init = 89522176(87424K) used = 2145104(2094K) committed = 89522176(87424K) max = 357957632(349568K)

Memory Pool: PS Perm Gen : PS Perm Gen: init = 21757952(21248K) used = 18665640(18228K) committed = 21757952(21248K) max = 268435456(262144K)

JVM Input Arguments : -Djava.util.logging.config.file=/apps/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djava.endorsed.dirs=/apps/tomcat/endorsed -Dcatalina.base=/apps/tomcat -Dcatalina.home=/apps/tomcat -Djava.io.tmpdir=/apps/tomcat/temp

___ Java System Properties _________________

catalina.base : /apps/tomcat

catalina.home : /apps/tomcat

catalina.useNaming : true

common.loader : ${catalina.base}/lib,

${catalina.base}/lib/*.jar,

${catalina.home}/lib,

${catalina.home}/lib/*.jar

file.encoding : UTF-8

file.encoding.pkg : sun.io

java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment

java.awt.printerjob : sun.print.PSPrinterJob

java.class.version : 50.0

java.home : /usr/java/jdk1.6.0_18/jre

java.io.tmpdir : /apps/tomcat/temp

java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory

java.naming.factory.url.pkgs : org.apache.naming

java.runtime.name : Java(TM) SE Runtime Environment

java.runtime.version : 1.6.0_18-b07

java.specification.name : Java Platform API Specification

java.specification.vendor : Sun Microsystems Inc.

java.specification.version : 1.6

java.util.logging.config.file : /apps/tomcat/conf/logging.properties

java.util.logging.manager : org.apache.juli.ClassLoaderLogManager

java.vendor : Sun Microsystems Inc.

java.vendor.url : http://java.sun.com/

java.vendor.url.bug : http://java.sun.com/cgi-bin/bugreport.cgi

java.version : 1.6.0_18

java.vm.info : mixed mode

java.vm.name : Java HotSpot(TM) 64-Bit Server VM

java.vm.specification.name : Java Virtual Machine Specification

java.vm.specification.vendor : Sun Microsystems Inc.

java.vm.specification.version : 1.0

java.vm.vendor : Sun Microsystems Inc.

java.vm.version : 16.0-b13

mail.mime.decodeparameters : true

org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true

os.arch : amd64

os.name : Linux

os.version : 2.6.18-274.18.1.0.1.el5

package.access : sun.,

org.apache.catalina.,

org.apache.coyote.,

org.apache.tomcat.,

org.apache.jasper.,

sun.beans.

package.definition : sun.,

java.,

org.apache.catalina.,

org.apache.coyote.,

org.apache.tomcat.,

org.apache.jasper.

server.loader :

shared.loader :

sun.arch.data.model : 64

sun.boot.library.path : /usr/java/jdk1.6.0_18/jre/lib/amd64

sun.cpu.endian : little

sun.cpu.isalist :

sun.io.unicode.encoding : UnicodeLittle

sun.java.launcher : SUN_STANDARD

sun.jnu.encoding : UTF-8

sun.management.compiler : HotSpot 64-Bit Server Compiler

sun.os.patch.level : unknown

tomcat.util.buf.StringCache.byte.enabled : true

user.country : US

user.dir : /apps/apache-tomcat-6.0.35/logs

user.home : /root

user.language : en

user.name : root

user.timezone : US/Pacific

2012-03-13 09:26:28,194 main INFO [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.

2012-03-13 09:26:28,242 main INFO [atlassian.jira.startup.JiraHomeStartupCheck] The jira.home directory '/apps/jira-home' is validated and locked for exclusive use by this instance.

2012-03-13 09:26:28,243 main INFO [atlassian.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.

2012-03-13 09:26:28,465 main INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from /apps/jira-home/dbconfig.xml

2012-03-13 09:26:28,552 main INFO [jira.config.database.DatabaseConfigurationManagerImpl] Now running Database Checklist Launcher

[Deleted user]

We got the exactly same problem.

The cause was SQL Server not running properly: JIRA could not access/write into its database...

[Anandhi A]

Hi,

I also have the same problem....How do i solve it...Memory space is available..no problem with it...There is nothing in logs also..

Thanks in advance.

[Nic Brough -Adaptavist-]

The original poster says there was a database issue - can you test the database settings from the Jira server?

[Anandhi A]

I am connecting to a remote database using IP address and SID. When i tested the connection after providing the database details in the Configuration Tool, it was successful.

[Nic Brough -Adaptavist-]

Ok, good. Could you test it outside Jira - make sure the user that Jira is using to connect with has full read/create/delete/index rights?

[Anandhi A]

The user has full rights...but JIRA is stuck up during startup. There is nothing else in the logs except the same message "Now Running Database Checklist Launcher"...:(

[RomanLutsiv]

Use JIRA Configuration tool to check and update DB configs: https://confluence.atlassian.com/jira/using-the-jira-configuration-tool-214865525.html#UsingtheJIRAConfigurationTool-database

[Jobin Kuruvilla [Adaptavist]]

Any error in the tomcat catalina logs? Like out of memory? How long is it hanging for?

[Jo-Anne MacLeod]

I'm with Jobin here, how is the memory? disk space?

[Patrick Toma]

There are no other errors.. its been hanging for over 3 hours.