JIRA throws severe messages during startup after configuring SSL

Question

Hi,

I followed the instructions for configuring JIRA to run over SSL as per

https://confluence.atlassian.com/display/JIRA052/Running+JIRA+over+SSL+or+HTTPS#RunningJIRAoverSSLorHTTPS-trust

with self signed certificates. I have configured HTTP/HTTPS using config.sh

My catalina error log shows

28-Aug-2017 01:02:52.920 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost

28-Aug-2017 01:02:53.102 SEVERE [Catalina-startStop-1] org.apache.catalina.core.ContainerBase.startInternal A child container failed during start

java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]

at java.util.concurrent.FutureTask.report(FutureTask.java:122)

at java.util.concurrent.FutureTask.get(FutureTask.java:192)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:911)

at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:890)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1403)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1393)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)

... 6 more

Caused by: java.lang.NullPointerException

at org.apache.tomcat.util.IntrospectionUtils.getProperty(IntrospectionUtils.java:189)

at org.apache.catalina.connector.Connector.getProperty(Connector.java:266)

at org.apache.catalina.connector.Connector.getAttribute(Connector.java:293)

at org.apache.catalina.core.ApplicationContext.populateSessionTrackingModes(ApplicationContext.java:946)

at org.apache.catalina.core.ApplicationContext.<init>(ApplicationContext.java:123)

at org.apache.catalina.core.StandardContext.getServletContext(StandardContext.java:2240)

at org.apache.catalina.core.StandardContext.postWorkDirectory(StandardContext.java:6110)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

... 6 more

28-Aug-2017 01:02:53.103 SEVERE [main] org.apache.catalina.core.ContainerBase.startInternal A child container failed during start

java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]

at java.util.concurrent.FutureTask.report(FutureTask.java:122)

at java.util.concurrent.FutureTask.get(FutureTask.java:192)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:911)

at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:791)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.startup.Catalina.start(Catalina.java:655)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:355)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)

Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1403)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1393)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: org.apache.catalina.LifecycleException: A child container failed during start

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)

at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:890)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

... 6 more

28-Aug-2017 01:02:53.103 SEVERE [main] org.apache.catalina.startup.Catalina.start The required Server component failed to start so Tomcat is unable to start.

org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]]

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)

at org.apache.catalina.startup.Catalina.start(Catalina.java:655)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Meth

Appreciate help/assistance in advance.

Regards

Anil Khiani

Anil Khiani · Answer

Thanks Branden. I will try the solution and update.

Cheers

Anil

somethingblue · Answer

Hi Anil,

I would start with the article titled JIRA throws SEVERE message during startup due to Unable to create directory for deployment.

It lists the cause as follows:

The Tomcat process is not able to access the scratchDir or deployment directory, most likely due to file permissions. The scratchDir is used by Tomcat when compiling JSPs which is the technology used to render the dynamically created web pages in JIRA applications. If Tomcat cannot access that directory it can result in failures to properly operate.

Here is the resolution:

* Stop your JIRA application.

* Fix the permissions for the below directories and all of their subdirectories:

* $JIRA_HOME/
$JIRA_INSTALL/

* Remove the following directory:

* 
$JIRA_INSTALL/work

* Start the application

Let us know if that works for you.  See the steps in JIRA throws SEVERE message during startup due to Unable to create directory for deployment  for specific OS related instructions to change the permissions in Step 2.

Cheers,

Branden