SQ 26.1.0.118079: sonarqube/temp/tmp directory fills up

SonarQube Server / Community Build
,
1
  • SonarQube 26.1.0.118079 Community Build
  • SonarQube deployed as zip

After upgrading to 26.1 the directory sonarqube-26.1.0.118079/temp/tmp started to slowly fill up until we run out of the disk space.

The sonarqube-26.1.0.118079/temp/tmp directory consists of *.tmp files which are ZIP archives that contain files such as analysis.log, lots of *.pb files and source-*.txt files.

Since we didn’t notice the use of this sonar/temp/tmp directory before (and when looking at the backup of the old sonarqube-25.9.0.112764 installation it doesn’t even exist there) it really looks like something new/recent. Or at least the job that was supposed to clean the directory doesn’t work anymore (or these tmp files should be deleted immediately after they aren’t needed any longer which doesn’t happen now).

For now, we’ll create a simple cron job at the operating system level to clean the directory, but this shouldn’t be necessary.

1 Like
3

I’ve searched the sources a little and it’s caused by changes introduced in this commit: SONAR-21454 Split the report in parts if too big · SonarSource/sonarqube@ae068c4 · GitHub

2 Likes
8

Hi,

Thanks for your investigation. That’s incredibly helpful. This is flagged for the team.

 
Ann

1 Like
9

Thanks for raising the issue and for the investigation, we will look at it promptly.

All my apologies for the inconvenience.

13

We identified that the files are not purged until the JVM running SonarQube is stopped. Until a proper fix is implemented, another workaround is to restart SonarQube to purge the files.

We are actively working on the fix.

15

Hi there,

The fix will be included in the next Community Build release, 26.2.

2 Likes
17

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.