Now quite as bad as my other post where I thought I had killed the remote machine.
I was going through updating the machines and NR.
(Too many different versions to be nice.)
Some/most updated nicely. A few didn't.
Some which stopped loading NR were fixed by me going in and starting NR manually and setting it to auto load with:
sudo systemctl enable nodered.service
If I didn't manually start it, it didn't seem to want to load.
So after that, most of the problematic ones started to work again.
Alas now I am down to 2 or 3.
extra stuff in to maybe help.
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 - Update 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 menu shortcut Update systemd script Any errors will be logged to /var/log/nodered-install.log pi@BedPi:~/.node-red $ node-red start -bash: node-red: command not found pi@BedPi:~/.node-red $
What I could gleam from the log is that NR was already at the latest version. (shrug)
Ok. That's me stumped.
For now there are two machines with this problem.
All I did to update them was enter:
bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)
As said: most machines did it no problem. A couple had to be nudged and these couple are just being stubborn.
Further trials seem to indicate that I have lost the command npm too.
Using this link to upgrade NR.
But the .node-red directory exists. It isn't like it has been uninstalled.