We Upgraded sonarqube from 9.8 to Sonarqube 9.9 community edition and after upgrading we cant see any projects and we are seeing the below message on the screen
An embedded database is used for evaluation purposes only. The embedded database will not scale, it will not support upgrading to newer versions of SonarQube, and there is no support for migrating your data out of it into a different database engine.
What do you make of that message in yellow at the bottom of your screen?
SonarQube only falls back to using the embedded DB when it’s not connected to an external DB. You should double-check your 9.9 configurations to make sure the DB connection details are properly and fully specified.
I checked the logs, and it is showing like this H2 database should be used for evaluation purpose only we also specified the db details in our configuration files
Your instance is using the - empty - H2 database embedded for evaluation purposes as a fallback because it wasn’t configured to connect to an external DB. You should double-check your configuration. Once you’ve successfully connected SonarQube to the old/existing DB and performed the migration step, you should see all your projects.
this is our configuration file, which is configured to connect to external DB
`dbUsername=postgres dbUrl=jdbc:postgresql://xxxxxxs.eu-central-1.rds.amazonaws.com:5432/sonar?sslmode=require&gssEncMode=disable azureClientID=abc ClusterName=xxxx ImageName=sonarqube:9.9.0-community
all the projects are loading when we are running on sonarqube 9.8.0 version but when we use the same db configuration, for sonarqube 9.9.0 then it is showing H2 database should be used…then i rolled back the sonarqube from 9.9.0 to sonarqube 9.8.0 then it is loading all the projects…so i want to know why this is happening eventhough we specify the correct db configuration and it is working for 9.8.0 but not for 9.9.0
We have gone through the upgrade notes, we couldn’t figure it out anything relevant to this issue, what we observe is it is not taking the external DB configurations instead it is taking the default H2 database.
Note: we are using cloudformation stack to deploy sonar application, above are the parameters which we are passing in parameters
when we go inside the docker container, then we can’t find run.sh and sonar.sh files under /opt/sonarqube/bin
I’m guessing somewhere you translate the values of dbUsername &etc into the recognized envvar names? You need to take a look at that step. Because, per the release notes, 9.9 dropped support for SONARQUBE_JDBC_*.
