# Error while updating to newer version of NR

**URL:** <https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141>\
**Category:** General\
**Created:** [13 December 2021 22:42 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141 "2021-12-13T22:42:52Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 08:01 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/22 "2021-12-14T08:01:52Z")

</div>

> [@Steve-Mcl](#):
>
> `sudo update-alternatives --config nodejs`

Sorry...

```auto
pi@TelePi:~/.node-red $ sudo update-alternatives --config nodejs 
update-alternatives: error: no alternatives for nodejs
pi@TelePi:~/.node-red $

```

Shrug.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [14 December 2021 08:55 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/23 "2021-12-14T08:55:35Z")

</div>

> [@Trying\_to\_learn](#):
>
> ```auto
> pi@TelePi:~/.node-red $ sudo update-alternatives --config nodejs 
> update-alternatives: error: no alternatives for nodejs
> pi@TelePi:~/.node-red $
> 
> ```
> 
> Shrug.

You do that on a system that actually HAS `nodejs` - to demonstrate what it "points to"

The point I was trying to make Andrew is, use `node` not `nodejs`

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 08:57 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/24 "2021-12-14T08:57:04Z")

</div>

Ok.

Thanks.

I need to get the CPU load down to something more like 30% (max) as now trying to get NR to load it like watching grass grow. (But more painful)

Looking at post 14 here, any ideas what is the problem?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2021 09:21 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/25 "2021-12-14T09:21:41Z")

</div>

It isn't clear what is hogging the processor. What does, with node red running,  
`sudo top`  
show?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 09:22 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/26 "2021-12-14T09:22:49Z")

</div>

htop doesn't really show much.

Would `sudo` make a difference?

 ![Screenshot from 2021-12-14 14-55-27](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/6/86fd0705754061b7a8f273e3b96e0a14ae4f3f4c.png)

Set to also show kernel tasks

Doing it as `sudo htop`....

 ![Screenshot from 2021-12-14 20-23-13](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/b/fb96f710e8ced8cf7394a6bfcd0bac2225a10966.png)

Running with `jessie` CPU load was down around 30%

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 09:25 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/27 "2021-12-14T09:25:00Z")

</div>

Oh, sorry. NR is not running in either case.

 ![Screenshot from 2021-12-14 20-29-05](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/f/bf10042186c0d9e4b17adc9f8fbff3364cfbbbe9.png)

Stopped.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2021 09:44 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/28 "2021-12-14T09:44:59Z")

</div>

I asked for top not htop, I understand top better. sudo may show extra processes I think.

So is the main problem that node red will not start? What happens if you just run  
node-red

If that doesn't show anything useful then set the log level to trace in settings.js and try again.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 09:48 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/29 "2021-12-14T09:48:26Z")

</div>

Sorry...

`sudo top`

 ![Screenshot from 2021-12-14 20-45-40](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/d/8dab9c1d06a2dff6e198ac4ec10ef0eb60566a30.png)

running `node-red` (from `~/.node-red`....

```auto
pi@TelePi:~/.node-red $ node-red
14 Dec 20:46:54 - [info] 

Welcome to Node-RED
===================

14 Dec 20:46:55 - [info] Node-RED version: v2.1.4
14 Dec 20:46:55 - [info] Node.js version: v14.18.1
14 Dec 20:46:55 - [info] Linux 5.10.63+ arm LE
14 Dec 20:47:08 - [info] Loading palette nodes
BAIL ON node-red-contrib-simple-message-queue/simple-queue
14 Dec 20:48:00 - [info] Dashboard version 2.26.2 started at /ui
14 Dec 20:48:04 - [warn] ------------------------------------------------------
14 Dec 20:48:04 - [warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red
14 Dec 20:48:04 - [warn] ------------------------------------------------------
14 Dec 20:48:04 - [info] Settings file : /home/pi/.node-red/settings.js
14 Dec 20:48:04 - [info] Context store : 'default' [module=memory]
14 Dec 20:48:04 - [info] User directory : /home/pi/.node-red
14 Dec 20:48:04 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Dec 20:48:04 - [info] Flows file : /home/pi/.node-red/flows.json
14 Dec 20:48:04 - [info] Creating new flow file
14 Dec 20:48:04 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

14 Dec 20:48:05 - [error] Uncaught Exception:
14 Dec 20:48:05 - [error] Error: listen EADDRINUSE: address already in use 0.0.0.0:1880
    at Server.setupListenHandle [as _listen2] (net.js:1331:16)
    at listenInCluster (net.js:1379:12)
    at doListen (net.js:1516:7)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
pi@TelePi:~/.node-red $ 

```

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [14 December 2021 09:51 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/30 "2021-12-14T09:51:28Z")

</div>

> [@Trying\_to\_learn](#):
>
> `listen EADDRINUSE: address already in use 0.0.0.0:1880`

Did you stop node-red service before running `node-red`?

`node-red-stop`

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 09:54 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/31 "2021-12-14T09:54:25Z")

</div>

Ok, sorry.

Try #2.

```auto
pi@TelePi:~/.node-red $ node-red-stop
Stop Node-RED
 
Use node-red-start to start Node-RED again
 
pi@TelePi:~/.node-red $ node-red
14 Dec 20:52:19 - [info] 

Welcome to Node-RED
===================

14 Dec 20:52:19 - [info] Node-RED version: v2.1.4
14 Dec 20:52:19 - [info] Node.js version: v14.18.1
14 Dec 20:52:19 - [info] Linux 5.10.63+ arm LE
14 Dec 20:52:32 - [info] Loading palette nodes
BAIL ON node-red-contrib-simple-message-queue/simple-queue
14 Dec 20:53:20 - [info] Dashboard version 2.26.2 started at /ui
14 Dec 20:53:23 - [warn] ------------------------------------------------------
14 Dec 20:53:23 - [warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red
14 Dec 20:53:23 - [warn] ------------------------------------------------------
14 Dec 20:53:23 - [info] Settings file : /home/pi/.node-red/settings.js
14 Dec 20:53:23 - [info] Context store : 'default' [module=memory]
14 Dec 20:53:23 - [info] User directory : /home/pi/.node-red
14 Dec 20:53:23 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Dec 20:53:23 - [info] Flows file : /home/pi/.node-red/flows.json
14 Dec 20:53:24 - [info] Creating new flow file
14 Dec 20:53:24 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

14 Dec 20:53:24 - [info] Server now running at http://127.0.0.1:1880/
14 Dec 20:53:24 - [info] Starting flows
14 Dec 20:53:25 - [info] Started flows

```

Looking possible.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2021 09:55 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/32 "2021-12-14T09:55:25Z")

</div>

So what exactly is the problem? Everything looks ok to me.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 09:56 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/33 "2021-12-14T09:56:19Z")

</div>

Now no flow/s.

(Luckily I have backups.)

How will I load them?

Import or copy all the files to `~/.node-red`?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 10:11 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/34 "2021-12-14T10:11:14Z")

</div>

$hit the `settings` file has changed.

I've for the security login (to the editor) working, but I am stuck where to define the `node-red/public` path.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2021 10:11 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/35 "2021-12-14T10:11:45Z")

</div>

Restore the .node-red folder from the original (except for node\_modules) and run npm install. If necessary set the flows file name in settings.js

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 10:14 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/36 "2021-12-14T10:14:19Z")

</div>

Thanks.

Do I need to stop NR before doing that?

I'll wait as I am stuck on the `settings.js` file and where `node-red/public/` is defined.  
I can see the line in the file, but it is more like:  
` //httpStaticAuth: {use.....`

Where as in the _old_ one it is:

` httpStatic: '/home/pi/.node-red/public/',`

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 10:31 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/37 "2021-12-14T10:31:36Z")

</div>

Oh, and got caught with the `mydevicename`.

Set that, but still the flows aren't being seen when NR starts.

Ok, found that _problem_.

Now I'm seeing this:

```auto
14 Dec 21:38:07 - [warn] Error loading credentials: SyntaxError: Unexpected token � in JSON at position 0
14 Dec 21:38:07 - [warn] Error loading flows: Error: Failed to decrypt credentials

```

That is a direct copy from the original backup files.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [14 December 2021 10:55 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/38 "2021-12-14T10:55:44Z")

</div>

Wouldn't it be better to backup node-RED, wipe the SD card, install a fresh, clean, shiny OS, then install node-RED + backup.

OS upgrades are never as good as a fresh install.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [14 December 2021 11:00 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/39 "2021-12-14T11:00:08Z")

</div>

Well.....

I've nearly done that now.

I've now been "bitten" by `paho-mqtt` not being installed.  
And something else about MQTT. When I run the script:

```auto
pi@TelePi:~/Pimoroni/blinkt $ python3 blinkt_ctl.py 
Traceback (most recent call last):
  File "blinkt_ctl.py", line 93, in <module>
    client = mqtt.Mosquitto()
AttributeError: module 'paho.mqtt.client' has no attribute 'Mosquitto'
pi@TelePi:~/Pimoroni/blinkt $ 

```

So it seems (somehow) mosquitto has been removed from the install list.

Be it I have to install it now or from a _brand spanking new_ version....

Seems I have a few other things to also get working. (Oh well. What's life without a challenge?) 😉 Just _how_ these things happen.

NR now seems to be working. `subflows`, etc. All good.  
Just now the things _behind the scenes_ (like `paho-mqtt` and mabe `mosquitto` in general is/are missing)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [17 December 2021 04:34 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/40 "2021-12-17T04:34:59Z")

</div>

Ok, things have .... progressed since then.

The RasPiZ(W) was pegging out its CPU load.

I tried different things and only made it worse.

It got to the stage where I couldn't connect to my WiFi.  
(I've since learnt where I went wrong on that - but that is now academic.)

Here's the short story:

_I broke something because I didn't start with a new flash of Buster_  
It was ongoing pegging out at 100% CPU for no reason I could see/find.

Suddenly I couldn't connect to my WiFi.  
Cutting my losses, I flashed a new SD card with buster - direct from the web.

Went through the fun stuff, and the bit extra.

Now, at this stage, I am not going to flash/update/install it on the Z(W).  
I have a 3B sitting here and I did it all on it. More memory and 3 cores.

Done. I was talking on the ethernet and knew I had to set up the WiFi.  
I'll skip the boring bits.

Now the _original_ SD card won't boot in the Z(W) or the 3b.  
Just get the colour screen - so it is seeing the card and SOMETHING is happening, but it just sits there.... doing nothing.

Got the new SD card. Took it out of the 3b, plugged it into the Z(W).

Booted. Can VNC into it, can SSH into it.  
Great.

Now, Couple of things to note here:  
1 - I installed the image from the net. Buster - full version.  
2 - node.red was **NOT** installed. Funny, I thought it came part and parcel.

As I was on my 3b and not this machine, all the "bookmarks" aren't available.  
So I loaded the browser. "How to install node-red on raspberry pi".  
Got a link. Looks like the one I sue.  
Copy it, paste it and it runs.  
As there is no existing node-red, it goes through fairly quickly.

All good.

I then get the old sd card and copy the **files** over.

```auto
flows_TelePi.json
flows_TelePi_cred.json
package.json
package-lock.json
settings.js

```

All good.

then ran `npm install`.

It went away and did it's thing.

After all this other things weren't installed and when done:

Now, NR is being difficult again.

(All from `~/.node-red` directory)  
ran `node-red-start`.  
Errors after errors.  
Stupid me, didn't get a screen shot.  
But they were new to me. very early on and not as before.

Ok... Some nodes didn't load: or something.

`npm install`  
`command not found`.  
Ok, not in those exact words. But how is it that I installed node-red and ran `npm install` before and now `npm` isn't a found command?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 December 2021 09:48 UTC](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141/41 "2021-12-17T09:48:04Z")

</div>

> [@Trying\_to\_learn](#):
>
> `npm install`  
> `command not found` .  
> Ok, not in those exact words

Show us the command and the exact words please. Exact words are essential when reporting a problem, otherwise we are just guessing.

[Previous page](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141.md?page=1)

[Next page](https://discourse.nodered.org/t/error-while-updating-to-newer-version-of-nr/55141.md?page=3)