Cannot upgrade Confluence from 7.2.2 to 7.3 or 7.4

[Roger_Staerk]

Hi there

Since the v7.2.2 from Atlassian Confluence Server (onPremise Windows 2019) we cannot upgrade anymore to an newer version... 

During the Upgrade from the Installer we get th following error:

"com.install4j.runtime.beans.actions.control.runscriptaction failed"

We can just abort, retry or ignore... In any cases, the instance will not start after finish... And we have to go back with the ssapshot to v7.2.2.

There was never a Java standalone or something similiar installed on this new server...

Thanks for an idea...

Roger

[Tinker Fadoua · Accepted solution]

@Roger_Staerk 

• Did you check all the system requirements of the version you will be migrating to?
• Did you run a plugin check and disabled any incompatible plugins?
• Do you have enough space on the server?
• what other errors are you seeing on the logs?

Please let me know so that I can better assist you.

Best,

Fadoua

[Roger_Staerk]

Hi Fadoua

Many thanks for your answer...

I think I have checked all requirements... And this problem occures since every upgrade from v7.2.2 onward... 

What do you mean which logs I should looking for? Windows protocoll or the upgrade logs?

Thanks for your help...

Roger

[Roger_Staerk]

I think there is enough space  and I have already made the upgrade plan...

[Roger_Staerk]

And here are our Addins/Apps... just a few... And we use these for years now...

[Roger_Staerk]

We use the Java 1.8 - it was installed with the Confluence Windows Installer...

There was never another Java instance or something similiar on this server...

Do you think we have to upgrade to Java 11 before we upgraded to Confluence 7.4?

And how can we do this? 

[Tinker Fadoua]

@Roger_Staerk 

You are a DataCenter(DC) user. How many nodes do you have?

Please confirm as upgrading DC is little bit different than server.

Best,

Fadoua

[Roger_Staerk]

Hello Fadoua

No, we use a Standalone, onpremise Server Edition, running on a Windows 2019 Server...

Not a DataCenter Edition...

[Tinker Fadoua]

@Roger_Staerk going back to your Java Question:

• You can only run Confluence with AdoptOpenJDK or Oracle JRE/JDK. 
• Some Oracle Java versions have bugs that impact Confluence. You can't run Confluence on Java 1.8.0_25 and 1.8.0_31 (see JDK-8059299) or Java 1.8.0_45 (see JDK-8068400).
• Some AdoptOpenJDK versions have bugs that impact Confluence. We recommend version jdk8u202 (see CONFSERVER-58784).
• You can't run Confluence on the OPENJ9 JVM from AdoptOpenJDK. Use the HotSpot JVM. 

Good to know:

• You don't need to install Java if you plan to use the installer to install Confluence, as a Java 11 JRE is bundled with Confluence (provided by AdoptOpenJDK).

Best,

Fadoua

[Roger_Staerk]

Hi Fadoua

Thanks for this update... 

Yes, I saw this... And I thought that when we download the 64Bit windows Installer from Confluence, and install this over our v7.2.2, this installer will upgrade also Jave  to v11 JRE...

But it looks that this is not happen... Or we do not see / recognice that there will be an Java upgrade during confluence upgrade....

The only error is as described on top "com.install4j.runtime.beans.actions.control.runscriptaction failed"

So my question.. how we can upgrade Java? Or do you mean we have first run jdk8u202  and after that doing the confluence upgrade to v7.4.0?

Thanks for your help and have a good evening...

Roger

[Tinker Fadoua]

I will definitely suggest you to install the required Java version before you upgrade Confluence. I had that issue recently while working on a customer server. The very first step was to take care of Java otherwise Confluence won't work.

Also make sure to set the path to the Java directory in setenv.bat file.

Have a great weekend @Roger_Staerk !

Best,

Fadoua

[Roger_Staerk]

Hello Fadoua

Thanks, I tried this workaround... before I upgrade to v7.4

Workaround

Downgrade the bundled Java AdoptOpenJDK from 1.8.0_222-10 to previously bundled JVM (i.e. 1.8.0_202-b08) resolves the issue.

 Substitute C:\Program Files\Atlassian\Confluence below if you have Confluence installed in a non-default location.

1. Download AdoptOpenJDK 8u202-b08 from https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/download/jdk8u202-b08/OpenJDK8U-jre_x64_windows_hotspot_8u202b08.zip
2. Shutdown Confluence
3. Rename C:\Program Files\Atlassian\Confluence\jre to C:\Program Files\Atlassian\Confluence\jre8u222-b10
4. Extract OpenJDK8U-jre_x64_windows_hotspot_8u202b08.zip to C:\Program Files\Atlassian\Confluence - it will extract with a sub-directory called jdk8u202-b08-jre
• Rename the new C:\Program Files\Atlassian\Confluence\jdk8u202-b08-jre to C:\Program Files\Atlassian\Confluence\jre
5. Start Confluence and Collaborative Editing should now start

But I got the same error....

Any other idea?

Thanks....

Roger

[Tinker Fadoua]

I am assuming this is a test server.

Can we redo everything from scratch?

There is a log under <install-Directory>/log/catalina.out

I want you to check the errors there.

Please let me know or if you can share a copy from the log after hiding any confidential information.

Best,

Fadoua

[Roger_Staerk]

Hi Fadoua

I did it now... :-)

BUT this time... First I upgraded with Confluence installer - and get this error message during the setup "com.install4j.runtime.beans.actions.control.runscriptaction failed" ( I think in the moment who want the installer delete the org directory  before copy the new staff).

And with this error, i click "ignore" and let the installer finish...

And after that, I replace the JRE with the following source:

OpenJDK8U-jre_x64_windows_hotspot_8u252b09.zip

Very strange, isn't? But for now it is running... And i'm wonder what happens when the next release will coming...

Thanks, Roger

[Roger_Staerk]

And here are the catalina.logs - maybe you will see the problem....

[Roger_Staerk]

ups, sorry... how can I attach the log-files here?

[Tinker Fadoua]

Copy/paste the file that's the only way to do it :)

[Roger_Staerk]

catalina.2020-04-24.log

[Roger_Staerk]

sorry...  copy/paste will not work... the logs are only 25kb

[Roger_Staerk]

maybe you can post here an email-address, so that I can send you the logs as files...

cheers, roger

[Tinker Fadoua]

Fadoua.boualem@gmail.com

[Tinker Fadoua]

@Roger_Staerk  the logs are not showing any errors. Really weird!!!