Check the Jira server application to make sure it is running

関連コンテンツ

  • 関連コンテンツがありません

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: サーバーと Data Center のみ。この記事は、サーバーおよび Data Center プラットフォームのアトラシアン製品にのみ適用されます。

目的

The purpose of this article is to list down some simple tests/checks that can be done to verify if Jira is running. This article can be used when Jira is inaccessible via web browser.

この例では、次のような構成であったとします。

  • Jira base URL: http://jira.atlassian.com
  • Jira's internal IP Address: 192.168.1.100
  • Jira is configured to use HTTP port 8080
  • Jira is configured with proxy

ソリューション

The following tests will try to narrow down the where is the problem:

Bypass proxy and SSL.

  1. Access Jira with the following URL:  http://192.168.1.100:8080
  2. If Jira is accessible with the URL above, then the problem is with the configured proxy.
  3. In order to do this, you will need a non-proxy connector configured in server.xml. Please refer to Bypass a proxy or SSL to test network connectivity for Jira server to achieve this.

ping <BASE URL>

  1. If this ping test fails, then it's network related. Please check if your client machine can resolve jira.com

  2. The hosts file is located in different directory. Please refer to Modify your hosts file for more information on how to edit the hosts file.

  3. OR  local DNS server. You may refer to 10 tips for troubleshooting DNS problems for assistance.



telnet <internal IP> <HTTP port>

  1. Replace < internal IP > and <HTTP port> with the respective values. then run telnet <internal IP> < HTTP Port>


    • If this telnet test fails, then these are the possible causes:

      • No network connectivity.

      • Firewall is blocking the HTTP port.

      • Jira service is not running.

      • Jira HTTP port was changed. Please verify the port in server.xml file.

  2. If it's possible to access Jira machine with GUI, try to access Jira locally via this URL: http:// localhost:8080.

    Make sure the Jira machine local firewall is disabled (IPtables, Windows Firewall, etc).


    • If you can access Jira now, then it's network related, you may need to check this with your Network Administrator.

    • If you can't access Jira, then the issue is no longer a network related problem.  

  3. If it's not possible to access The Jira machine with GUI, then you can run the following command for verification:

    • wget http://<INTERNAL IP>:<HTTP PORT> (eg. http://localhost:8704/j704)

      Example of JIRA is running 
      apac@10:~$ wget http://localhost:8704/j704 --2015-12-31 16:44:06-- http://localhost:8704/j704 Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8704... connected. HTTP request sent, awaiting response... 302 Found Location: http://localhost:8704/j704/ [following] --2015-12-31 16:44:06-- http://localhost:8704/j704/ Reusing existing connection to localhost:8704. HTTP request sent, awaiting response... 302 Found Location: http://localhost:8704/j704/secure/MyJiraHome.jspa [following] --2015-12-31 16:44:06-- http://localhost:8704/j704/secure/MyJiraHome.jspa Reusing existing connection to localhost:8704. HTTP request sent, awaiting response... 302 Found Location: http://localhost:8704/j704/secure/Dashboard.jspa [following] --2015-12-31 16:44:06-- http://localhost:8704/j704/secure/Dashboard.jspa Reusing existing connection to localhost:8704. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘j704.1’ [ <=> ] 34,744 --.-K/s in 0.06s 2015-12-31 16:44:07 (587 KB/s) - ‘j704.1’ saved [34744]
      Example of there is no JIRA is running 
      apac@10:~$ wget http://localhost:6412/j6412 --2015-12-31 16:45:46-- http://localhost:6412/j6412 Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:6412... failed: Connection refused.

Is Jira running


  1. Check to see that Jira is running on the server
    1. If Jira is installed as Service:
      1. Linux; run the following command: ps -ef | grep jira OR ps -ef | grep '[j]ira' (to exclude grep from ps outputs):
      Example of JIRA is running 
      osboxes@osboxes:/opt/atlassian/jira702/conf$ ps -ef | grep jira
root      9096  8286  0 10:29 pts/10   00:00:00 su - jira
jira      9097  9096  0 10:29 pts/10   00:00:00 -su
jira     11349  2859 99 11:32 ?        00:00:03 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
osboxes  11367 27426  0 11:32 pts/4    00:00:00 grep --color=auto jira
      Example of there is no JIRA is running 
      osboxes@osboxes:/opt/atlassian/jira702/conf$ ps -ef | grep jira
root      9096  8286  0 10:29 pts/10   00:00:00 su - jira
jira      9097  9096  0 10:29 pts/10   00:00:00 -su
osboxes  11478 27426  0 11:35 pts/4    00:00:00 grep --color=auto jira


      1. Windows; navigate to  Control Panel > Administrative Tools > Services. Find for Jira Service (the name varies depending on the specified name during the Service creation) and check for it's Status.
    2. If Jira is not installed as Service and Jira is started using Understand startup and shutdown scripts in Jira server:
      1. Linux; run the following command: ps -ef | grep jira
      Example of JIRA is running 
      osboxes@osboxes:/opt/atlassian/jira702/conf$ ps -ef | grep jira
root      9096  8286  0 10:29 pts/10   00:00:00 su - jira
jira      9097  9096  0 10:29 pts/10   00:00:00 -su
jira     11349  2859 99 11:32 ?        00:00:03 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
osboxes  11367 27426  0 11:32 pts/4    00:00:00 grep --color=auto jira
      Example of there is no JIRA is running 
      osboxes@osboxes:/opt/atlassian/jira702/conf$ ps -ef | grep jira
root      9096  8286  0 10:29 pts/10   00:00:00 su - jira
jira      9097  9096  0 10:29 pts/10   00:00:00 -su
osboxes  11478 27426  0 11:35 pts/4    00:00:00 grep --color=auto jira

    3. Windows; run the following command: tasklist|findstr java

      Example of JIRA is running 
      C:\Users\IT>tasklist | findstr java
java.exe                      6224 Console                    1    371,212 K

       If you have multiple Jiras running, you can use the following command to differentiate. Please replace <pid> the result from tasklist command.

      wmic.exe path Win32_Process where handle='<pid>' get name, commandline  /format:list
      Example of there is no JIRA is running 
      C:\Users\IT>tasklist | findstr jav

  2. Check in atlassian-jira.log to see if Jira is started successfully:

    1. At the end of Jira's core startup, there will be:

          *****************************************************************************************************************************
    Jira 8.12.0 build: 812001 started. You can now access Jira through your web browser. Plugins and caches are being initialised.
    *****************************************************************************************************************************

    2. At this point Jira will display the landing page in a browser while it intialises plugins and caches.

    3. Once Jira has finished initialising plugins and caches, you will see:

      localhost-startStop-1 INFO      [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.

    4. Jira is now fully initialised and accessible.

  3. If Jira is not accessible at this point, or there are errors and startup did not complete successfully, please get in touch with Atlassian Support by opening a ticket and upload the logs and configuration of your environment. If using Linux, you can upload a generated support zip file via command line with the Command Line Support Tool, if using Windows please compress and upload the contents of the following directories/files:


説明The purpose of this article is to list down some simple tests/checks that can be done to verify if Jira is running. This article can be used when Jira is inaccessible via web browser.
製品Jira
プラットフォームサーバー
最終更新日 2022 年 11 月 10 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する

関連コンテンツ

  • 関連コンテンツがありません
Powered by Confluence and Scroll Viewport.