After upgrading to Sonar to 4.2, I have errors on some projects with these logs :
The resource '...' is duplicated in database
I had to manually remove the duplicate lines in the database as i didn't know what is the snapshot that provokes this behavior, or if it's du to Database upgrade.
Hope to understand what has going on as i should upgrade other Sonar servers to version 4.2
The issue you're facing relates to a bug that we're currently investigating. Follow the following thread of discussion to get some news about the fix : http://sonar.markmail.org/thread/rgpwforpxm6elnc7
Related
SonarQube Community,
I upgraded from SonarQube 5.6 to 5.6.6 and the DB migration appeared to complete successfully.
Afterwards some of the projects summary data when drilling into the project does not show correctly while other projects do.
I have provide a link to the 3 items, two pngs showing visually what I am trying to communicate and the third with the log output from the upgrade and data migration.
I have rolled back to the old DB data as well as 5.6 and done this upgrade twice with the same outcome so it can be reproduced.
Is there something I need to know in doing this upgrade that I may have missed?
I have done several upgrades over the years and this is the first time I have seen this problem.
Thanks for any help you may be able to provide.
Doug
This is a case of a corrupted ElasticSearch index. It can be fixed by deleting _$SONARQUBE_HOME/data/es_.
From your comments, it looks like you carried over the ES index from your previous version. Instead, you should have
turned off your old version
exploded the zip for the new version
pointed the new version at your database
(re)installed your plugins
started the new version and allowed the ES indices to automatically (re)generate as part of the upgrade process
I'm working in the sonarqube 3.7.4. I analysed my java project and it clearly showing me the number of issues with the count. But while clicking the issues it results in "No matching issues found".
Please provide me the suggestion to fix the issues
You should upgrade to the latest LTS version of SonarQube : 4.5.6
I upgraded sonarqube to 5.2. I replaced the old instance with a new instance, so the old configuration was deleted and replaced.
I have several custom fxcop rules.
When running the analysis, I am getting the following error.
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: Unable to find the rule key corresponding to the rule config key "HSI1009" in repository "fxcop".
This is caused by empty entries in the sonar created file fxcop-sonarqube.ruleset file.
Does anyone know if this is a bug or some error on my end? I did not have these sorts of issues before the 5.2 upgrade, but unable to go back due to reliance on some plugins using 5.2.
I was only able to fix this by downgrading back to SonarQube 5.1.2. Even though I am using the same C# plugin (5.0) and the same runner version (2.5), upgrading to SonarQube 5.2 and up broke custom fxcop rules.
This problem has been fixed with the SonarQube Scanner for MSBuild v1.0.2+ : https://jira.sonarsource.com/browse/SONARMSBRU-151
Also be sure to run the SQ Scanner for MSBuild in a .NET 4.5.2 context.
Before I upgraded Sonar 5.0 I used the internal org.codehaus.sonar:sonar-maven-plugin:4.3.2. After the upgrade I used the same plugin in version 5.0 but got the error
Failed to execute goal org.codehaus.sonar:sonar-maven-plugin:5.0:sonar (default-cli) on project at.biac.offer.pom: Please update sonar-maven-plugin to at least version 2.3
Then I switched to org.codehaus.mojo:sonar-maven-plugin:2.5 but now I get the following error
org.sonar.jpa.session.DatabaseException: Database schema must be updated [version/required=721/170]. Please browse to your sonar homepage.
Is there any way to fix this problem without loosing my analysis data so far?
Database upgrade is a normal step when doing an upgrade of the SonarQube server. You should not lose any data.
I'm just upgrading our Sonar installation, from v3.5.1 to 3.6, and the process has been running for over two hours. Last log file entry was "Convert 508818 violations to issues" as the process was starting.
Now, the sonar site /setup is still showing "Sonar database is currently upgrading".
Is it correct that the upgrade of 500.000 violations to issues takes so much time?
Why does the log file is not being updated?
Thanks in advance.
Andreas
The upgrade from 3.5.1 to 3.6 can indeed last very long - but it will complete. You're facing this limitation: https://jira.codehaus.org/browse/SONAR-4470
This is mainly linked to performance issues on JRuby side (DB migration scripts are usually written on Rails side). As you can read in the ticket, we decided to rewrite this migration script in full Java and to provide a SonarQube 3.6.1 fix version.