2026.1 - Issues and Securty Hotspots not displaying

SonarQube Server / Community Build
1

SonarQube Version: 2026.1 - Enterprise Self Hosted (zip run as service)

Ever since moving to 2026.1, the overview is working properly, but when we try and click into the issues or security hotspots, the project displays shows “no issues!”. I am proving screenshots on an admin account.

I have re-indexed. I have deleted projects and started a brand new project and scan results from scratch. I even migrated to a brand new server due to sunsetting old infra. The only unchanged piece during all this is the external database server.

However, SOME projects work just fine. Not many, but some. There does not seem to be any pattern for the projects that are working correctly.

2

Hi,

I know you say you’ve reindexed, but this looks like a classic “bad Elasticsearch index” case. So I need to make sure: how did you reindex?

And can you try to force an ElasticSearch reindex one more time?

 
Thx,
Ann

3

Thanks for the response.

I turned off the service, deleted everything under /data/, and then turned the service back on. No change, same issue. No errors in the logs either.

However, I did notice the documentation states to use <sonarhome>/data now. Due to our Org’s OS requirements (carry over from when we were using Sonarqube 8), we have the ES stuff stored in /data and not inside sonar’s installation path (for us, /opt/sonarqube).

For the 2nd test on re-indexing, I moved away from our legacy setup of using /data and changed our config to just use the default path (/opt/sonarqube/data). After the re-index for this change, everything seems to be good now.

Is there a chance that 2026.1 Sonarqube doesn’t like data existing outside of Sonarqube’s dir? I revived the old sunset box, and changed the config to use sonarhome/data. This fixed the issue as well. We have been using the /data path for years now across multiple server migrations without issue.

4

Hi,

Thanks for sharing your investigations. I’m not aware of any changes to the location of the ES data, and the docs aren’t helping me in that regard.

I’m going to run this by the devs to see if we’ve missed a docs update.

 
Thanks again!
Ann

6

Based on my spotty memory, back in the 8.x era, there was a config property advertised (sonar.path.data) that you can use any path you want for the ES Data. It just had a caveat that you would need to create the initial */data folder and assign permissions accordingly. At startup, ES tries to create the ./es-data and ./es-temp folder. If permissions were wrong, Sonarqube will fail to startup. This is how we have been configuring out options ever since. We used this to change the default location due to our internal requirements.

It seems at some point the documentation stopped referencing this option in the initial setup, but we kept using it regardless. I can’t find it referenced anymore either hah. I am guessing it became recommended to always use the default path of sonarhome/data/*.

My 2 cents. Thanks for the fast responses like always.

1 Like