Upgraded SonarQube 9.9.0 to 10.1 and some projects are not visible

Hi,

Did you find anything in my logs?

Hello,

The logs you’re sending me are not the right one. They are from the 16th of August:

2023.08.16 21:16:49 INFO  app[][o.s.a.SchedulerImpl] SonarQube is operational
2023.08.16 21:18:39 INFO  app[][o.s.a.SchedulerImpl] Stopping SonarQube

Can you repeat the steps and make sure to send me the right logs and the time at which you started SQ?

Cheers,
Aurélien

I did exactly when you said but I will do it again and send you the logs. It appears that sonar is not writing new logs. See below:

[root@ip-10-240-145-250 sonarqube-9.9.0.65466]# pwd
/opt/sonarqube-9.9.0.65466
[root@ip-10-240-145-250 sonarqube-9.9.0.65466]# ll
total 108
drwxr-xr-x 6 sonarqube sonarqube 96 Feb 3 2023 bin
drwxr-xr-x 2 sonarqube sonarqube 66 Aug 16 19:27 conf
-rw-r–r-- 1 sonarqube sonarqube 7651 Feb 3 2023 COPYING
drwxr-xr-x 4 sonarqube sonarqube 46 Mar 11 15:33 data
-rw-r–r-- 1 sonarqube sonarqube 90320 Feb 3 2023 dependency-license.json
drwxr-xr-x 7 sonarqube sonarqube 132 Aug 16 21:16 elasticsearch
drwxr-xr-x 5 sonarqube sonarqube 57 Mar 11 15:34 extensions
drwxr-xr-x 5 sonarqube sonarqube 132 Feb 3 2023 lib
drwxr-xr-x 2 sonarqube sonarqube 4096 Aug 16 16:31 logs
drwxr-xr-x 5 sonarqube sonarqube 92 Aug 16 21:18 temp
drwxr-xr-x 5 sonarqube sonarqube 4096 Feb 3 2023 web
[root@ip-10-240-145-250 sonarqube-9.9.0.65466]#

If I send you the logs again, it will be still be the one from Aug 16. I change directory to “logs”, the last time the files there was modified is Aug 16

I see some logs in /var/log/messages and it appears that log4j is trying to remediate it self. Please review the attached logs and let me know if you know what it it. other than that, every other logs are not updating itself aside from the messages. other logs are still stuck to Aug 16

There seems to be a problem with your environment / configuration.

One possibility is that you still have an instance running somewhere that prevents the new one to create fils. Please make sure with ps command that no sonar processes are left.

Otherwise, there might directory/file permissions issues.

I would recommend to try to kill all sonar processes, install SonarQube from scratch in a new location (pointing to the same DB), and try to start from there.

We have a production SonarQube server and I create a clone of the Production SonarQube server to use as a Staging environment. So yes, there is another SonaQube instance that is running. However, The 2 SonarQube are pointing to different database. The cloned server(staging environment) is pointing to the database backup that I created before all this. In our case, we cannot install sonarqube from ground up, we want to upgrade the existing sonarqube version that we have.

Question for you, If I install a brand new SonarQube server and point it to the same database, I would expect to see all our project, is that correct?

Yes, the new installation will use the data already present in the DB. Please make sure to make a DB backup before you start a new version of SonarQube with the same DB (as recommended in our documentation).