Jira Client for Linux: Understanding and Troubleshooting

When troubleshooting issues with your Jira client on a Linux system, logs can be a reliable means of understanding what was running. These logs should only contain a single version of each Service Desk and Jira Software, but it's possible that one or more of these have been disabled in Jira and are not being loaded.

One way to review the contents of both is by connecting to Jira using Python on Linux/UNIX, React, or Ruby. You can also use the /jira connect pluginid command to access the client without an access token.

Another approach is to manually review the files in the `$JIRAINSTALL/atlassian-jira/WEB-INF/application-installation` directory. This folder contains various versions of Jira software and plugins, making it harder to determine what version was used last. However, you can try searching for specific file names such as `jira-core-8.3.x.jar`, `jira-plugin-manager-8.3.x.jar`, `jira-software-8.3.x.jar`, etc.

If you don't see these files in the directory or corresponding logs, it may indicate that Jira was not installed or is not being used. You can also try searching for other strings such as 'JIRA starting' or 'JIRA shutting down' in the log file to determine when Jira starts up and what versions are currently installed.

In addition to reviewing logs and files, you can also check the certification path on your system by following these steps:

1. Open a terminal or command prompt.

2. Navigate to the `$JIRAINSTALL/atlassian-jira/WEB-INF` directory.

3. Run the `java -jar application.jar --debug` command to start Jira in debug mode.

4. Click on the 'Certification Path' option from the list of available options.

5. Select the root certificate and click on 'View Certificate'.

6. In the new window, click on the certificate details to view the certification path.

By following these steps, you can gain a better understanding of what is running on your Jira client and troubleshoot any issues that may arise.

Jira client linux