Please report this error at: npm ERR! <>

(Wb666greene) #1

Installing node-red on fresh Ubuntu-Mate 16.04 install.

used the script:
bash <(curl -sL

Did node-red-start, opened my browser and used Manage Pallet to install node-red-node-base64 and got this error in the logs:

23 Jan 20:48:15 - [info] Installing module: node-red-node-base64, version: 0.1.3 23 Jan 20:48:16 - [warn] Installation of module node-red-node-base64 failed: 23 Jan 20:48:16 - [warn] ------------------------------------------ 23 Jan 20:48:16 - [warn] Unhandled rejection Error: EACCES: permission denied, mkdir '/home/ai/.npm/_cacache/index-v5/24/bc' npm ERR! cb() never called! npm ERR! This is an error with npm itself. Please report this error at: npm ERR! <> npm ERR! A complete log of this run can be found in: npm ERR! /home/ai/.npm/_logs/2019-01-24T02_48_16_688Z-debug.log

Here is the debug.log:
~$ cat /home/ai/.npm/_logs/2019-01-24T02_48_16_688Z-debug.log 0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', 1 verbose cli '/usr/bin/npm', 1 verbose cli 'install', 1 verbose cli '--save', 1 verbose cli '--save-prefix=~', 1 verbose cli '--production', 1 verbose cli 'node-red-node-base64@0.1.3' ] 2 info using npm@6.7.0 3 info using node@v10.15.0 4 verbose npm-session f74f2a2317fd538c 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 http fetch GET 200 395ms 8 silly pacote version manifest for node-red-node-base64@0.1.3 fetched in 407ms 9 timing stage:loadCurrentTree Completed in 437ms 10 silly install loadIdealTree 11 silly install cloneCurrentTreeToIdealTree 12 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms 13 silly install loadShrinkwrap 14 timing stage:loadIdealTree:loadShrinkwrap Completed in 4ms 15 silly install loadAllDepsIntoIdealTree 16 silly resolveWithNewModule node-red-node-base64@0.1.3 checking installable status 17 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 6ms 18 timing stage:loadIdealTree Completed in 12ms 19 silly currentTree node-red-project@0.0.1 20 silly idealTree node-red-project@0.0.1 20 silly idealTree └── node-red-node-base64@0.1.3 21 silly install generateActionsToTake 22 silly diff-trees filtering actions: includeDev false includeProd true includeOpt true 23 timing stage:generateActionsToTake Completed in 3ms 24 silly diffTrees action count 1 25 silly diffTrees add node-red-node-base64@0.1.3 26 silly decomposeActions action count 8 27 silly decomposeActions fetch node-red-node-base64@0.1.3 28 silly decomposeActions extract node-red-node-base64@0.1.3 29 silly decomposeActions preinstall node-red-node-base64@0.1.3 30 silly decomposeActions build node-red-node-base64@0.1.3 31 silly decomposeActions install node-red-node-base64@0.1.3 32 silly decomposeActions postinstall node-red-node-base64@0.1.3 33 silly decomposeActions finalize node-red-node-base64@0.1.3 34 silly decomposeActions refresh-package-json node-red-node-base64@0.1.3 35 silly install executeActions 36 silly doSerial global-install 8 37 verbose correctMkdir /home/ai/.npm/_locks correctMkdir not in flight; initializing 38 verbose lock using /home/ai/.npm/_locks/staging-bdd1e6c25794ac87.lock for /home/ai/.node-red/node_modules/.staging 39 silly doParallel extract 1 40 silly extract node-red-node-base64@0.1.3 41 silly tarball trying node-red-node-base64@0.1.3 by hash: sha512-0KlJDMur9tfnHwC7anlM9gYPjCMLsGVjRuvWSQssdGDibxIgpZDJ/0IuHIM3CAcEPaetlk4P0yj0XtH9Rgda0w== 42 silly tarball no local data for node-red-node-base64@0.1.3. Extracting by manifest. 43 timing npm Completed in 1145ms 44 error cb() never called! 45 error This is an error with npm itself. Please report this error at: 46 error <>

I installed this on a different machine about six weeks ago (Ubuntu-Mate 18.04) and it worked. No idea what has gone wrong here. I hope there is a quick solution.

(Atrian Wagner) #2

The cb() error you are seeing has a thread over here: [crash] npm ERR! cb() never called!

There’s a Canary build that should give you a more descriptive error to try to better pinpoint the actual issue.

(Wb666greene) #3

I’m not making any sense about that"canary" thing, but the thread you linked mentioned “too many open files”. I was running a large make and trying to setup node-red while waiting for it to complete.

Now that the compile completed ,I tried again and it installed.


(system) closed #4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.