Just upgraded NR on my RPI and guess what happened

General
1

In sort of light of my recent UBUNTU install/update I decided to update my MAIN RPI machine to get the latest features.

Though 18.04 was doing fine, I feel I need to keep up with everyone else.

Did the "magic command" and.......
It died.
This is the command:

bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

done from the home directory.
No sudo, no extra stuff.

This takes me back to what I saw when I was trying to get the Ubuntu version installed.
(But I'll let that go.)

This is a RPI.
It was running 18.04.

I put the command in and....

I am 90% sure when I have done that in the past it was from the .node-red directory.

This is the error I see:

pi@TimePi:~ $ sudo systemctl status nodered
â—Ź nodered.service - Node-RED graphical event wiring tool
   Loaded: loaded (/lib/systemd/system/nodered.service; enabled)
   Active: failed (Result: start-limit) since Fri 2018-09-21 15:01:18 AEST; 5min ago
     Docs: http://nodered.org/docs/hardware/raspberrypi.html
  Process: 522 ExecStart=/usr/bin/env node-red-pi $NODE_OPTIONS $NODE_RED_OPTIONS (code=exited, status=127)
 Main PID: 522 (code=exited, status=127)

Sep 21 15:01:18 TimePi systemd[1]: nodered.service: main process exited, code=exited, status=127/n/a
Sep 21 15:01:18 TimePi systemd[1]: Unit nodered.service entered failed state.
Sep 21 15:01:18 TimePi systemd[1]: nodered.service holdoff time over, scheduling restart.
Sep 21 15:01:18 TimePi systemd[1]: Stopping Node-RED graphical event wiring tool...
Sep 21 15:01:18 TimePi systemd[1]: Starting Node-RED graphical event wiring tool...
Sep 21 15:01:18 TimePi systemd[1]: nodered.service start request repeated too quickly, refusing to start.
Sep 21 15:01:18 TimePi systemd[1]: Failed to start Node-RED graphical event wiring tool.
Sep 21 15:01:18 TimePi systemd[1]: Unit nodered.service entered failed state.
pi@TimePi:~ $
2

To maybe help, here is today's extract from the log.
Attached.

NR_Error_log.txt (174.1 KB)

3

If I try to start node-red with nodered it loops back to the install and goes through it all again.

After 20-30 minutes it says "Done".. Do you want to start node-red now?

I press Y and it again loops back to the upgrade/install screen and...... round and round we go.
I stopped it on the second time.

4

And just a bit more stuff I have gathered:

pi@TimePi:~/.node-red $ node -v
v8.12.0
pi@TimePi:~/.node-red $ npm -v
6.4.1
pi@TimePi:~/.node-red $

and (though pre the above):

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

Node-RED is not yet fully installed

Fetching Node-RED update.

 
This script will remove versions of Node.js prior to version 6.x, and Node-RED and
if necessary replace them with Node.js 8.x LTS (carbon) and the latest Node-RED from Npm.
 
It also moves any Node-RED nodes that are globally installed into your user
~/.node-red/node_modules directory, and adds them to your package.json, so that
you can manage them with the palette manager.
 
It also tries to run 'npm rebuild' to refresh any extra nodes you have installed
that may have a native binary component. While this normally works ok, you need
to check that it succeeds for your combination of installed nodes.
 
To do all this it runs commands as root - please satisfy yourself that this will
not damage your Pi, or otherwise compromise your configuration.
If in doubt please backup your SD card first.
 
Are you really sure you want to do this ? [y/N] ? n
 
pi@TimePi:~/.node-red $

It just keeps on going if I press Y.

5

If your only node.js application that you use on this pi is Node-RED, try

Simon

6

Thank you very much.

Did the commands, and all is working now.

1 Like