Fail to download plugin [cssfamily] into /home/user/.sonar/_tmp/fileCache8861767396753390681.tmp

My package.json:

{
  "name": "brandName",
  "version": "1.0.0",
  "description": "brandName",
  "main": "gulpfile.js",
  "private": true,
  "scripts": {
    "postinstall": "find node_modules/ -name \"*.info\" -type f -delete",
    "audit:check": "node node_modules/npm-audit-resolver/check",
    "audit:resolve": "node node_modules/npm-audit-resolver/resolve",
    "deploy": "gulp deploy",
    "sonarqube": "sonarqube-scanner-node"
  },
  "author": "Engineers <engineers@something.info>",
  "license": "ISC",
  "devDependencies": {
    "gulp": "^4.0.2",
    "minimist": "^1.2.5",
    "npm-audit-resolver": "^2.2.0",
    "sonarqube-scanner": "^2.7.0",
    "sonarqube-scanner-node": "0.0.10"
  },
  "dependencies": {
    ---------
  }
}

Command used to run sonarQube : npm run sonarqube

  • versions used (SonarQube ^2.7.0, Scanner 0.0.10)
ERROR: Error during SonarQube Scanner execution
ERROR: Fail to download plugin [javascript] into /home/userName/.sonar/_tmp/fileCache1640509318682103808.tmp
ERROR: Caused by: unexpected end of stream
ERROR:
ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
child_process.js:637
    throw err;

ERROR: Error during SonarQube Scanner execution
ERROR: Fail to download plugin [go] into /home/userName/.sonar/_tmp/fileCache5638733885361493353.tmp
ERROR: Caused by: unexpected end of stream
ERROR:

Whenever I run sonar scanner am getting these plugins not found. Everytime the different plugins.
() ERROR: Fail to download plugin [go] into
(
) ERROR: Fail to download plugin [javascript] into

Complete log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'sonarqube' ]
2 info using npm@6.4.1
3 info using node@v10.15.3
4 verbose run-script [ 'presonarqube', 'sonarqube', 'postsonarqube' ]
5 info lifecycle brandName@1.0.0~presonarqube: brandName@1.0.0
6 info lifecycle brandName@1.0.0~sonarqube: brandName@1.0.0
7 verbose lifecycle brandName@1.0.0~sonarqube: unsafe-perm in lifecycle true
8 verbose lifecycle brandName@1.0.0~sonarqube: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/u02/home/userName/drupal/drupal-7.9/sites/brandName/node_modules/.bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/webop/perlgem_tools/bin:/home/userName/.local/bin:/home/userName/bin:/u01/perlgem_eng/tools/bin:/home/webop/perlgem_tools/bin
9 verbose lifecycle brandName@1.0.0~sonarqube: CWD: /u02/home/userName/drupal/drupal-7.9/sites/brandName
10 silly lifecycle brandName@1.0.0~sonarqube: Args: [ '-c', 'sonarqube-scanner-node' ]
11 silly lifecycle brandName@1.0.0~sonarqube: Returned: code: 1  signal: null
12 info lifecycle brandName@1.0.0~sonarqube: Failed to exec sonarqube script
13 verbose stack Error: brandName@1.0.0 sonarqube: `sonarqube-scanner-node`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:189:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:189:13)
13 verbose stack     at maybeClose (internal/child_process.js:970:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid brandName@1.0.0
15 verbose cwd /u02/home/userName/drupal/drupal-7.9/sites/brandName
16 verbose Linux 3.10.0-1062.9.1.el7.x86_64
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "sonarqube"
18 verbose node v10.15.3
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error brandName@1.0.0 sonarqube: `sonarqube-scanner-node`
22 error Exit status 1
23 error Failed at the brandName@1.0.0 sonarqube script.
24 verbose exit [ 1, true ]

Am running sonarQube from my linux server. Any help is appreciated.

Hi,

For the record, the npm scanner isn’t supported by SonarSource, but I think that’s beside the point here.

I suspect you have a proxy or other “helpful” software on your network that’s causing this problem. You should look there first.

 
HTH,
Ann