java: not found during Stash startup
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products will end after 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
Problem
Stash fails to start and the following appears in the catalina.out:
./catalina.sh: 1: eval: /usr/lib/jvm/java-8-oracle/jre/bin/java/bin/java: not found
Cause
The JAVA_HOME environment variable isn't problem set, so Stash is looking for bin/java in the wrong place.
Resolution
- Adjust JAVA_HOME for the user running Stash. In the example above it should be
/usr/lib/jvm/java-8-oracle/jreinstead of/usr/lib/jvm/java-8-oracle/jre/bin/java. - If the path shown in the error persists, confirm JAVA_HOME was adjusted for the correct user.
- If JRE_HOME is also shown as the wrong path, confirms if there's a JRE_HOME variable set, adjusting it as well. If this isn't set, it's just going to take the value from JAVA_HOME.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.