I installed Jira server on windows server and it ran fine. Once I stopped server and restart now its

[Sushil Bhattachan]

Hi

I installed Jira server on windows server and it ran fine. Once I stopped server and restart now its not working. It gives Jira page not found error in the browser. I am very new and not that technical.. Any help is really appreciate. 

Here is log file content. 

17-Jan-2019 16:15:06.009 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.32
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 20 2018 19:50:35 UTC
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.32.0
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\PROGRA~1\ATLASS~1\JIRA\jre
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Program Files\Atlassian\JIRA
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Program Files\Atlassian\JIRA
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Atlassian\JIRA
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Atlassian\JIRA
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=C:\Program Files\Atlassian\JIRA\endorsed
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Atlassian\JIRA\conf\logging.properties
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms256m
17-Jan-2019 16:15:06.025 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx768m
17-Jan-2019 16:15:06.025 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: [C:\Program Files\Atlassian\JIRA\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\GooGet;C:\Program Files\Google\Compute Engine\metadata_scripts;C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin;C:\Program Files\Google\Compute Engine\sysprep;C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;.]
17-Jan-2019 16:15:07.228 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
17-Jan-2019 16:15:07.244 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2317 ms
17-Jan-2019 16:15:07.275 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
17-Jan-2019 16:15:07.275 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.32
17-Jan-2019 16:17:22.650 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
17-Jan-2019 16:17:22.666 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
17-Jan-2019 16:17:22.697 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 135452 ms

[Taranjeet Singh]

@Sushil Bhattachan Looking at the last line of your Tomcat Server logs, where it provides the time in which it will start the Server, it may also be the case that application server might be taking time to come up. This may happen sometimes; I don't remember exactly why, but it may be a Java 8 issue as well, that leads to this delay in Tomcat Server startup. If you explore online, you may find some information on a JVM property that can be setup for JIRA startup, that will speed up the Server startup.

So, if this is a case of delayed start up of Tomcat Server, you can check by accessing your JIRA application in browser after some time to see it it is up or not. 

[Sushil Bhattachan]

Taranjeet. Thanks a lot for your response. Yes it worked. It seem like it takes 15-20mins to start :(. Thanks a lot. 

[Taranjeet Singh]

@Sushil BhattachanCan you please accept my answer for the others in community to follow?

[Taranjeet Singh]

@Sushil Bhattachan As a next step, I would suggest to look into Atlassian JIRA application logs (atlassina-jira.log) located in JIRA home directory, in order to get a log of specific errors that might be causing this issue, while trying to access JIRA in the browser.

The location of atlassian-jira.log file can be determined by referring to this Atlassian document: https://confluence.atlassian.com/adminjiraserver075/important-directories-and-files-935391741.html