Issues upgrading from 9.7.0

SonarQube Server / Community Build
,
1

Make sure to tell us:

  • What version are you upgrading from? 9.7.0.61562

  • System information (Operating system, Java version, Database provider/version): RHEL 7.9
    Java versions:
    openjdk version “18.0.2” 2022-07-10
    openJDK Runtime Environment 21.9 (build 18.0.2+9)
    openJDK 64bit server vm 21.9 (build 18.0.2+9, mixed mode, sharing)

  • What’s the issue you’re facing?

We followed the upgrade instructions to unzip /sonarqube/sonarqube-9.9.0.65466 and edit the sonar.properties using the same inputs as in the previous version. We are unable to get the service to start and remain running. We are not getting a se.log in our log folder. We are only getting a sonar.log and nohup.log either of which are really helping us with the problem.

In the sonar.log file we are seeing:

[o.s.a.p.AbstractManagedProcess] Process exited with exit rule [ElasticSearch]:1

In our journalctl we are seeing:

Exception in thread “main” java.lang.unsupposrtedoperationException: The security Manager is deprecated and will be removed at a future release at java.base/java.lang.system.SetsecurityManager(system.java:416)

We have tried numerous fixes and none of the threads we’ve found have this exact issue. We are not trying to run the sonar.sh script as root and we’ve done several reboots.

2

Hi,

Can you downgrade to Java 17 and try again?

Also, can you list all the files in your log directory?

 
Ann

3

What database server are you using?

I also saw today the unsupportedoperationException from security manager when upgrading from 9.4 to 9.9 LTS. But it was on Windows Server 2016 with OpenJDK 17.
As we are using MS SQL server the Release notes 9.6 gave a hint to use trustServerCertificate=true and therewith it was possible to get it running.

Obviously SonarQube will need to replace their current usage of SecutiryManager in the future.

1 Like