# Error: "Node not available"
**URL:** https://discourse.nodered.org/t/error-node-not-available/55732
**Category:** Developing Nodes
**Created:** [26 December 2021 18:26 UTC](https://discourse.nodered.org/t/error-node-not-available/55732 "2021-12-26T18:26:49Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@bsailer2510](https://discourse.nodered.org/u/bsailer2510)
#### Post date: [26 December 2021 18:26 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/1 "2021-12-26T18:26:49Z")
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
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [26 December 2021 18:48 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/2 "2021-12-26T18:48:08Z")
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
```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node14
```
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [26 December 2021 19:27 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/3 "2021-12-26T19:27:44Z")
> [@bsailer2510](#):
>
> -nodeJS v10.24.0
> -node-red v2.1.4
Node-red v2+ requires node js V12 or greater.
Run the official raspberry pi update script with ` --node14` at the end of it.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [26 December 2021 21:31 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/4 "2021-12-26T21:31:08Z")
> [@bsailer2510](#):
>
> 've updated Node-Red, NVM
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.
---
### Author:  [@bsailer2510](https://discourse.nodered.org/u/bsailer2510)
#### Post date: [27 December 2021 05:20 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/5 "2021-12-27T05:20:06Z")
Hi Guys! Thank you for your tips. Using the install script with a version does end up in a
```auto
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).
---
### Author:  [@bsailer2510](https://discourse.nodered.org/u/bsailer2510)
#### Post date: [27 December 2021 07:43 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/6 "2021-12-27T07:43:31Z")
Hmmmh, i can start node-red with sudo but dont get my flows back....
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [27 December 2021 07:48 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/7 "2021-12-27T07:48:11Z")
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.
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [27 December 2021 07:49 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/8 "2021-12-27T07:49:12Z")
PS: don't run node-red as sudo unless you know what you are doing & have a specific reason to do so.
---
### Author:  [@bsailer2510](https://discourse.nodered.org/u/bsailer2510)
#### Post date: [27 December 2021 09:45 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/9 "2021-12-27T09:45:06Z")
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"...
```auto
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)
Abgebrochen
```
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [28 December 2021 09:56 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/10 "2021-12-28T09:56:46Z")
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.
---
### Author:  [@bsailer2510](https://discourse.nodered.org/u/bsailer2510)
#### Post date: [29 December 2021 09:15 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/11 "2021-12-29T09:15:23Z")
```auto
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.188.35:1880
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 http://flows.nodered.org
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'.
```
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 December 2021 09:50 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/12 "2021-12-29T09:50:29Z")
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.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [27 February 2022 09:51 UTC](https://discourse.nodered.org/t/error-node-not-available/55732/13 "2022-02-27T09:51:26Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.