after using jira for a several days, after rebooting server jira not starting

[Vinod Bathi]

jira.service - Atlassian Jira
Loaded: loaded (/etc/systemd/system/jira.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-09-09 17:19:09 IST; 7s ago
Process: 3775 ExecStart=/opt/atlassian/jira/bin/start-jira.sh (code=exited, status=0/SU
Main PID: 3821 (code=exited, status=1/FAILURE)

Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Version : 8.3.1
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: [19B blob data]
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: If you encounter issues s
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Server startup logs are l
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Existing PID file found d
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Removing/clearing stale P
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Tomcat started.
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: Started Atlassian Jira.
Sep 09 17:19:09 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: jira.service: Main process exited,
Sep 09 17:19:09 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: jira.service: Failed with result '
lines 1-16/16 (END)

[ADSSA Jira Admin]

Did you restarted the services 

[ADSSA Jira Admin]

Restart jira services 

[Vinod Bathi]

yes, i have given the command systemctl start jira 

                                                  ./start-jira.sh

but unable to start

[ADSSA Jira Admin]

do the following steps

1.Go to services.msc

2.Atlassian jira

3.Stop and restart

Note:If services doe not stop complete kill the task forcefully using the below command in CMD (admin) where PID is mentioned i atlassian services 

sc queryex servicename

taskkill /f /pid [PID]

[Vinod Bathi]

hi,

i am using an ubuntu server, its not windows

[Vinod Bathi]

Hi,

when i open /opt/atlassian/jira/logs# vi catalina.out

root@ubuntu-s-1vcpu-2gb-blr1-01:/opt/atlassian/jira/logs# vi catalina.out
09-Aug-2019 11:48:38.160 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.40
09-Aug-2019 11:48:38.165 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Apr 10 2019 14:31:19 UTC
09-Aug-2019 11:48:38.165 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.40.0
09-Aug-2019 11:48:38.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux
09-Aug-2019 11:48:38.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 4.15.0-52-generic
09-Aug-2019 11:48:38.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
09-Aug-2019 11:48:38.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /opt/atlassian/jira/jre
09-Aug-2019 11:48:38.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_202-b08
09-Aug-2019 11:48:38.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
09-Aug-2019 11:48:38.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /opt/atlassian/jira
09-Aug-2019 11:48:38.172 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /opt/atlassian/jira
09-Aug-2019 11:48:38.175 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties
09-Aug-2019 11:48:38.175 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
09-Aug-2019 11:48:38.176 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
09-Aug-2019 11:48:38.176 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
09-Aug-2019 11:48:38.177 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
09-Aug-2019 11:48:38.177 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
09-Aug-2019 11:48:38.177 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
09-Aug-2019 11:48:38.178 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
09-Aug-2019 11:48:38.178 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
09-Aug-2019 11:48:38.179 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
09-Aug-2019 11:48:38.179 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
09-Aug-2019 11:48:38.180 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
09-Aug-2019 11:48:38.180 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.locale.providers=COMPAT
09-Aug-2019 11:48:38.180 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
09-Aug-2019 11:48:38.180 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
09-Aug-2019 11:48:38.181 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
09-Aug-2019 11:48:38.186 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
09-Aug-2019 11:48:38.191 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log
09-Aug-2019 11:48:38.192 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
09-Aug-2019 11:48:38.193 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
09-Aug-2019 11:48:38.196 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
09-Aug-2019 11:48:38.196 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
09-Aug-2019 11:48:38.196 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
09-Aug-2019 11:48:38.197 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
09-Aug-2019 11:48:38.198 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
09-Aug-2019 11:48:38.198 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
09-Aug-2019 11:48:38.199 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/atlassian/jira
09-Aug-2019 11:48:38.199 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/atlassian/jira
09-Aug-2019 11:48:38.201 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/atlassian/jira/temp
09-Aug-2019 11:48:38.201 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: [/opt/atlassian/jira/atlassian-jira-software-8.3.1-x64.bin.13582.dir/user::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
09-Aug-2019 11:48:38.412 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
09-Aug-2019 11:48:38.461 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1490 ms
09-Aug-2019 11:48:38.493 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
09-Aug-2019 11:48:38.493 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.40
09-Aug-2019 11:48:38.537 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: [/opt/atlassian/jira/conf/Catalina/localhost]
2019-08-09 11:48:48,269 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory '/var/atlassian/application-data/jira' is validated and locked for exclusive use by this instance.
2019-08-09 11:48:48,406 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

[Nic Brough -Adaptavist-]

I think this is a good pointer to the problem

>Unable to create directory for deployment

This usually means that you have got the wrong ownership and/or permissions on the directories for Jira.  The most common way for this to happen is when you try to start it as the wrong user.  That user takes ownership of parts of the file system in order to run, then when you stop it and restart as the correct user, this correct user cannot write to all the files and directories it needs to.

Most common is "Start as Jira-user, stop, and restart as root, then stop and restart as Jira-user" - root can take ownership of any file to do what it needs.  Jira-user is an ordinary user and cannot take back ownership of root-owned files.

Stop Jira, check the permissions and ownership are all "the user who should be running Jira" and restart Jira as that user.

Note also, before all of that, just make a quick check that you have not got a filled disk, either on space or inodes.  "df -kih" should tell you instantly.

[Vinod Bathi]

root@ubuntu-s-1vcpu-2gb-blr1-01:/opt/atlassian/jira/bin# sudo systemctl start jira
root@ubuntu-s-1vcpu-2gb-blr1-01:/opt/atlassian/jira/bin# sudo systemctl status jira
● jira.service - Atlassian Jira
Loaded: loaded (/etc/systemd/system/jira.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-09-09 17:19:09 IST; 7s ago
Process: 3775 ExecStart=/opt/atlassian/jira/bin/start-jira.sh (code=exited, status=0/SU
Main PID: 3821 (code=exited, status=1/FAILURE)

Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Version : 8.3.1
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: [19B blob data]
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: If you encounter issues s
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Server startup logs are l
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Existing PID file found d
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Removing/clearing stale P
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 start-jira.sh[3775]: Tomcat started.
Sep 09 17:19:08 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: Started Atlassian Jira.
Sep 09 17:19:09 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: jira.service: Main process exited,
Sep 09 17:19:09 ubuntu-s-1vcpu-2gb-blr1-01 systemd[1]: jira.service: Failed with result '
lines 1-16/16 (END)