nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Software Stuck on Database Setup Page

gf_4ubrrf

Hello,

I have successfully installed Jira Software and created database as guided buy Atlassian. I also added the MySQL connector required.

For some reason, I seem to be getting stuck on the database setup page. It shows connectivity and 175 tables are created but I can't get past this page and it's been an hour. All I get is a spinning wheel and "Please wait while the database is set up. This may take a minute..."

I initially thought it was an error I made and uninstalled about 3 times. With fresh installs, still experiencing the same issue. It is frustrating, please help.

OS is CentOS 7
4TB Storage, 2GB RAM with 6GB Swap

MySQL Connector Version - Java-8.0.17
JIRA Software - 8.3.1

Accepted answers

All comments

Alexis Robert

Hi @gf ,

it might be a permissions issue on the database, can you have a look at the logs in JIRA_INSTALL_DIR/log/catalina.out and see if you have any errors related to the database ?

gf_4ubrrf

Hello @Alexis Robert many thanks for your response. I have had a look at the logs but I'm not tech savvy, I only know how to follow guidelines for now so the content doesn't make any sense to me.

Shall I attach the log on here for your perusal?

Alexis Robert

Hi @gf ,

if you open the log files, can you search for lines starting with ERROR ? You can then copy these lines here.

gf_4ubrrf

Hello @Alexis Robert

the content of the logs are as below;



06-Aug-2019 11:52:52.531 INFO [http-nio-8080-exec-15] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

06-Aug-2019 11:52:52.531 INFO [http-nio-8080-exec-16] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

brbojorque

Looking at the problem it is obvious that there is an infrastructure issue here.

You are running JIRA using 2GB RAM, the minimum requirements are 6GB RAM or even higher depending on the users as per https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html

Please upgrade the infrastructure, make sure before you connect the database the JVM values are updated. xms = 1g and xmx = 3g

gf_4ubrrf

Hello @brbojorque ,

infrastructure had been upgraded since the initial post with additional 6GB RAM space added. Still, the same issue occur.

Deleted MariaDB and installed MySQL, now stuck on

'Database: We've found an error in MySQL supported version!

The database setup is not supporting utf8mb4'

I never imagined i'd need to put in this much work to get this running. It is still not running.

brbojorque

It is very easy to fix, just drop the database and create a new one using the link below.

https://confluence.atlassian.com/kb/how-to-fix-the-collation-and-character-set-of-a-mysql-database-744326173.html

Or just use Postgres, its much easier just follow the steps below.

https://confluence.atlassian.com/conf64/database-setup-for-postgresql-936511499.html

gf_4ubrrf

Hello @brbojorque Already done all that as well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server