Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to launch the JIRA server

Ganesh Narayan September 28, 2020

Hi Team,

I have installed the JIRA server  - 8.5.7

Getting the below error in the Catalina log file,

SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhos

Kindly suggest on the same, this is a urgent requirement

 

Thanks in advance

1 answer

0 votes
Bastian Stehmann
Community Champion
September 28, 2020

Hi @Ganesh Narayan ,

 

as it says it can't create the directory, it is probably a permission problem.

Make sure that the user, under which Jira runs, has the right permissions to read and write to /opt/atlassian/jira

Ganesh Narayan September 29, 2020

Hello @Bastian Stehmann ,

Am installing software with admin permission, I mean I have the full control.

permission cannot be an issue...

NOTE : On launching Application am getting the response such as I attached, please find the attachment.

Bastian Stehmann
Community Champion
September 29, 2020

Yes, you have admin permission, but the user, that runs jira (usally also jira), does not have admin permission. So you should check the permission of that folders, as the error message says, that there is a permission problem.

Ganesh Narayan September 29, 2020

Hi @Bastian Stehmann

Thanks for your reply, but the above solution did not worked too...

We have tried by giving full permission, Still the same error.

I need a clarification - what if the system doesn't connected to internet, will that be a problem to install the JIRA software.

If you want to more details about the error log , we will share you, Please let me know the solution.

Bastian Stehmann
Community Champion
September 29, 2020

Hi @Ganesh Narayan ,

 

it doesn't matter if the server can access the internet or not, that should not be the problem.

Yes, maybe it would help if you can share more of the log to see if there are other hints that might help us.

Ganesh Narayan September 30, 2020

yes @Bastian Stehmann ,

Thanks for the clarification.

The below are the logs - catalina

30-Sep-2020 03:30:53.282 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.42
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 4 2019 20:29:04 UTC
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.42.0
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\PROGRA~1\ATLASS~1\JIRA\jre
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_202-b08
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\JIRA
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\JIRA
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+ExplicitGCInvokesConcurrent
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Atlassian\JIRA
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Atlassian\JIRA
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Atlassian\JIRA\conf\logging.properties
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -agentpath:C:/PROGRA~2/DYNATR~1/oneagent/agent/lib64/oneagentloader.dll=loglevelcon=none,tenant=kcg66495,tenanttoken=qv5jTontbyGEuhA2,server=https://sg-ap-southeast-2-52-62-86-10-prod12-sydney.live.ruxit.com/communication;https://sg-ap-southeast-2-52-63-191-73-prod12-sydney.live.ruxit.com/communication;https://sg-ap-southeast-2-13-210-45-36-prod12-sydney.live.ruxit.com/communication;https://kcg66495.live.dynatrace.com:443/communication
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.21] using APR version [1.6.5].
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
30-Sep-2020 03:30:53.313 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
30-Sep-2020 03:30:53.407 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1a 20 Nov 2018]
30-Sep-2020 03:30:53.938 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
30-Sep-2020 03:30:53.993 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2215 ms
30-Sep-2020 03:30:54.032 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
30-Sep-2020 03:30:54.032 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.42
30-Sep-2020 03:30:54.079 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: [C:\Program Files\Atlassian\JIRA\conf\Catalina\localhost]
30-Sep-2020 03:32:34.358 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
30-Sep-2020 03:32:34.420 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
30-Sep-2020 03:32:34.451 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 100446 ms

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 18, 2020

Based on recent experience this message should not prevent Jira from starting (while it is a good idea to get rid of the root cause, though!). The presence of the last line even more makes me think that the specific error (alone) is not the reason for the problems you are facing.

Have you already checked if Jira is running but not accessable for some reasons?  For example a firewall active or so?

If that does not apply please also check atlassian-jira.log - just to make sure there is nothing logged that could be useful in debugging this topic.

Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.7
TAGS
AUG Leaders

Atlassian Community Events