This is another machine - than the other thread I have.
Another machine is/was/still is giving me grief.
It isn't coming online when it boots.
So I try to look at the NR edit screen. Won't load.
SSH into it and it showed as dead.
I decided as it was/is being problematic, I should run the update command and see if it fixes the problem.
Alas, no.
This is what happens:
Running Node-RED update for user pi at /home/pi on raspbian\n
This can take 20-30 minutes on the slower Pi versions - please wait.
Stop Node-RED ✔
Remove old version of Node-RED ✔
Remove old version of Node.js ✔
Install Node.js LTS ✘ Failed to install Node.js - Exit
Clean npm cache
Install Node-RED core
Move global nodes to local
Install extra Pi nodes
Npm rebuild existing nodes
Add shortcut commands
Update systemd script
Any errors will be logged to /var/log/nodered-install.log
pi@PIFACE:~/.node-red $
Not my week.
The command I used: bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)
W: Failed to fetch https://dl.bintray.com/resin-io/debian/dists/stable/etcher/binary-armhf/Packages HttpError404
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
pi@PIFACE:~/.node-red $ sudo apt install -y nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version.
The following packages were automatically installed and are no longer required:
ax25-node gyp libax25 libc-ares-dev libjs-node-uuid libv8-3.14-dev openbsd-inetd pix-icons
pix-plym-splash pixel-wallpaper
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
pi@PIFACE:~/.node-red $ node -v
-bash: node: command not found
pi@PIFACE:~/.node-red $ npm -v
-bash: npm: command not found
pi@PIFACE:~/.node-red $
I'm guessing that isn't good.
Just in case, attached is the whole thing Update_try.txt (7.7 KB)
you do seem to have rather a lot of extra library sources... and yet something is stopping the basic node install script from adding itself to the list and installing node.js correctly.
Basically you need a file /etc/apt/sources.list.d/nodesource.list to contain
deb https://deb.nodesource.com/node_10.x jessie main
deb-src https://deb.nodesource.com/node_10.x jessie main
then run sudo apt-update && sudo apt install nodejs
then check to see what got installed node -v && npm -v
I will admit here that I think I know why that file is missing.
aaaargh - you did not want to apt install npm... now that is broken (1.4 is way too old) - please sudo apt-get purge npm nodejs to remove it (and any nodejs), then sudo rm /etc/apt/sources.list.d/nodesource.list to remove that old one, then re-run the upgrade/install bash command (without sudo)... and see which version we get... - it may well re-install 6 - in which case then yes a whole OS upgrade is the way forward.
I know that is from another thread, but as this machine is as infected as the other/s..... I probably did it on this one as well.
Sorry if that caused unneeded stress.
pi@PIFACE:/etc/apt/sources.list.d $ sudo apt install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ax25-node gyp libax25 libc-ares-dev libc-ares2 libjs-node-uuid libv8-3.14-dev libv8-3.14.5 openbsd-inetd pix-icons pix-plym-splash
pixel-wallpaper
Use 'apt-get autoremove' to remove them.
The following packages will be upgraded:
nodejs
1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Need to get 14.2 MB of archives.
After this operation, 70.0 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_10.x/ jessie/main nodejs armhf 10.16.3-1nodesource1 [14.2 MB]
Fetched 14.2 MB in 6s (2,259 kB/s)
(Reading database ... 186280 files and directories currently installed.)
Preparing to unpack .../nodejs_10.16.3-1nodesource1_armhf.deb ...
Unpacking nodejs (10.16.3-1nodesource1) over (0.10.29~dfsg-2) ...
Processing triggers for man-db (2.7.5-1~bpo8+1) ...
Setting up nodejs (10.16.3-1nodesource1) ...
pi@PIFACE:/etc/apt/sources.list.d $ node -v
v10.16.3
pi@PIFACE:/etc/apt/sources.list.d $ npm -v
6.9.0
pi@PIFACE:/etc/apt/sources.list.d $
Start NR?
Maybe not.
pi@PIFACE:~ $ cd .node-red
pi@PIFACE:~/.node-red $ node-red-start
-bash: node-red-start: command not found
I'm not going to guess which command/script I need to do to get that part working.
Running Node-RED update for user pi at /home/pi on raspbian\n
This can take 20-30 minutes on the slower Pi versions - please wait.
Stop Node-RED ✔
Remove old version of Node-RED ✔
Remove old version of Node.js -
Leave existing Node.js - Node v10.16.3 Npm 6.9.0
Clean npm cache -
Install Node-RED core ✔ 0.20.7
Move global nodes to local -
Install extra Pi nodes -
Npm rebuild existing nodes -
Add shortcut commands ✔
Update systemd script ✔
Any errors will be logged to /var/log/nodered-install.log
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 Tuesday 3 September 19:25:24 AEST 2019 - Finished Tuesday 3 September 19:30:37 AEST 2019
pi@PIFACE:~ $ node -v
v10.16.3
pi@PIFACE:~ $ npm -v
6.9.0
pi@PIFACE:~ $
It is working, but WOW all the dashboard things are unassigned.
The drop down list is completely different and I can't find some of the names I can see in the dashboard list on the right of the screen.
I may need to get a complete list of what I did to get it working, so I can use it to get the others working.
The old way still works - so you can just use that if necessary. The new way should be fairly intuitive - it works on one tab at a time only - but you can then just drag widgets around within and between their groups to arrange the order and size .
Say I have a "window" called TELEMETRY. On that I have a few "groups" like: 1, 2, 3, 4.
When I double click a dashboard node I get the list but all I see is TELEMETRY.
I don't get to see the 1, 2, 3 or 4.
I kind of "cheated" with the RPI and just selected the name of the "window" in which those nodes live.
Looking to the right of the screen as I move the mouse over the lists of nodes, I see the ones on/in the main edit screen become highlighted pretty much in the right way.
All that being good, I press DEPLOY and go to the GUI page.
BLANK.
I see the GUI nodes have changed their look. Not a big problem, but it sort of threw me.
All the flows on the RPI are "happy" as in there are no errors/missing nodes/etc.
Thanks in advance.
I was going to show pictures of this but when I press the to get a screen shot, I lose the menu I see.
