# Node-red-contrib-inspector fail with 32 bits os? **URL:** \ **Category:** General\ **Tags:** function-node\ **Created:** [1 October 2022 16:51 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461 "2022-10-01T16:51:56Z")\ **Posts on this page:** 20\ **Page:** 1

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\ **Post date:** [1 October 2022 16:51 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/1 "2022-10-01T16:51:56Z")

Lately I have CPU performance troubles on my RP3B+. At the beginning of this summer my project was more then 95% finished, and over the summer until now I only made minor changes, some tweaking etc. only more or less of the same functions I already made. Since a week or so the CPU usage is ramping up over time. Before it was always between 5 and 10%. Now, after restart/reboot, it starts just over 10 and slowly creeps to more then 25% during 24 hours. As long as CPU usage is lower then 10%, Node-Red is performing excellent. Above that performance is getting worse. With (h)top I can see that node-red is causing more CPU usage. As I didn't made major changes/developments on node-red, I tried searching for the problem, but didn't find it. So I thought let's try the node-red-contrib-inspector, maybe I can find the source of the problem.with that tool. But now I encounter another problem. It seems I have a 32 bit OS, I always thought I have 64 bits OS. ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/6/3670907afca1a786bf90117221e02e2dd5276173.png) This is an overview of the software running on my RPI. ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/1/f1ad39ee4f6ee141ed1c7c9df3fcf4eaeb38c85c.png) Is there somebody that can shine a light on this? ---

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\ **Post date:** [1 October 2022 16:59 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/2 "2022-10-01T16:59:43Z")

Possibly not helping that you have weird versions of node.js and npm installed. Here's what I have: Node: v16.17.1 npm: 8.15.0 Generally, you should avoid using odd-numbered versions of node.js as they are considered development versions by many. I think that what you've listed as npm is actually node-red? Your version of InfluxDB could do with upgrading to v1.8 as well. I can't read any of the details on that embedded image. ---

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\ **Post date:** [1 October 2022 17:48 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/3 "2022-10-01T17:48:39Z")

@TotallyInformation Thanks for your reaction. I have replaced the embedded image, It should now be possible to enlarge the image. As about the versions I don't know. At some point in time I installed these with a bash file that was recommended. > bash \<(curl -sL [https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)) As I said before I have not experienced any problems over the summer, until about a week ago. I am not sure if I can update to higher version without getting new problems. The versions of NPM and node.js I get with following commands: ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/1/61678fc102ca932da2d6e5bec7279a2453120ac5.png) ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/d/1d8c94103db2dddbdca20dc1353dd09994658010.png) ---

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\ **Post date:** [1 October 2022 18:36 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/4 "2022-10-01T18:36:06Z")

If you were able to run the bash command, you can simply run it again but passing `--node 16` to get the current LTS version of node.js and the corresponding npm version. You should also do: ```auto cd ~/.node-red npm rebuild ``` after changing major node versions. Makes sure that any C++ libraries are rebuilt correctly. Then just restart node-red and reload the editor. To get the actual node and npm versions, this command will do it: `node --version && npm --version`. If you are running v2.2.0 of node-red, probably best to get the latest version. The script will do that as well as deal with node.js and npm. Can't say that this will fix your issue but it may well do so and getting everything current is generally the best starting point anyway. Especially as most people in the forum in a position to help you will be on current versions of everything as well. ---

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\ **Post date:** [1 October 2022 18:43 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/5 "2022-10-01T18:43:22Z")

> [@TotallyInformation](#): > > after changing major node versions. Makes sure that any C++ libraries are rebuilt correctly. How do I do this? I didn't make any C++ applications. I probably should follow your recommendations, luckily I have a second RPI available so I can test these updates. I will try tomorrow. ---

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\ **Post date:** [1 October 2022 18:49 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/6 "2022-10-01T18:49:58Z")

> [@henkkas](#): > > How do I do this? I didn't make any C++ applications. As I said, this the command `npm rebuild` in your userDir folder (typically `~/.node-red`). While you didn't make a C++ library, if you have something like the serial or SQLite nodes, they DO have C++ libraries. It is common to get problems after a major version upgrade of node.js if you don't do this. ---

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\ **Post date:** [2 October 2022 12:43 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/7 "2022-10-02T12:43:50Z")

@TotallyInformation, indeed when I give the command `npm --version` I get result 7.7.6. I checked the commands again and found the error. I corrected the result and my software version looks like this, ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/1/31bd3d884bc78276e61919252be422dce2314b44.png) Leaves me the question in my first comment. Why does my RPI 3B+ reports a 32 bits OS when [Node-red-contrib-inspector](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461) is used with Chrome inspect? I thought I had 64-bits OS.also to @BartButenaers ---

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\ **Post date:** [2 October 2022 13:27 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/8 "2022-10-02T13:27:49Z")

About testing upgrade node.js 15.x to 16.x, that didn't go well. Here are the steps I took. 1. Command: `curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash` 2. `sudo apt-get install -y node.js` 3. `cd ~/.node-red` 4. `npm rebuild` At point 4 I got a lot of errors. See this error log `````auto > 0 verbose cli /usr/bin/node /usr/bin/npm > 1 info using npm@8.15.0 > 2 info using node@v16.17.1 > 3 timing npm:load:whichnode Completed in 1ms > 4 timing config:load:defaults Completed in 8ms > 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 3ms > 6 timing config:load:builtin Completed in 4ms > 7 timing config:load:cli Completed in 7ms > 8 timing config:load:env Completed in 2ms > 9 timing config:load:file:/home/pi/.node-red/.npmrc Completed in 1ms > 10 timing config:load:project Completed in 14ms > 11 timing config:load:file:/home/pi/.npmrc Completed in 3ms > 12 timing config:load:user Completed in 4ms > 13 timing config:load:file:/usr/etc/npmrc Completed in 1ms > 14 timing config:load:global Completed in 1ms > 15 timing config:load:validate Completed in 2ms > 16 timing config:load:credentials Completed in 4ms > 17 timing config:load:setEnvs Completed in 4ms > 18 timing config:load Completed in 54ms > 19 timing npm:load:configload Completed in 55ms > 20 timing npm:load:mkdirpcache Completed in 4ms > 21 timing npm:load:mkdirplogs Completed in 1ms > 22 verbose title npm rebuild > 23 verbose argv "rebuild" > 24 timing npm:load:setTitle Completed in 4ms > 25 timing config:load:flatten Completed in 14ms > 26 timing npm:load:display Completed in 47ms > 27 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs > 28 verbose logfile /home/pi/.npm/_logs/2022-10-02T13_10_07_825Z-debug-0.log > 29 timing npm:load:logFile Completed in 74ms > 30 timing npm:load:timers Completed in 1ms > 31 timing npm:load:configScope Completed in 0ms > 32 timing npm:load Completed in 192ms > 33 timing arborist:ctor Completed in 3ms > 34 silly logfile done cleaning log files > 35 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules/bufferutil > 36 timing build:queue Completed in 58ms > 37 timing build:link:node_modules/acorn Completed in 20ms > 38 timing build:link:node_modules/bwip-js Completed in 17ms > 39 timing build:link:node_modules/is-base64 Completed in 17ms > 40 timing build:link:node_modules/mime Completed in 16ms > 41 timing build:link:node_modules/jsmodbus Completed in 16ms > 42 timing build:link:node_modules/mkdirp Completed in 16ms > 43 timing build:link:node_modules/mustache Completed in 15ms > 44 timing build:link:node_modules/node-gyp-build Completed in 16ms > 45 timing build:link:node_modules/pixelmatch Completed in 14ms > 46 timing build:link:node_modules/prebuild-install Completed in 13ms > 47 timing build:link:node_modules/rc Completed in 13ms > 48 timing build:link:node_modules/semver Completed in 12ms > 49 timing build:link:node_modules/systeminformation Completed in 11ms > 50 timing build:link:node_modules/sshpk Completed in 13ms > 51 timing build:link:node_modules/vm2 Completed in 11ms > 52 timing build:link:node_modules/which Completed in 11ms > 53 timing build:link:node_modules/node-red-contrib-ui-multistate-switch/node_modules/mustache Completed in 10ms > 54 timing build:link:node_modules/request/node_modules/uuid Completed in 10ms > 55 timing build:link Completed in 24ms > 56 info run @serialport/bindings@9.2.8 install node_modules/@serialport/bindings prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild > 57 info run bufferutil@1.2.1 install node_modules/bufferutil node-gyp rebuild > 58 info run gc-stats@1.0.0 install node_modules/gc-stats node-gyp rebuild > 59 info run bufferutil@4.0.6 install node_modules/engine.io/node_modules/bufferutil node-gyp-build > 60 info run bufferutil@4.0.6 install { code: 0, signal: null } > 61 timing build:run:install:node_modules/engine.io/node_modules/bufferutil Completed in 1352ms > 62 info run utf-8-validate@5.0.9 install node_modules/engine.io/node_modules/utf-8-validate node-gyp-build > 63 info run utf-8-validate@5.0.9 install { code: 0, signal: null } > 64 timing build:run:install:node_modules/engine.io/node_modules/utf-8-validate Completed in 1239ms > 65 info run bufferutil@1.2.1 install { code: 1, signal: null } > 66 timing command:rebuild Completed in 14228ms > 67 verbose stack Error: command failed > 67 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27) > 67 verbose stack at ChildProcess.emit (node:events:513:28) > 67 verbose stack at maybeClose (node:internal/child_process:1093:16) > 67 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) > 68 verbose pkgid bufferutil@1.2.1 > 69 verbose cwd /home/pi/.node-red > 70 verbose Linux 5.10.63-v7+ > 71 verbose node v16.17.1 > 72 verbose npm v8.15.0 > 73 error code 1 > 74 error path /home/pi/.node-red/node_modules/bufferutil > 75 error command failed > 76 error command sh /tmp/install-2a82c177.sh > 77 error make: Map '/home/pi/.node-red/node_modules/bufferutil/build' wordt binnengegaan > 77 error CXX(target) Release/obj.target/bufferutil/src/bufferutil.o > 77 error make: Map '/home/pi/.node-red/node_modules/bufferutil/build' wordt verlaten > 78 error gyp info it worked if it ends with ok > 78 error gyp info using node-gyp@9.0.0 > 78 error gyp info using node@16.17.1 | linux | arm > 78 error gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3" > 78 error gyp info spawn /usr/bin/python3 > 78 error gyp info spawn args [ > 78 error gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py', > 78 error gyp info spawn args 'binding.gyp', > 78 error gyp info spawn args '-f', > 78 error gyp info spawn args 'make', > 78 error gyp info spawn args '-I', > 78 error gyp info spawn args '/home/pi/.node-red/node_modules/bufferutil/build/config.gypi', > 78 error gyp info spawn args '-I', > 78 error gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi', > 78 error gyp info spawn args '-I', > 78 error gyp info spawn args '/home/pi/.cache/node-gyp/16.17.1/include/node/common.gypi', > 78 error gyp info spawn args '-Dlibrary=shared_library', > 78 error gyp info spawn args '-Dvisibility=default', > 78 error gyp info spawn args '-Dnode_root_dir=/home/pi/.cache/node-gyp/16.17.1', > 78 error gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp', > 78 error gyp info spawn args '-Dnode_lib_file=/home/pi/.cache/node-gyp/16.17.1/<(target_arch)/node.lib', > 78 error gyp info spawn args '-Dmodule_root_dir=/home/pi/.node-red/node_modules/bufferutil', > 78 error gyp info spawn args '-Dnode_engine=v8', > 78 error gyp info spawn args '--depth=.', > 78 error gyp info spawn args '--no-parallel', > 78 error gyp info spawn args '--generator-output', > 78 error gyp info spawn args 'build', > 78 error gyp info spawn args '-Goutput_dir=.' > 78 error gyp info spawn args ] > 78 error gyp info spawn make > 78 error gyp info spawn args ['BUILDTYPE=Release', '-C', 'build'] > 78 error ../src/bufferutil.cc:25:30: error: ‘v8::Handle’ has not been declared > 78 error static void Initialize(v8::Handle target) > 78 error ^ ~~~~~ > 78 error ../src/bufferutil.cc:25:36: error: expected ‘,’ or ‘...’ before ‘<’ token > 78 error static void Initialize(v8::Handle target) > 78 error ^ > 78 error ../src/bufferutil.cc: In static member function ‘static void BufferUtil::Initialize(int)’: > 78 error ../src/bufferutil.cc:33:14: error: ‘target’ was not declared in this scope > 78 error Nan::Set(target, Nan::New("BufferUtil").ToLocalChecked(), t->GetFunction()); > 78 error ^ ~~~~~ > 78 error ../src/bufferutil.cc:33:14: note: suggested alternative: ‘Merge’ > 78 error Nan::Set(target, Nan::New("BufferUtil").ToLocalChecked(), t->GetFunction()); > 78 error ^ ~~~~~ > 78 error Merge > 78 error ../src/bufferutil.cc:33:86: error: no matching function for call to ‘v8::FunctionTemplate::GetFunction()’ > 78 error Nan::Set(target, Nan::New("BufferUtil").ToLocalChecked(), t->GetFunction()); > 78 error ^ > 78 error In file included from ../src/bufferutil.cc:7: > 78 error /home/pi/.cache/node-gyp/16.17.1/include/node/v8.h:6802:46: note: candidate: ‘v8::MaybeLocal v8::FunctionTemplate::GetFunction(v8::Local)’ > 78 error V8_WARN_UNUSED_RESULT MaybeLocal GetFunction( > 78 error ^ ~~~~~~~~~~ > 78 error /home/pi/.cache/node-gyp/16.17.1/include/node/v8.h:6802:46: note: candidate expects 1 argument, 0 provided > 78 error ../src/bufferutil.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Merge(Nan::NAN_METHOD_ARGS_TYPE)’: > 78 error ../src/bufferutil.cc:49:49: error: no matching function for call to ‘v8::Value::ToObject()’ > 78 error Local