Fail to parse entry in bootstrap index

ERROR:

ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.

ERROR: Error during SonarQube Scanner execution

org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarQube

at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(IsolatedLauncherFactory.java:85)

at java.base/java.security.AccessController.doPrivileged(Native Method)

at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:74)

at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(IsolatedLauncherFactory.java:70)

at org.sonarsource.scanner.api.EmbeddedScanner.doStart(EmbeddedScanner.java:185)

at org.sonarsource.scanner.api.EmbeddedScanner.start(EmbeddedScanner.java:123)

at org.sonarsource.scanner.cli.Main.execute(Main.java:73)

at org.sonarsource.scanner.cli.Main.main(Main.java:61)

Hello @vishal_linu,

Please remind that this is a community forum where people offer their time to help others. Standard politeness and courtesy apply. Also explaining what you are doing, what you expect vs what you have usually help to spot any issue.

From what I can see, you should check the availability of your SonarQube instance (sonar.host.url) because it simply appears to be not reachable. Availability here includes network rules, SSL handshake, etc. Basically making sure that the scanner can communicate to the SonarQube server.

Antoine

1 Like

Thanks for the reply

I am trying to connect sonar qube from azure ci/cd pipelines and i also have the sonar.host.url configured in the config file and the sonar server is on-prem

I have no SSL for on prem