Initial Analysis Fails on multiple projects


My issue involves attempting to perform analysis on a Windows machine for a simple maven project. The first issue that occurred (and has occurred on several other machines for .Net projects) is a Build Failure as follows


mvn sonar:sonar


[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.155 s
[INFO] Finished at: 2019-10-02T12:01:28-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin: (default-cli) on project : Unable to execute SonarQube: Fail to get bootstrap index from server: Failed to connect to localhost/0:0:0:0:0:0:0:1:9000: Connection refused: connect -> [Help 1]

The above issue seems to be because the analysis rejects the specified host ( and attempts to use localhost. Now this was (possibly) remediated by modifying settings.xml in $MAVEN_HOME, removing localhost as shown below and replacing it with


The error after is as follows that I am stuck on

[INFO] SCM provider for this project is: git
[INFO] 41 files to be analyzed
[INFO] 40/41 files analyzed
[WARNING] Missing blame information for the following files:
[WARNING] * pom.xml
[WARNING] This may lead to missing/broken features in SonarQube
[INFO] 3 files had no CPD blocks
[INFO] Calculating CPD for 37 files
[INFO] CPD calculation finished
[INFO] Analysis report generated in 947ms, dir size=949 KB
[INFO] Analysis report compressed in 374ms, zip size=294 KB
[INFO] ------------------------------------------------------------------------
[INFO] Skipping
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------

I’m not sure what blame information is or why the pom.xml is the cause. Or is this whole issue due to the project now being banned? Also if you have a more suitable answer for how to fix the first localhost issue that would help me with other stations also having that issue.

hello @Nater,

You can ignore warning about pom.xml for the time being, it only means that pom.xml file was not yet committed in git, so scanner couldn’t retrieve the blame information for it.

The “banning” of the project doesn’t come from the sonarqube scanner, it usually means that some module on which this project depends failed to build. Can you check that there isn’t some other failure somewhere higher in the logs? You can also run with -X parameter to get more debug information in the logs.

I noticed in your mvn sonar:sonar command you have duplicated -D option for sonar.organization, it should be just -Dsonar.organization=... , I am not sure if this is the source of the error.

Thanks for the response Tibor. The argument issue was a typo since I hand jammed this from screenshots of logs. After generating a new admin key this was resolved.