Upgrade problem: Node-RED is not yet fully installed

General
62

Maybe rename it instead then?

(And add warning in docs that the script is only for people who just want to run NodeRED and not for experts?)

63

Errrr no thanks. Maybe if you can identify which dir inside there then yes

64

I've just tried to upgrade Node-RED on a RPi-B (old version) that's been working for months.
I get the following message, which then sends me round in a loop of actions.
How can I salvage the situation??

All done.
You can now start Node-RED with the command node-red-start
or using the icon under Menu / Programming / Node-RED
Then point your browser to localhost:1880 or http://{your_pi_ip-address}:1880

Started Fri 21 Sep 16:09:20 BST 2018 - Finished Fri 21 Sep 16:13:34 BST 2018

pi@raspberrypi:~/.node-red $ node-red-start

Node-RED is not yet fully installed

Fetching Node-RED update.

65

Break out of your loop and as long as Node-RED is your only node.js application on your pi try

sudo rm -rf /usr/lib/node_modules
sudo rm -rf /usr/bin/node

And re-run the update script

66

Thanks - that seems to have worked.
Just got two more RPi(s) to update this evening.

67

Wanted to say Thanks plus say what worked for me.

I went round the loop several times and had the same, not installed error.

I tried this suggestion from "cymplecy"
sudo rm -rf /usr/lib/node_modules
sudo rm -rf /usr/bin/node

Did not seem to make a difference but it is what I did and the end result so maybe?

Then did this from "dceejay Leader"

npm cache clear
sudo npm cache clear
sudo apt-get purge nodejs npm

During the above it suggested I perform an "apt-get auto remove" so I did.

It worked, this time the update / install script took longer, it started and all my nodes appeared to be intact.

"Manage Pallets" was back which is where I started several hours earlier.
SO this is what I did, it seems to be OK; Thanks.

2 Likes
68

Hallo,
I had the same problem after trying to update node red and saw it dosen't load the actually core.
Today I found an older book there was it right explaind and agess what happened , it runs.

69

I'm having this issue pop up on about every 3rd install I have running (all Rpi3+)

This latest one I'm not able to resolve after running through everything in this thread.

Right now, when I just attempt to sudo npm install -g --unsafe-perm node-red I get this:

npm ERR! Unexpected end of JSON input while parsing near '...Oup68CH2Rp+mpCv\nHt+t'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-06-24T17_08_30_573Z-debug.log

So I'm going back through install logs to find this error popping up during the install script. Any idea where this originates?

SOLVED: I was able to get things rolling by switch to user ROOT and running npm cache clean --force. Now working through a problem with node_modules/serialport not self registering...

70

The npm cache is messed up, run
npm cache clean --force
And
npm -g cache clean --force

1 Like
71

Thank you. I just wanted to note that I keep having issues with clearing the npm cache. This doesn't always seem to be reliable. So, I tried npm cache verify instead and this solved the problem.

72

If you keep having issues with the cache there is something very odd going on.
What do
npm -v
and
node -v
show?

73

Sorry, I haven't been getting notifications for my replies.

$: npm -v 
6.14.5
$; node - v
12.18.2
74

Are you still having problems?

75

No, npm cache verify fixed it ultimately.

1 Like