Unable to Install Node_RED Missing node.js, and NPM stops installation Buster 10

General
1

Hello,
I am installing Node-RED on my third Rpi 3 and ran into the following. I am pasting the CLI output as well and a portion of the error logs. The error log indicates some 404 errors is the site experiencing some issues. I did not have this issue yesterday?

I used this command for all of my other installs:

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

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 14 LTS              ✘   Bad install:  Node.js missing  Npm missing - Exit
  Clean npm cache                     
  Install Node-RED core               
  Move global nodes to local          
  Npm rebuild existing nodes          
  Install extra Pi nodes              
  Add shortcut commands               
  Update systemd script               
                                      

Any errors will be logged to   /var/log/nodered-install.log

pi@raspberrypi:~ $ 

tReading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libc-ares2 libnode64 libuv1 nodejs-doc
Suggested packages:
  npm
The following NEW packages will be installed:
  libc-ares2 libnode64 libuv1 nodejs nodejs-doc
0 upgraded, 5 newly installed, 0 to remove and 84 not upgraded.
Need to get 6,100 kB of archives.
After this operation, 27.7 MB of additional disk space will be used.
Err:1 http://raspbian.raspberrypi.org/raspbian buster/main armhf libc-ares2 armhf 1.14.0-1
  404  Not Found [IP: 93.93.128.193 80]
Err:2 http://raspbian.raspberrypi.org/raspbian buster/main armhf libuv1 armhf 1.24.1-1
  404  Not Found [IP: 93.93.128.193 80]
Err:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf libnode64 armhf 10.21.0~dfsg-1~deb10u1+rpi1
  404  Not Found [IP: 93.93.128.193 80]
Err:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf nodejs armhf 10.21.0~dfsg-1~deb10u1+rpi1
  404  Not Found [IP: 93.93.128.193 80]
Err:5 http://raspbian.raspberrypi.org/raspbian buster/main armhf nodejs-doc all 10.21.0~dfsg-1~deb10u1+rpi1
  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/c/c-ares/libc-ares2_1.14.0-1_armhf.deb  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/libu/libuv1/libuv1_1.24.1-1_armhf.deb  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/n/nodejs/libnode64_10.21.0~dfsg-1~deb10u1+rpi1_armhf.deb  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/n/nodejs/nodejs_10.21.0~dfsg-1~deb10u1+rpi1_armhf.deb  404  Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/n/nodejs/nodejs-doc_10.21.0~dfsg-1~deb10u1+rpi1_all.deb  404  Not Found [IP: 93.93.128.193 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?ype or paste code here
1 Like
2

There is something odd going on with your system.

First try and bring your system up to date using
sudo apt update && sudo apt full-upgrade
If that fails then post the output here.

1 Like
3

Colin,
I forgot

sudo apt update && sudo apt full-upgrade

on this machine. I have been working on this project since about this time yesterday with about three hours sleep. Time for a brew here in Colorado USA.

Thanks so much for waking me up.

Dave

4

Sorry Colin my last full upgrade on a pi 400 resulted with this when I
ran the Node_red update
CLI output(The last little bits at the end of the CLI output was me attempting to run the suggested command. I may have to quit now to have my draft.

Dave

Running Node-RED install for user pi at /home/pi on raspbian

Nodejs 10 is no longer supported.
  You can update to the latest Node-RED 1.x version by adding  --nodered-version="1.3.5"
  to that install command. If in doubt this is the safer option.
  
  Or you can force an install of node 12 or 14 by using the --node12, --node14 or --node16 parameter
  However doing so may break some nodes that may need re-installing manually.
  Generally it is recommended to upgrade all nodes to their latest versions before upgrading.
  
  Please backup your installation and flows before upgrading.
  
  Exiting now.
pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered--version="1.3.5"
> ^C
pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered--version="1.3.5")
/dev/fd/63: line 1: 404:: command not found
pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered--nodered-version="1.3.5")
/dev/fd/63: line 1: 404:: command not found
pi@raspberrypi:~ $

Install error log:

Already have nodejs v10.24.0
OLD nodejs 10 :
NEW nodejs  :
Nodejs 10 too old and new version not specified - exiting
5

I Finally got the CLI input correct syntax correct. There are so many languages to have some grasp of today

Thanks for all of the help. I am now on the downside of the idiot curve I hope.
Dave

Here is my CLI output for reference after the Bash adjustment was made.

This can take 20-30 minutes on the slower Pi versions - please wait.

  Stop Node-RED                       ✔
  Remove old version of Node-RED      ✔
  Node option not specified           :   --node12, --node14, or --node16
  Leave existing Node.js              :   v10.24.0   Npm 5.8.0
  Clean npm cache                     -
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
  Install Node-RED core               ✔   1.3.5 
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
  Move global nodes to local          ✔
  Leave existing nodes                -
  Install extra Pi nodes              ✔
  Add shortcut commands               ✔
  Update systemd script               ✔



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 :  Thu 02 Dec 2021 06:49:26 PM EST 
Finished:  Thu 02 Dec 2021 06:51:54 PM EST
 
You may want to run   node-red admin init
to configure your initial options and settings.
 
pi@raspberrypi:~ $
6

Is there any reason why you are using Raspberry Pi OS Buster rather than the latest release Bullseye?

Did you deliberately install an old version of Node-Red?
I suspect you were misled by the message " You can update to the latest Node-RED 1.x version by adding --nodered-version="1.3.5" to that install command."
The latest Node-Red version is 2.1.4. Unless you want an old version you should not use --nodered-version=n.

I too have had a "Bad install" error on a couple of recent Raspberry Pi installs.
I resolved it by a) re-running the install script or b) sudo apt install npm and then re-running the install script specifying --node16.

7

Hello you will have to give me a hint as to where to specify --node16. I tried to add it on to the end of the install statement. That did not work.

On a side note have you ever heard of issues with Rpi 4's and 400s not playing with i2c BUS? I am tearing my hair out trying to get this figured out?

Thanks
Dave
Appreciate the Help.

8

After the closing bracket.

bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node16

I'm not sure if this will upgrade Node-Red from 1.3.5 to 2.1.4.
If it's a new Raspberry Pi setup it might be worth reburning the OS.

No idea about I2C, sorry.

9

I am confused by ask your earlier posts. Does
sudo apt update && sudo apt full-upgrade
work? If not then you need to sort that first.

@jbudd is right though, if this is a new setup then you should use Bullseye.

10

The situation became a lot muddier yesterday as Rpi have introduced a "legacy" Buster.

I think that maybe we should be recommending this Buster version until the Bullseye one becomes stable.

But this is only day 2 of a new world so who knows?

11

Is it not stable?

12

supported/working with old stuff/whatever word you want

They haven't released an updated Buster for the fun of it :slight_smile:

13

Probably best to read the blog post to get the full story.

It is not that bullseye isn't stable, but as with any new major version it causes churn in some areas. They have released their "legacy" OS image, based on Buster, which won't have major changes for another 2 years.

It won't be supported on any new Raspberry Pi hardware they may release as that hardware could rely on newer kernel/libraries. But if you have something stable running on existing hardware with Buster, it gives you an option to keep running on a supported OS for some time to come.

14

I looked at a Buster to Bullseye upgrade for my Debian home server - I can see that upgrades in the land of Linux have really not improved over the years! :frowning:

There were so many caveats and manual fixes needed that I gave up after about 1/2 an hours reading.

15

It is the equivalent of nodejs v16 being the current LTS release, but security releases of 14 and 12 are still provided so old apps can keep running. Or Ubuntu 20.04, which is the current LTS but 18.04, 16.04 and 14.04 still receive security fixes.

16

Do you mean trying to do an upgrade of an existing system? I agree that isn't going to work easily. I think a re-install is needed, which is a pain.

That is one thing that Ubuntu does rather well, they have a dedicated piece of s/w that handles an upgrade, which usually works remarkably well.

17

Yes. If I do have to do a new install, it probably wont be Debian if they can't manage upgrades better than this.

I've been trying to avoid Ubuntu, preferring the simplicity and stability of Debian. But maybe I'll be forced to change.

Any OS that can't handle a major version upgrade isn't worth using.

18

I mistakenly at first downloaded Bullseye Imager page at rpi.org. I certainly was quicker, then as I began to bring up some of my "legacy" flows, I began to have issues with things not working. If you have run across some of my posts here you would see. I revert backward to buster, and all was working, mostly again. I did notice straight away that Bullseye was much much faster off the line!

After seeing the news yesterday late, I am reticent to touch anything until the alternatives at hand are explored my more advanced spirits than i.

Dave

19

It did make it through the upgrade process without error, but apparently i am running 1.3.5 as opposed to 2,1,4.

Dave

20

Did you specify a node red version when you ran the script? If so then run it again without the node red version specified, but tell it to install node version 14 or 16.