Ndtyjky

I am setting up a Bitbucket/Jira machine (CentOS VM). I am running Bitbucket on port 8080 and it's working fine. When trying to install Jira (HTTP: 8081, control: 8006) 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 with:

sudo chown -R jira:jira /var/atlassian/application-data/

sudo chown -R jira:jira /opt/atlassian/jira/

Here I have uploaded all the logs generated when installing and starting.

The problem is visible here in your catalina.out:

2018-11-10 17:24:50,218 JIRA-Bootstrap WARN      [o.o.c.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database

2018-11-10 17:24:50,222 JIRA-Bootstrap ERROR      [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "jira.jiraaction"

2018-11-10 17:24:50,222 JIRA-Bootstrap ERROR      [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:

    CREATE TABLE jira.jiraaction (ID NUMERIC(18,0) NOT NULL, issueid NUMERIC(18,0), AUTHOR VARCHAR(255), actiontype VARCHAR(255), actionlevel VARCHAR(255), rolelevel NUMERIC(18,0), actionbody TEXT, CREATED TIMESTAMPTZ, UPDATEAUTHOR VARCHAR(255), UPDATED TIMESTAMPTZ, actionnum NUMERIC(18,0), CONSTRAINT PK_jiraaction PRIMARY KEY (ID))

    Error was: org.postgresql.util.PSQLException: ERROR: schema "jira" does not exist

It appears that you have configured the Jira database to use a schema named jira which does not exist.

One option is to create it and ensure that the appropriate permissions are granted to the Postgres user that you're using to access the database.

An alternative is to simply reset the schema back to the default of public (in your /var/atlassian/application-data/jira/dbconfig.xml). You are already using a separate database for Jira anyway, and at least on Postgres, having a distinct schema is unnecessary.