After migrating JIRA from a server to another, can't execute the embedded JAVA command
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
Symptoms
JIRA won't boot up after migrating it from a server to another. When trying to start JIRA, the following error will occur:
1
/opt/atlassian/jira/jre/bin/java: No such file or directoryWhen running the command file /opt/atlassian/jira/jre/bin/java, the following output may be displayed:
1
2
# 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 strippedIndicating the java command does exist but can't be executed.
Cause
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.
Resolution
Browse to www.atlassian.com and download the JIRA version according to your operational system and architecture.
ℹ️ You may need to re-move the old JIRA installation package and install a new one.
ℹ️ 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.
Was this helpful?