atlassian-jira-5.1.7-standalone install - stuck during startup

[WP Service Account]

While evaluating if Jira, my installation got stuck during startup.

I am attaching the log output - I am installing the evaluation version of 5.1.7 Jira on Oracle Linux 64 bit. What could be causing this to get stuck here... (complete logs attached)

root@ukdc1-c-ole-1-jira atlassian-jira-5.1.7-standalone # cd bin

root@ukdc1-c-ole-1-jira bin # su jira

jira@ukdc1-c-ole-1-jira bin $ ./start-jira.sh -fg

executing as current user

.....

.... .NMMMD. ...

.8MMM. $MMN,..~MMMO.

.?MMM. .MMM?.

OMMMMZ. .,NMMMN~

.IMMMMMM. .NMMMN. .MMMMMN,

,MMMMMM$..3MD..ZMMMMMM.

=NMMMMMM,. .,MMMMMMD.

.MMMMMMMM8MMMMMMM,

.ONMMMMMMMMMMZ.

,NMMMMMMM8.

.:,.$MMMMMMM

.IMMMM..NMMMMMD.

.8MMMMM: :NMMMMN.

.MMMMMM. .MMMMM~.

.MMMMMN .MMMMM?.

Atlassian JIRA

Version : 5.1.7

Detecting JVM PermGen support...

PermGen switch is supported. Setting to 256m

If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

Using JIRA_HOME: /home/jira

Server startup logs are located in /opt/atlassian-jira-5.1.7-standalone/logs/catalina.out

Using CATALINA_BASE: /opt/atlassian-jira-5.1.7-standalone

Using CATALINA_HOME: /opt/atlassian-jira-5.1.7-standalone

Using CATALINA_TMPDIR: /opt/atlassian-jira-5.1.7-standalone/temp

Using JRE_HOME: /opt/jdk/jdk1.6.0_37

Using CLASSPATH: /opt/atlassian-jira-5.1.7-standalone/bin/bootstrap.jar

Using CATALINA_PID: /opt/atlassian-jira-5.1.7-standalone/work/catalina.pid

29-Oct-2012 15:43:29 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: /opt/jdk/jdk1.6.0_37/jre/lib/amd64/server:/opt/jdk/jdk1.6.0_37/jre/lib/amd64:/opt/jdk/jdk1.6.0_37/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

29-Oct-2012 15:43:30 org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8080

29-Oct-2012 15:43:30 org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 837 ms

29-Oct-2012 15:43:30 org.apache.catalina.realm.JAASRealm setContainer

INFO: Set JAAS app name Catalina

29-Oct-2012 15:43:30 org.apache.catalina.core.StandardService start

INFO: Starting service Catalina

29-Oct-2012 15:43:30 org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-10-29 15:43:32,346 main INFO atlassian.jira.startup.JiraStartupLogger

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

JIRA starting...

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

2012-10-29 15:43:32,382 main INFO atlassian.jira.startup.JiraStartupLogger

___ Environment _____________________________

JIRA Build : 5.1.7#786-sha1:c37bed149f6b583a3248f8332088171039413a3a

Build Date : Tue Oct 09 00:00:00 BST 2012

JIRA Installation Type : Standalone

Application Server : Apache Tomcat/6.0.32 - Servlet API 2.5

Java Version : 1.6.0_37 - Sun Microsystems Inc.

Current Working Directory : /opt/atlassian-jira-5.1.7-standalone/bin

Maximum Allowable Memory : 682MB

Total Memory : 245MB

Free Memory : 183MB

Used Memory : 62MB

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

Memory Pool: PS Eden Space : PS Eden Space: init = 67174400(65600K) used = 64703960(63187K) committed = 67174400(65600K) max = 246153216(240384K)

Memory Pool: PS Survivor Space : PS Survivor Space: init = 11141120(10880K) used = 0(0K) committed = 11141120(10880K) max = 11141120(10880K)

Memory Pool: PS Old Gen : PS Old Gen: init = 178978816(174784K) used = 0(0K) committed = 178978816(174784K) max = 536870912(524288K)

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

JVM Input Arguments : -Djava.util.logging.config.file=/opt/atlassian-jira-5.1.7-standalone/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -Djira.home=/home/jira -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/atlassian-jira-5.1.7-standalone/endorsed -Dcatalina.base=/opt/atlassian-jira-5.1.7-standalone -Dcatalina.home=/opt/atlassian-jira-5.1.7-standalone -Djava.io.tmpdir=/opt/atlassian-jira-5.1.7-standalone/temp

___ Java System Properties _________________

atlassian.standalone : JIRA

catalina.base : /opt/atlassian-jira-5.1.7-standalone

catalina.home : /opt/atlassian-jira-5.1.7-standalone

catalina.useNaming : true

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

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

${catalina.home}/lib,

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

file.encoding : ISO-8859-1

file.encoding.pkg : sun.io

java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment

java.awt.headless : true

java.awt.printerjob : sun.print.PSPrinterJob

java.class.version : 50.0

java.home : /opt/jdk/jdk1.6.0_37/jre

java.io.tmpdir : /opt/atlassian-jira-5.1.7-standalone/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_37-b06

java.specification.name : Java Platform API Specification

java.specification.vendor : Sun Microsystems Inc.

java.specification.version : 1.6

java.util.logging.config.file : /opt/atlassian-jira-5.1.7-standalone/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_37

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 : 20.12-b01

jira.home : /home/jira

mail.mime.decodeparameters : true

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

os.arch : amd64

os.name : Linux

os.version : 2.6.18-308.4.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 : /opt/jdk/jdk1.6.0_37/jre/lib/amd64

sun.cpu.endian : little

sun.cpu.isalist :

sun.io.unicode.encoding : UnicodeLittle

sun.java.command : org.apache.catalina.startup.Bootstrap start

sun.java.launcher : SUN_STANDARD

sun.jnu.encoding : ISO-8859-1

sun.management.compiler : HotSpot 64-Bit Tiered Compilers

sun.os.patch.level : unknown

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

user.country : GB

user.dir : /opt/atlassian-jira-5.1.7-standalone/bin

user.home : /home/jira

user.language : en

user.name : jira

user.timezone : GB-Eire

2012-10-29 15:43:32,392 main INFO atlassian.jira.startup.JiraStartupLogger Running JIRA startup checks.

2012-10-29 15:43:32,462 main INFO atlassian.jira.startup.JiraHomeStartupCheck The jira.home directory '/home/jira' is validated and locked for exclusive use by this instance.

2012-10-29 15:43:32,463 main INFO atlassian.jira.startup.JiraStartupLogger JIRA pre-database startup checks completed successfully.

2012-10-29 15:43:32,832 main INFO jira.config.database.SystemTenantDatabaseConfigurationLoader Reading database configuration from /home/jira/dbconfig.xml

2012-10-29 15:43:34,268 main INFO atlassian.jira.startup.JiraStartupLogger

___ Starting the JIRA Plugin System _________________

2012-10-29 15:43:34,270 main INFO atlassian.plugin.manager.DefaultPluginManager Initialising the plugin system

2012-10-29 15:43:40,930 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/auiplugin-3.7-m6.jar (1349760276000) created

2012-10-29 15:43:41,051 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-language-pack-de_DE-5.1.6-v2r5488-2012-10-04.jar (1349760278000) created

2012-10-29 15:43:41,070 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-language-pack-es_ES-5.1.6-v2r11549-2012-10-03.jar (1349760278000) created

2012-10-29 15:43:41,091 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-language-pack-fr_FR-5.1.6-v2r2045-2012-10-02.jar (1349760278000) created

2012-10-29 15:43:41,119 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-language-pack-ja_JP-5.1.6-v2r13500-2012-10-02.jar (1349760276000) created

2012-10-29 15:43:41,128 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-languages-5.1.7-en_UK.jar (1349760706000) created

2012-10-29 15:43:41,138 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/jira-languages-5.1.7-en_US.jar (1349760706000) created

2012-10-29 15:43:41,162 main INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: /home/jira/plugins/.bundled-plugins/soy-template-plugin-1.1.3.jar (1349760130000) created

2012-10-29 15:43:41,621 main INFO atlassian.plugin.util.WaitUntil Plugins that have yet to be enabled: tac.jira.languages.ja_JP, tac.jira.languages.fr_FR, com.atlassian.soy.soy-template-plugin, tac.jira.languages.de_DE, tac.jira.languages.es_ES, com.atlassian.auiplugin , 60 seconds remaining

2012-10-29 15:43:42,645 main INFO atlassian.plugin.loaders.ScanningPluginLoader No plugins found to be deployed

2012-10-29 15:43:42,648 main INFO atlassian.plugin.manager.DefaultPluginManager Plugin system started in 0:00:08.375

2012-10-29 15:43:42,654 main INFO atlassian.jira.startup.JiraStartupLogger

___ Plugin System Started _________________

2012-10-29 15:43:43,310 main INFO jira.config.database.SystemTenantDatabaseConfigurationLoader Reading database configuration from /home/jira/dbconfig.xml

2012-10-29 15:43:43,501 main INFO jira.config.database.DatabaseConfigurationManagerImpl The database is not yet configured

2012-10-29 15:43:43,502 main INFO jira.config.database.DatabaseConfigurationManagerImpl Enqueuing Database Checklist Launcher' on post-database-configured-but-pre-database-activated queue

2012-10-29 15:43:43,503 main INFO jira.config.database.DatabaseConfigurationManagerImpl The database is not yet configured

2012-10-29 15:43:43,503 main INFO jira.config.database.DatabaseConfigurationManagerImpl Enqueuing Post database-configuration launchers' on post-database-activated queue

29-Oct-2012 15:43:44 org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8080

29-Oct-2012 15:43:44 org.apache.catalina.startup.Catalina start

INFO: Server startup in 14569 ms

[Nic Brough -Adaptavist-]

Er, nothing. The last line says it's up and running.

What seems to be the problem here?