Cannot install Jira

[Deleted user]

I am setting up a Bitbucket/Jira machine (CentOS VM / ports 80, 443 and 8080 unblocked). I am running Bitbucket on port 8080 and it's working fine. When trying to install Jira I go through the console installer and then to the web interface to complete the installation. However, the interface redirects me to /secure/errors.jsp (with a 302 redirect) and that page then returns a 503. I have tried changing permissions (as described here) and reinstalling.

What is going on?

Below you can see a log of a freshly installed Jira instance:

10-Nov-2018 15:20:43.980 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.32
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 20 2018 19:50:35 UTC
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.32.0
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 3.10.0-514.el7.x86_64
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /opt/atlassian/jira/jre
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /opt/atlassian/jira
10-Nov-2018 15:20:43.982 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /opt/atlassian/jira
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx768m
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
10-Nov-2018 15:20:43.983 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/atlassian/jira
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/atlassian/jira
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/atlassian/jira/temp
10-Nov-2018 15:20:43.984 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
10-Nov-2018 15:20:44.097 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8081"]
10-Nov-2018 15:20:44.103 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 477 ms
10-Nov-2018 15:20:44.113 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
10-Nov-2018 15:20:44.113 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.32
10-Nov-2018 15:21:06.807 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8081"]
10-Nov-2018 15:21:06.813 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
10-Nov-2018 15:21:06.824 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 22720 ms
10-Nov-2018 15:21:17.280 INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instance.
10-Nov-2018 15:21:17.281 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8081"]
10-Nov-2018 15:21:17.332 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
10-Nov-2018 15:21:17.384 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [commons-pool-EvictionTimer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Object.wait(Native Method)
 java.util.TimerThread.mainLoop(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)
10-Nov-2018 15:21:17.391 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasBatch] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Object.wait(Native Method)
 java.lang.Object.wait(Object.java:502)
 org.objectweb.jonas_timer.TimerManager.batch(TimerManager.java:193)
 org.objectweb.jonas_timer.Batch.run(TimerManager.java:65)
10-Nov-2018 15:21:17.392 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasClock] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Thread.sleep(Native Method)
 org.objectweb.jonas_timer.TimerManager.clock(TimerManager.java:142)
 org.objectweb.jonas_timer.Clock.run(TimerManager.java:46)
10-Nov-2018 15:21:17.393 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [webwork.action.ActionContext$1] (value [webwork.action.ActionContext$1@132057f9]) and a value of type [webwork.action.ActionContext] (value [webwork.action.ActionContext@218557bf]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
10-Nov-2018 15:21:17.393 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@de8dbd0]) and a value of type [com.atlassian.jira.web.filters.ThreadLocalQueryProfiler] (value [com.atlassian.jira.web.filters.ThreadLocalQueryProfiler@1c66da0b]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
10-Nov-2018 15:21:17.393 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [webwork.action.ActionContext$1] (value [webwork.action.ActionContext$1@132057f9]) and a value of type [webwork.action.ActionContext] (value [webwork.action.ActionContext@17d54e97]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
10-Nov-2018 15:21:17.394 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [com.atlassian.instrumentation.operations.ThreadLocalOpTimerFactory$1] (value [com.atlassian.instrumentation.operations.ThreadLocalOpTimerFactory$1@1eed8dc4]) and a value of type [com.atlassian.instrumentation.operations.registry.OpRegistry] (value [com.atlassian.instrumentation.operations.registry.OpRegistry@1ead48f1 {db.conns=OpCounter{name='db.conns', invocationCount=1, elapsedTotal=1076240, elapsedMin=1076240, elapsedMax=1076240, resultSetSize=0, cpuTotal=0, cpuMin=0, cpuMax=0}}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
10-Nov-2018 15:21:17.401 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8081"]
10-Nov-2018 15:21:17.404 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8081"] 

[Andy Heinzer]

It looks like there is a problem with the database Jira is trying to use on startup.  The logs have errors such as this:

2018-11-10 17:24:51,645 JIRA-Bootstrap ERROR      [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, user_key, lower_user_name FROM jira.app_user (ERROR: schema "jira" does not exist
  Position: 43)

This would tend to indicate that the schema of the database does not match the value set for that schema in the dbconfig.xml file.   

In addition to this problem I also noticed that you're using Jira 7.12.3 with a postgres 9.2.x database:

2018-11-10 17:24:50,209 JIRA-Bootstrap INFO      [o.o.c.entity.jdbc.DatabaseUtil] Database Product Name is PostgreSQL
2018-11-10 17:24:50,209 JIRA-Bootstrap INFO      [o.o.c.entity.jdbc.DatabaseUtil] Database Product Version is 9.2.24

The problem here could also be that this latest version of Jira no longer supports postgres 9.2 or earlier database versions.  You can find this information in Jira 7.12.x supported platforms documentation.

I would recommend that you use a supported database type/version and then create a new database per the steps in Connecting Jira applications to PostgreSQL.  Which assumes you will use a postgres version between 9.3.x - 9.6.x.   By following these steps, you should then be able to correct both problems and get onto a supported platform.

[Tom Lister]

Hi @[deleted]

It's likely the default JIRA install will be using port 8080 so can't start if bitbucket is already using it.

The installer should give you options to choose ports to use.

The <jira-install>/conf/server.xml can be edited to change the ports used.

If that doesn't work can you post the whole log somewheree?

[Deleted user]

I set the Jira port to 8081 and the control port to 8006 when installing.

I tried accessing it directly on the server and I get:

# wget -O- localhost:8081
--2018-11-10 17:25:47-- http://localhost:8081/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8081... connected.
HTTP request sent, awaiting response... 302
Location: /secure/errors.jsp [following]
--2018-11-10 17:25:47-- http://localhost:8081/secure/errors.jsp
Reusing existing connection to [localhost]:8081.
HTTP request sent, awaiting response... 503
2018-11-10 17:25:47 ERROR 503: (no description).

I have uploaded the logs of a fresh Jira installation here.

[Deleted user]

I have installed Jira on port 8081 and conrol port 8006.

All the logs generated after installation and initial start are here.