Install JIRA on RedHat using the installer

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

When installing JIRA on Linux RedHat release 7.4 and CentOS 7 using the installation .bin file, the installation would fail with JIRA throwing the following error:

When making the following actions...

  • Download JIRA Installer

  • Set the installation file to runnable.

  • Run the installer from terminal.

  • Running JIRA even with the -c would still have throw the same error.

    1 sudo /tmp/atlassian-jira-software-7.5.0-x64.bin -c

The following appears in the terminal

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 $ sudo /tmp/atlassian-jira-software-7.5.0-x64.bin Unpacking JRE ... Starting Installer ... Could not display the GUI. This application needs access to an X Server. ******************************************************************* You can also run this application in console mode without access to an X server by passing the argument -c *******************************************************************

Diagnosis

Environment

  • RedHat 7.4

  • CentOS 7

Cause

The problem is caused by changes to the font type used by this version of RedHat as described here.

Solution

Workaround

Use the zip or tar.gz file to install JIRA instead.

Resolution

Follow the steps described in the answer section of this article to change the font used.

  • Should the issue persist, please raise a ticket with the Redhat team as this is an issue caused by the operating system and appears to impact Java applications.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.