JIRA won't start after upgrade from 7.7.1 to 8.13.9

[Lisa Ruby]

I just upgraded from JIRA Server 7.7.1 to 8.13.9 on Windows 8.1 using the installer (so overwrote my previous version) and JIRA won't start. I read through all of the documentation on upgrading and did everything I thought I needed to do. I upgraded my Postgres database to a version supported by both 7.7.1 and 8.13.9 (9.6.22) before I did the upgrade. The upgraded database worked fine with 7.7.1.

JIRA is installed in C:\Program Files\Atlassian\Application Data\JIRA

My JIRA HOME location is D:\mysoftware\Atlassian\Application Data\JIRA

My normal JAVA_HOME environment variable is set to:
JAVA_HOME=C:\Program Files\AdoptOpenJDK\jdk-11.0.9.11-hotspot

Everything seemed to go OK with the upgrade, but now JIRA won't start. For 7.7.1 I had JIRA running as a Windows service. That service is gone and a Service for 8.13.9 was not added. There was no option that I saw during the install for running it as a service. Since it deleted the previous service I would assume it knew the server was running as a server. 

I tried manually installing as a service and it didn't work. I can't seem to paste in the output from doing that. 

Then I tried manually starting JIRA using start-jira.bat (run in command window as administrator), which also failed. 

Here is the initial output from my first attempt at running start-jira.bat:

C:\Program Files\Atlassian\JIRA\bin>start-jira.bat

To run Jira in the foreground, start the server with start-jira.bat /fg

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.13.9

The system cannot find the path specified.

If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at
https://docs.atlassian.com/jira/jadm-docs-0813/Troubleshooting+installation

Using CATALINA_BASE: "C:\Program Files\Atlassian\JIRA"
Using CATALINA_HOME: "C:\Program Files\Atlassian\JIRA"
Using CATALINA_TMPDIR: "C:\Program Files\Atlassian\JIRA\temp"
Using JRE_HOME: "C:\Program Files\Atlassian\JIRA\jre\"
Using CLASSPATH: "C:\Program Files\Atlassian\JIRA\bin\bootstrap.jar;C:\Program Files\Atlassian\JIRA\bin\tomcat-juli.jar"
Using CATALINA_OPTS: ""
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
: 'version': No such file or directory
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
find: 'version': No such file or directory
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
find: 'version': No such file or directory
****************************************************************************
******* Wrong JVM version! Jira requires 1.8 or 11 to run. *******
****************************************************************************
***
*** Output of java -version command is:
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)
*** (End of output) ***
***
*** If you want JIRA to start using this JVM
*** set environment variable 'ignore_jvm_version' to 'true'
***
****************************************************************************

I tried setting ignore_jvm_version to true and running start-jira.bat again, and then ended up with the output below. Apparently there is something wrong with the scripts or some other executable that can't handle the space in 'Program Files'.  That certainly isn't anything new with the normal install location for applications in Windows. 

C:\Program Files\Atlassian\JIRA\bin>start-jira.bat

To run Jira in the foreground, start the server with start-jira.bat /fg

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.13.9

JAVA_HOME "C:\Program Files\Atlassian\JIRA\jre\" contains spaces. Please change to a location without spaces if this causes problems.

If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-0813/Troubleshooting+installation

Files\Atlassian\JIRA\jre\\bin\java.exe"" was unexpected at this time.

Does anyone know of a fix or workaround for this? Thank you. 

[Lisa Ruby · Accepted solution]

Solved my problem. The batch file check-java.bat, which gets run when starting JIRA from the command line using start-jira.bat calls the Windows find command. I have cygwin installed on my computer and the cygwin/bin directory is at the front of my PATH environment variable because I prefer the cygwin tools to the Windows command line tools. This caused the cygwin find command to be run when check-java.bat called find, which caused syntax problems. I removed the cygwin\bin  directory from my PATH variable and JIRA started.

If the JIRA upgrade had installed JIRA as a service, like I had it with the previous version, this wouldn't have been a problem. There was no option in the installation to tell it to install as a service. It removed the service for version 7.7.1 that I upgraded from, and did not install the service for 8.13.9. I have now installed the service. 

[Kishan Sharma]

Hi Lisa,

Can you try to install your JDK in a folder which doesn't have space in it eg: something like  C:\Java\jdk1.8.0_65

Refer this link for details, 

[Lisa Ruby]

Thank you for replying. 

I can try that, but I think there will still be problems with the path to catalina. And when it couldn't deal with the path to my JAVA install it tried using the jre distributed with the installation and had the same problem with the space in Program Files because the JAVA install is in Program Files. Seems pretty broken. 

I renamed my new install and went back to my old one. I see in all of the batch files in 7.7.1 they were using %~dp0 to convert paths to their short versions without the spaces. The new scripts in 8.13.9 don't do that.

[Ismael Jimoh]

I believe windows has this shortened format for various directions for example Program Files becomes something like PROGRA~1.

I will check if this helps and restart the application.

[Ismael Jimoh]

Also explained in detail here: https://confluence.atlassian.com/adminjiraserver/installing-java-938846828.html

regards.

[Lisa Ruby]

I tried changing into the JIRA install bin directory using PROGRA~1 (C:\PROGRA~1\Atlassian\JIRA\bin) and setting the JAVA_HOME and JAVA_JRE environment variables using PROGRA~1 and it's still failing. Don't have time to paste all the results in here now. I will investigate more when I can get back to this. For now I've gone back to running 7.7.1. I had to recreate the 7.7.1 Windows service and I did have to set JAVA_HOME using PROGRA~1 rather than Program Files to get the batch file that installs the service to run. But it worked in 7.7.1. Maybe I ran into some other error I need to investigate in 8.13.9, but it still looked like it was running into the Program Files path somewhere. 

[theresat]

I'm totally new to Confluence. I have made a page, put a table in it, have imparted it to my group. <a href="https://vatcalculatorlive.co.uk/"> VAT Calculator </a> Presently I need to have the option to channel the table on a worth in a table segment. How would I do it?

[Lisa Ruby]

@theresat

You need to open a new question. You put your question in as a reply to my question regarding a problem with JIRA not starting after an upgrade. Your issue is unrelated and people are not likely to see your question. 

[Ismael Jimoh]

@Lisa Ruby 

Any progress with your review of the instance logs?

I will suggest cleaning out the old log files and then tailing the logs so we can see where it’s failing at for example.

Regards.

[Lisa Ruby]

@Ismael Jimoh 

Thank you for checking back. I am not able to work on this again until next week. I will post again after I start working on it again next week. 

Regards

[Lisa Ruby]

@Ismael Jimoh 

I went back to JIRA 7.7.1 and ran the upgrade again, just in case something went wrong when I did it the first time. No change. Still can't start JIRA 8.13.9.
Setting JAVA_HOME and/or JRE_HOME using PROGRA~1 instead of Program Files in the path does not help. I tried using my AdoptOpenJDK jre 11.0.9+ and also tried the jre shipped with JIRA. I still get the same errors as before. I have pasted the output from start-jira.bat below. The Atlassian log directory in the JIRA install directory is empty. The logs in the JIRA Home directory (I think that's what it's called) have no entries from me trying to start JIRA 8.13.9. Seems it's not getting far enough to try to log anything. 

C:\PROGRA~1\Atlassian\JIRA\bin>start-jira.bat

To run Jira in the foreground, start the server with start-jira.bat /fg

                  `sMMMMMMMMMMMMMM+

                     MMMMMMMMMMMMMM

                     :sdMMMMMMMMMMM

                             MMMMMM

          `sMMMMMMMMMMMMMM+  MMMMMM

             MMMMMMMMMMMMMM  +MMMMM

              :sMMMMMMMMMMM   MMMMM

                     MMMMMM    `UOJ

   `sMMMMMMMMMMMMM+  MMMMMM

     MMMMMMMMMMMMMM  +MMMMM

      :sdMMMMMMMMMM   MMMMM

             MMMMMM    `UOJ

             MMMMMM

             +MMMMM

              MMMMM

               `UOJ

      Atlassian Jira

      Version : 8.13.9

If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-0813/Troubleshooting+installation

Using CATALINA_BASE:   "C:\PROGRA~1\Atlassian\JIRA"

Using CATALINA_HOME:   "C:\PROGRA~1\Atlassian\JIRA"

Using CATALINA_TMPDIR: "C:\PROGRA~1\Atlassian\JIRA\temp"

Using JRE_HOME:        "C:\PROGRA~1\Atlassian\JIRA\jre"

Using CLASSPATH:       "C:\PROGRA~1\Atlassian\JIRA\bin\bootstrap.jar;C:\PROGRA~1\Atlassian\JIRA\bin\tomcat-juli.jar"

Using CATALINA_OPTS:   ""

find: '/V': No such file or directory

find: 'JDK_JAVA_OPTIONS': No such file or directory

: 'version': No such file or directory

The process tried to write to a nonexistent pipe.

find: '/V': No such file or directory

find: 'JDK_JAVA_OPTIONS': No such file or directory

find: 'version': No such file or directory

The process tried to write to a nonexistent pipe.

find: '/V': No such file or directory

find: 'JDK_JAVA_OPTIONS': No such file or directory

: 'version': No such file or directory

The process tried to write to a nonexistent pipe.

****************************************************************************

*******      Wrong JVM version! Jira requires 1.8 or 11 to run.      *******

****************************************************************************

***

*** Output of java -version command is:

openjdk version "1.8.0_292"

OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)

OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)

*** (End of output) ***

***

*** If you want JIRA to start using this JVM

*** set environment variable 'ignore_jvm_version' to 'true'

***

****************************************************************************

C:\PROGRA~1\Atlassian\JIRA\bin>

--------------------------------------

If I set ignore_jvm_version to true then I get this:

C:\PROGRA~1\Atlassian\JIRA\bin>start-jira.bat

To run Jira in the foreground, start the server with start-jira.bat /fg

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.13.9

If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-0813/Troubleshooting+installation

Using CATALINA_BASE: "C:\PROGRA~1\Atlassian\JIRA"
Using CATALINA_HOME: "C:\PROGRA~1\Atlassian\JIRA"
Using CATALINA_TMPDIR: "C:\PROGRA~1\Atlassian\JIRA\temp"
Using JRE_HOME: "C:\PROGRA~1\Atlassian\JIRA\jre"
Using CLASSPATH: "C:\PROGRA~1\Atlassian\JIRA\bin\bootstrap.jar;C:\PROGRA~1\Atlassian\JIRA\bin\tomcat-juli.jar"
Using CATALINA_OPTS: ""
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
find: 'version': No such file or directory
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
find: 'version': No such file or directory
find: '/V': No such file or directory
find: 'JDK_JAVA_OPTIONS': No such file or directory
find: 'version': No such file or directory
****************************************************************************
******* Wrong JVM version! Jira requires 1.8 or 11 to run. *******
****************************************************************************
***
*** Output of java -version command is:
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)
*** (End of output) ***
***
*** Environment variable 'ignore_jvm_version' is set to 'true'
*** JIRA is going to bypass restriction and run using existing JVM version
***
****************************************************************************
9 was unexpected at this time.
C:\PROGRA~1\Atlassian\JIRA\bin>

[Lisa Ruby]

I just found the problem. I started searching the JIRA\bin bat files for some of the error messages I pasted in above. The issue is that check-java.bat is wanting to use the Windows find command and I have cygwin installed and the cygwin\bin directory comes first in my system PATH environment variable setting.  So the cygwin find command was running rather than Windows find. I removed cygwin from the path and JIRA now starts. 

[Ismael Jimoh]

Thanks for sharing the root cause here.

Glad you have the issue resolved now.

[Engineering_Licensing_ualberta_ca]

I am having the same error but I do not have cygwin installed. Any ideas?

[Ismael Jimoh]

@Engineering_Licensing_ualberta_ca in the case here, it was Cygwin, I would check if I have any application using Java that overwrites the default behaviour of JIRA.

We would need to see what the exact error you get is and also as suggested above if you are the server administrator, expect that you review what JAVA applications you may have that are based on JAVA and may have led to the issue.

Regards.