Error: "Node not available"

Since i've updated Node-Red, NVM and NodeJS today i'm getting an Errormessage on all my existing Flows: "Node not available". Anyone any idea?

-Raspberry Pi 4
-nodeJS v10.24.0
-node-red v2.1.4

I have seen a few posts recently about problems around Node-red and NodeJS 10.
It might be worth making a backup of your .node-red dirctory then run the installation script specifying node 14 or node 16

bash <(curl -sL --node14

Node-red v2+ requires node js V12 or greater.

Run the official raspberry pi update script with --node14 at the end of it.

1 Like

If you really mean nvm then I don't think the script will work. nvm is not recommended unless you have a reason to use it. If you must use it then you will have to install nodejs 14 yourself.

Hi Guys! Thank you for your tips. Using the install script with a version does end up in a

Willkommen bei Node-RED!
27 Dec 06:16:17 - [info] Node-RED Version: v2.1.4
27 Dec 06:16:17 - [info] Node.js  Version: v16.13.1
27 Dec 06:16:17 - [info] Linux 5.10.63-v7l+ arm LE
27 Dec 06:16:19 - [info] Paletten-Nodes werden geladen
malloc(): invalid size (unsorted)
nodered.service: Main process exited, code=killed, status=6/ABRT
nodered.service: Failed with result 'signal'.

Installing without a version ends up that i have the same error as initial mentioned (Node not available).

Hmmmh, i can start node-red with sudo but dont get my flows back....

Because sudo has a different home & is own set of flows.

However this does suggest a problem with one of nodes or your flows.

Start node-red (no sudo) in safe mode...

node-red --safe

You can't fix up your flows/nodes then when you press deploy they start running.

PS: don't run node-red as sudo unless you know what you are doing & have a specific reason to do so.

Thank you. I fixed the broken flows before installation allready. When i try to start it in safe mode as user "Pi" then it stops with "invalide size"...

pi@raspberrypi:~ $ node-red --safe
27 Dec 10:43:18 - [info]

Willkommen bei Node-RED!

27 Dec 10:43:18 - [info] Node-RED Version: v2.1.4
27 Dec 10:43:18 - [info] Node.js  Version: v16.13.1
27 Dec 10:43:18 - [info] Linux 5.10.63-v7l+ arm LE
27 Dec 10:43:19 - [info] Paletten-Nodes werden geladen
malloc(): invalid size (unsorted)

That sounds like a problem with a particular node type. Try setting the log level to trace in settings.js (in your .node-red folder) and restart node red. Post the console output here.

Start Node-RED

Once Node-RED has started, point a browser at
On Pi Node-RED works better with the Firefox or Chrome browser

Use   node-red-stop                          to stop Node-RED
Use   node-red-start                         to start Node-RED again
Use   node-red-log                           to view the recent log output
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to

Starting as a systemd service.
29 Dec 09:37:53 - [info]
Willkommen bei Node-RED!
29 Dec 09:37:53 - [info] Node-RED Version: v2.1.4
29 Dec 09:37:53 - [info] Node.js  Version: v16.13.1
29 Dec 09:37:53 - [info] Linux 5.10.63-v7l+ arm LE
29 Dec 09:37:55 - [info] Paletten-Nodes werden geladen
29 Dec 09:37:56 - [debug] Module: google-translate-tts 0.4.0-dev /home/pi/.node-red/node_modules/google-translate-tts
29 Dec 09:37:56 - [debug] Module: node-red-contrib-bigcsv 1.2.0 /home/pi/.node-red/node_modules/node-red-contrib-bigcsv
29 Dec 09:37:56 - [debug] Module: node-red-contrib-bigtimer 2.7.6 /home/pi/.node-red/node_modules/node-red-contrib-bigtimer
29 Dec 09:37:56 - [debug] Module: node-red-contrib-ble-scan 1.0.0 /home/pi/.node-red/node_modules/node-red-contrib-ble-scan
29 Dec 09:37:56 - [debug] Module: node-red-contrib-buffer-parser 3.1.7 /home/pi/.node-red/node_modules/node-red-contrib-buffer-parser
29 Dec 09:37:56 - [debug] Module: node-red-contrib-cast 0.2.17 /home/pi/.node-red/node_modules/node-red-contrib-cast
29 Dec 09:37:56 - [debug] Module: node-red-contrib-eufy-security 0.0.2 /home/pi/.node-red/node_modules/node-red-contrib-eufy-security
29 Dec 09:37:56 - [debug] Module: node-red-contrib-fs-ops 1.6.0 /home/pi/.node-red/node_modules/node-red-contrib-fs-ops
29 Dec 09:37:56 - [debug] Module: node-red-contrib-generic-ble 4.0.3 /home/pi/.node-red/node_modules/node-red-contrib-generic-ble
29 Dec 09:37:56 - [debug] Module: node-red-contrib-google-action 1.2.1 /home/pi/.node-red/node_modules/node-red-contrib-google-action
29 Dec 09:37:56 - [debug] Module: node-red-contrib-huemagic 3.0.0 /home/pi/.node-red/node_modules/node-red-contrib-huemagic
29 Dec 09:37:56 - [debug] Module: node-red-contrib-media-utils 0.0.4 /home/pi/.node-red/node_modules/node-red-contrib-media-utils
29 Dec 09:37:56 - [debug] Module: node-red-contrib-nora 0.0.34 /home/pi/.node-red/node_modules/node-red-contrib-nora
29 Dec 09:37:56 - [debug] Module: node-red-contrib-nuki 1.1.0 /home/pi/.node-red/node_modules/node-red-contrib-nuki
29 Dec 09:37:56 - [debug] Module: node-red-contrib-onvif 1.0.3 /home/pi/.node-red/node_modules/node-red-contrib-onvif
29 Dec 09:37:56 - [debug] Module: node-red-contrib-play-audio 2.5.0 /home/pi/.node-red/node_modules/node-red-contrib-play-audio
29 Dec 09:37:56 - [debug] Module: node-red-contrib-powershell 0.0.3 /home/pi/.node-red/node_modules/node-red-contrib-powershell
29 Dec 09:37:56 - [debug] Module: node-red-contrib-python-function 0.0.5 /home/pi/.node-red/node_modules/node-red-contrib-python-function
29 Dec 09:37:56 - [debug] Module: node-red-contrib-python3-function 0.0.4 /home/pi/.node-red/node_modules/node-red-contrib-python3-function
29 Dec 09:37:56 - [debug] Module: node-red-contrib-shelly 4.1.0 /home/pi/.node-red/node_modules/node-red-contrib-shelly
29 Dec 09:37:56 - [debug] Module: node-red-contrib-telegrambot 11.0.0 /home/pi/.node-red/node_modules/node-red-contrib-telegrambot
29 Dec 09:37:56 - [debug] Module: node-red-contrib-tfjs-coco-ssd 1.0.2 /home/pi/.node-red/node_modules/node-red-contrib-tfjs-coco-ssd
29 Dec 09:37:56 - [debug] Module: node-red-contrib-vestel-tv 0.0.1 /home/pi/.node-red/node_modules/node-red-contrib-vestel-tv
29 Dec 09:37:56 - [debug] Module: node-red-dashboard 3.1.3 /home/pi/.node-red/node_modules/node-red-dashboard
29 Dec 09:37:56 - [debug] Module: node-red-node-openweathermap 0.5.0 /home/pi/.node-red/node_modules/node-red-node-openweathermap
29 Dec 09:37:56 - [debug] Module: node-red-node-pi-gpio 2.0.1 /home/pi/.node-red/node_modules/node-red-node-pi-gpio
29 Dec 09:37:56 - [debug] Module: node-red-node-ping 0.3.1 /home/pi/.node-red/node_modules/node-red-node-ping
29 Dec 09:37:56 - [debug] Module: node-red-node-random 0.4.0 /home/pi/.node-red/node_modules/node-red-node-random
29 Dec 09:37:56 - [debug] Module: node-red-node-serialport 0.15.0 /home/pi/.node-red/node_modules/node-red-node-serialport
29 Dec 09:37:56 - [debug] Module: node-red-node-smooth 0.1.2 /home/pi/.node-red/node_modules/node-red-node-smooth
29 Dec 09:37:56 - [debug] Module: nodered-contrib-signal-client 2.4.2 /home/pi/.node-red/node_modules/nodered-contrib-signal-client
malloc(): invalid size (unsorted)
nodered.service: Main process exited, code=killed, status=6/ABRT
nodered.service: Failed with result 'signal'.

Looks as if it may be a further problem with the signal node. Are you using that node still? If not then go into your .node-red folder and run
npm remove node-red-contrib-signal-client
then restart node-red. If you are still using it then do
npm remove node-red-contrib-signal-client
npm install node-red-contrib-signal-client
and post the result here.

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