Issue with Upgrade from Version 10.6.92116 to 10.7.0.96327

Hello everyone,

We recently upgraded SonarQube on our server from version 10.6.92116 to 10.7.0.96327.

After the upgrade, we were prompted to update the database, so we navigated to <SERVER_URL>/setup and clicked on “Upgrade Database.” Unfortunately, we received an error message during the update process, and SonarQube subsequently began a continuous restart loop.

We then restored the snapshots and attempted the update again, but encountered the same issue.

We haven’t found any error messages in the logs, which makes troubleshooting challenging.

For now, we’ve rolled back to version 10.6.92116, which appears to be working correctly.

Has anyone else faced this problem or might have suggestions for resolving it?

Thank you in advance for any insights!

Hi,

Could you bump up your server log levels to DEBUG in the configuration and try this again? Hopefully we’ll get something in the logs this time to give us a starting place.

 
Thx,
Ann

Hi Ann,
thank you for your response.
We already did this in our second attempt previously mentioned, unfortunately nothing changed in the logs.

Thanks,
Marco

Hi Marco,

If DEBUG didn’t add anything, can you go further, to TRACE?

Also, how are you running SonarQube, and what’s your OS?

 
Ann

Hi,

We can attempt to run it again, but since this machine is only accessible during scheduled maintenance sessions, it won’t be possible to address immediately. It seems, however, that the logs aren’t capturing any entries because the service fails to start after initiating the DB update.

Our system configuration is as follows:

Operating System: Red Hat Enterprise Linux release 8.7

Database: Microsoft SQL Server 13.00.4259

Driver: Microsoft JDBC Driver 12.6 for SQL Server (12.6.1.0)

1 Like

Hi,

Uhm… SonarQube has to be running in order for you to initiate the DB update…?

 
Ann

Certainly, SonarQube starts after the update using the zip file. However, when the DB upgrade is executed, it throws an error, causing the service to stop and continuously attempt to restart without success. We don’t see any entries in the log from that point onward.

Thanks,
Marco

Hi Marco,

It’s this error that I’m trying to capture. Hopefully TRACE will do it. Or at least give us an idea of what was going on when it happened.

 
Ann

We’ll run an upgrade with the log level set to TRACE over the next few days and will update you on the results.

Thank you very much

1 Like