SonarLint Fails to start with Eclipse

SonarQube for IDE IntelliJ Platform
, , , ,
27

Disabling Windows Defender firewall had no effect on the timeout-exception. Having firewall on or off also has no influence on the amount of node processes being started (I count 5 node.exe’s in taskmanager)

28

same here

Eclipse: Version: 2020-09 (4.17.0)
SonarLint: 5.5.2.24675

Using Node.js executable C:\Program Files\nodejs\node.exe from property sonar.nodejs.executable.
Checking Node.js version
Launching command C:\Program Files\nodejs\node.exe -v
Using Node.js v14.15.1.
Starting Node.js process to start eslint-bridge server at port 64700
Launching command C:\Program Files\nodejs\node.exe C:\Users\gerhard\workspace2\.sonarlint\work\pisco\.sonartmp_5669563592587798263\eslint-bridge-bundle\package\bin\server 64700
starting eslint-bridge server at port 64700
eslint-bridge server is running at port 64700
Failed to start server (60s timeout)
org.sonarsource.nodejs.NodeCommandException: Failed to start server (60s timeout)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServer(EslintBridgeServerImpl.java:113)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServerLazily(EslintBridgeServerImpl.java:170)
	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.execute(AbstractEslintSensor.java:106)
	at org.sonar.plugins.javascript.eslint.JavaScriptEslintBasedSensor.execute(JavaScriptEslintBasedSensor.java:49)
	at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.executeSensor(SensorsExecutor.java:80)
	at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.execute(SensorsExecutor.java:71)
	at org.sonarsource.sonarlint.core.container.analysis.AnalysisContainer.doAfterStart(AnalysisContainer.java:132)
	at org.sonarsource.sonarlint.core.container.ComponentContainer.startComponents(ComponentContainer.java:126)
	at org.sonarsource.sonarlint.core.container.ComponentContainer.execute(ComponentContainer.java:111)
	at org.sonarsource.sonarlint.core.container.storage.StorageAnalyzer.analyze(StorageAnalyzer.java:75)
	at org.sonarsource.sonarlint.core.container.storage.StorageContainerHandler.analyze(StorageContainerHandler.java:85)
	at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.lambda$analyze$0(ConnectedSonarLintEngineImpl.java:152)
	at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.withReadLock(ConnectedSonarLintEngineImpl.java:349)
	at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.withReadLock(ConnectedSonarLintEngineImpl.java:339)
	at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.analyze(ConnectedSonarLintEngineImpl.java:149)
	at org.sonarlint.eclipse.core.internal.engine.connected.ConnectedEngineFacade.lambda$13(ConnectedEngineFacade.java:354)
	at org.sonarlint.eclipse.core.internal.engine.connected.ConnectedEngineFacade.withEngine(ConnectedEngineFacade.java:147)
	at org.sonarlint.eclipse.core.internal.engine.connected.ConnectedEngineFacade.runAnalysis(ConnectedEngineFacade.java:353)
	at org.sonarlint.eclipse.core.internal.jobs.AnalyzeConnectedProjectJob.runAnalysis(AnalyzeConnectedProjectJob.java:70)
	at org.sonarlint.eclipse.core.internal.jobs.AnalyzeConnectedProjectJob.runAnalysis(AnalyzeConnectedProjectJob.java:1)
	at org.sonarlint.eclipse.core.internal.jobs.AbstractAnalyzeProjectJob.run(AbstractAnalyzeProjectJob.java:389)
	at org.sonarlint.eclipse.core.internal.jobs.AbstractAnalyzeProjectJob.runAnalysisAndUpdateMarkers(AbstractAnalyzeProjectJob.java:199)
	at org.sonarlint.eclipse.core.internal.jobs.AbstractAnalyzeProjectJob.doRun(AbstractAnalyzeProjectJob.java:161)
	at org.sonarlint.eclipse.core.internal.jobs.AbstractSonarProjectJob.run(AbstractSonarProjectJob.java:45)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
29

Hi folks,

We are still struggling to understand the problem. Another suspicion we have is a problem with local interfaces. The code that starts the ESLint server sometimes refers to “localhost”, sometimes uses Java InetAdddress.getLoopBack. Are you aware of anything specific on your computer around those local network interfaces (127.x)?

30

Update from my side: Did a fresh install of windows 20h2 for unrelated reasons. Saw this topic light back up and decided to test some more… After setting everything back up it seems to work properly now without anything special. I didn’t do anything different than last time. Only changes as far as I’m aware are: fresh windows install, latest jdk-11 release. Should have roughly the same programs installed as before too.

Will let you know if the situation changes. Thanks for the support.