SonarCloud ERROR: Failed to start server (300s timeout) Error - Initial 1st Scan

Initial scan after deploying everything with integration to Bitbucket, running scan got the following error:

`INFO: Deploying custom rules bundle jar:file:/root/.sonar/cache/06b160cbad8e9f8df7328b1a2c5a0afe/sonar-securityjsfrontend-plugin.jar!/js-vulnerabilities-rules-1.0.0.tgz to /opt/atlassian/pipelines/agent/build/.scannerwork/.sonartmp/eslint-bridge-bundle/package/custom-rules8157227769959478266`
`ERROR: Failed to start server (300s timeout)`
`org.sonarsource.nodejs.NodeCommandException: Failed to start server (300s timeout)`
`	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServer(EslintBridgeServerImpl.java:135)`
`	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServerLazily(EslintBridgeServerImpl.java:212)`
`	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.execute(AbstractEslintSensor.java:66)`
`	at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:62)`
`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:75)`
`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1(ModuleSensorsExecutor.java:48)`
`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy(ModuleSensorsExecutor.java:66)`
`	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:48)`
`	at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:64)`
`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`
`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`
`	at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:446)`
`	at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:442)`
`	at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:400)`
`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`
`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`
`	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:128)`
`	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)`
`	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)`

`	at org.sonar.batch.bootstrapper.Batch.doExecute(Batch.java:58)`
`	at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:52)`
`	at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:46)`
`	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)`
`	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)`
`	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)`
`	at java.base/java.lang.reflect.Method.invoke(Method.java:566)`
`	at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)`
`	at com.sun.proxy.$Proxy0.execute(Unknown Source)`
`	at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:189)`
`	at org.sonarsource.scanner.api.EmbeddedScanner.execute(EmbeddedScanner.java:138)`
`	at org.sonarsource.scanner.cli.Main.execute(Main.java:112)`
`	at org.sonarsource.scanner.cli.Main.execute(Main.java:75)`
`	at org.sonarsource.scanner.cli.Main.main(Main.java:61)`

Which follows later on with this: (I changed the filename to )

INFO: Sensor Ruby Sensor [ruby]
INFO: 2 source files to be analyzed
INFO: 0/2 files analyzed, current file: <filen name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb
INFO: 0/2 files analyzed, current file: <file name>.rb

and at the end, ended with:

Failed

Container ‘docker’ exceeded memory limit.

Any idea how to solve this so that the scan will finish?

Hi,

What version of Node.js is installed on your build agent?

 
Ann

This actually was solved by setting a higher memory in the pipline.yml in bitbucket

1 Like

Hi,

Thanks for the followup! This will help others in the future!

 
:smiley:
Ann