After migrating JIRA from a server to another, can't execute the embedded JAVA command

Still need help?

The Atlassian Community is here for you.

Ask the community


JIRA won't boot up after migrating it from a server to another. When trying to start JIRA, the following error will occur:

/opt/atlassian/jira/jre/bin/java: No such file or directory

When running the command file /opt/atlassian/jira/jre/bin/java, the following output may be displayed: 

# file /opt/atlassian/jira/jre/bin/java
/opt/atlassian/jira/jre/bin/java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped

Indicating the java command does exist but can't be executed.


This is probably occurring because the new server is a 64 bit Linux, when the old one is a 32 bit one – or vice-versa. 


  • Browse to and download the JIRA version according to your operational system and architecture.
    (info) You may need to re-move the old JIRA installation package and install a new one.

    (info) OS-related questions are out of the support scope, so you may need to contact the OS vendor to get any further assistance on the server side.

Last modified on Nov 2, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.