search

node-red / linux-installers

Node-RED install scripts for various flavours of Linux
Apache License 2.0
94 stars 63 forks source link

Install fails, finds no npm #39

Closed jpelletier closed 1 year ago

jpelletier commented 1 year ago

Tried to install node-red on a Banana pi M2 Zero with these instructions: https://nodered.org/docs/getting-started/raspberrypi The script fails, can't find npm

knolleary commented 1 year ago

What OS have you installed on the banana pi and how did you install node.js?

jpelletier commented 1 year ago

I used this Ubuntu 2022-09-27-Armbian_22.11.0-trunk_jammy_edge_lubuntu_5.19.6-qt5-swap-bpi-P2z-M2Z-10804MB

Node.js was already included. I tried installing npm, but I had the same problem. I tried with --node16 with same problem.

The script worked fine on a raspberry pi 3+.

hardillb commented 1 year ago

Please attach the log file created by the install script.

knolleary commented 1 year ago

I'm going to transfer this issue over to the installer repo.

jpelletier commented 1 year ago

Here is the log file: nodered-install.log

Steve-Mcl commented 1 year ago

Did you add --node16 or --node18 to the end of the command?

e.g.

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

I tried with --node16 at the end, as you mentioned. It worked with the Raspberry Pi but not the Banana Pi.

dceejay commented 1 year ago

from your log - 

Err:3 http://mirror.albony.xyz/armbian jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5
Reading package lists...
E: Repository 'https://itai-nelken.github.io/weekly-box86-debs/debian  InRelease' changed its 'Origin' value from 'weekly_box86_debs' to ''
E: Repository 'https://itai-nelken.github.io/weekly-box86-debs/debian  InRelease' changed its 'Label' value from 'weekly_box86_debs' to ''
E: Repository 'https://itai-nelken.github.io/weekly-box86-debs/debian  InRelease' changed its 'Codename' value from 'buster' to ''
W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059
E: The repository 'http://cli.github.com/packages stable InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://mirror.albony.xyz/armbian jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5
Error executing command, exiting

So it seems that the Armbian repository it is trying to use for nodes isn't fully "signed" so nodejs is failing to install correctly (so then the script fails and then install node 12 from the default repo which doesn't contain npm and etc etc... not good.

I think you are going to have to install nodejs 16 manually first - or get the correct signed key for that repo - or change your update repos to be a more stable one rather than "weekly" - and then you can run the script to install Node-RED on top.

jpelletier commented 1 year ago

Update: I switched to the Raspberry Pi Zero 2 W because of the camera port, and I don't need node-red finally.