Node-red bash curl script install fails on Coral Dev board

Google used some "weird" and apparently poorly documented "Mendel-Chef" Debian variation. I managed to get OpenCV 4.0.0 to build on it following some instructions I'd found via Google search (although trying 4.1.0 failed horribly with these instructions). My AI code runs nicely on this, about the same a the Pi4B. The main advantage is its a nice small package with the TPU build in as opposed to being an external Dongle and it has a built in fan. The Pi4 needs a fan to run the AI workload. Now I need to install node red to complete the system.

Unfortunately the bash curl install script fails:

All packages are up to date.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.52.1-5+deb9u9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

## Installing the NodeSource Node.js 10.x repo...


## Populating apt-get cache...

+ apt-get update
Get:1 file:/var/cache/mdt/packages ./ InRelease
Ign:1 file:/var/cache/mdt/packages ./ InRelease
Get:2 file:/var/cache/mdt/packages ./ Release
Ign:2 file:/var/cache/mdt/packages ./ Release
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Hit:6 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
Hit:7 https://packages.cloud.google.com/apt mendel-bsp-enterprise-chef InRelease
Hit:8 https://packages.cloud.google.com/apt mendel-chef InRelease
Reading package lists...

## Confirming "chef" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/chef/Release'

## Your distribution, identified as "chef", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support


WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,174 kB of archives.
After this operation, 13.4 MB of additional disk space will be used.
Get:1 https://packages.cloud.google.com/apt mendel-chef/main arm64 nodejs arm64 4.8.2~dfsg-1 [3,174 kB]
Fetched 3,174 kB in 0s (4,706 kB/s)
Selecting previously unselected package nodejs.
(Reading database ... 46236 files and directories currently installed.)
Preparing to unpack .../nodejs_4.8.2~dfsg-1_arm64.deb ...
Unpacking nodejs (4.8.2~dfsg-1) ...
Setting up nodejs (4.8.2~dfsg-1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for man-db (2.7.6.1-2) ...
sudo: npm: command not found
mendel@Coral:~$ 

Sudo apt-get install npm fails.Nodejs in installed and is 4.8.2. Curious that a "Google" product would be so out of date with nodejs.

Am I out of luck, or is there some reasonably easy fix?

Try installing node manually. You would need to apt uninstall the v4 version first. Then follow the instruction on the nodejs web site. Hopefully that would get node 10 installed. Then retry the script

I finally got around to trying it, and got nodejs and npm installed from the nodejs web site arm64.xz file and re-ran the bash curl script. But when I got to:

All done.
  You can now start Node-RED with the command  node-red-start

when I did node-red-start:

mendel@Coral:~$ node-red-start

Node-RED is not yet fully installed

Fetching Node-RED update.
...

So I let the update run.

When I got to:

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  Tue Aug 27 15:12:55 CDT 2019  -  Finished  Tue Aug 27 15:14:29 CDT 2019

Would you like to start Node-RED now (y/N) ? y

It appears I'm stuck in an installation/update loop.

Node-RED is not yet fully installed

Fetching Node-RED update.

 
This script will remove versions of Node.js prior to version 7.x, and Node-RED and
if necessary replace them with Node.js 10.x LTS (dubnium) and the latest Node-RED from Npm.

Any ideas on how to fix?

hmm - so what do the commands node -v and npm -v report ? and which node ?
(we may have to go fully manual on this - but no matter)
Once we get nodejs back to a decent state (ie node 10.x and npm 6.x) - we should be able to do
sudo npm i -g --unsafe-perm node-red
This won't install the service files etc - but they may already (now) be in place having run the script several times :-)...
Then try node-red-start - if that fails - just try node-red - which won;t stat it as a service but hopefully will at least then run. (we can work from there)

mendel@Coral:~$ node -v
v10.16.3
mendel@Coral:~$ npm -v
6.11.2
mendel@Coral:~$ which node
/usr/bin/node

This is the symlink I made following the nodejs.org installation instructions. I removed the 4.8 nodejs that got installed as part of the initial failure before re-runing the bash curl script after installing node.

Nothing of note (to me) in the log file from the last "loop":

mendel@Coral:~$ cat /var/log/nodered-install.log

***************************************

Started : Wed Aug 28 14:05:52 CDT 2019
Running for user mendel at /home/mendel
Found global nodes:   :

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package nodered
Now install nodejs

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package npm
(Reading database ... 46297 files and directories currently installed.)
Removing nodejs (4.8.2~dfsg-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
dpkg: warning: ignoring request to remove node which isn't installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 file:/var/cache/mdt/packages ./ InRelease
Ign:1 file:/var/cache/mdt/packages ./ InRelease
Get:2 file:/var/cache/mdt/packages ./ Release
Ign:2 file:/var/cache/mdt/packages ./ Release
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Get:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en
Ign:4 file:/var/cache/mdt/packages ./ Translation-en
Get:5 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:5 file:/var/cache/mdt/packages ./ Translation-en_US
Hit:6 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
Hit:7 https://packages.cloud.google.com/apt mendel-bsp-enterprise-chef InRelease
Hit:8 https://packages.cloud.google.com/apt mendel-chef InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.52.1-5+deb9u9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

## Installing the NodeSource Node.js 10.x repo...


## Populating apt-get cache...

+ apt-get update
Get:1 file:/var/cache/mdt/packages ./ InRelease
Ign:1 file:/var/cache/mdt/packages ./ InRelease
Get:2 file:/var/cache/mdt/packages ./ Release
Ign:2 file:/var/cache/mdt/packages ./ Release
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Ign:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Get:3 file:/var/cache/mdt/packages ./ Packages
Get:4 file:/var/cache/mdt/packages ./ Translation-en_US
Ign:4 file:/var/cache/mdt/packages ./ Translation-en_US
Get:5 file:/var/cache/mdt/packages ./ Translation-en
Ign:5 file:/var/cache/mdt/packages ./ Translation-en
Hit:6 https://packages.cloud.google.com/apt coral-edgetpu-stable InRelease
Hit:7 https://packages.cloud.google.com/apt mendel-bsp-enterprise-chef InRelease
Hit:8 https://packages.cloud.google.com/apt mendel-chef InRelease
Reading package lists...

## Confirming "chef" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/chef/Release'

## Your distribution, identified as "chef", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support


WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,174 kB of archives.
After this operation, 13.4 MB of additional disk space will be used.
Get:1 https://packages.cloud.google.com/apt mendel-chef/main arm64 nodejs arm64 4.8.2~dfsg-1 [3,174 kB]
Fetched 3,174 kB in 0s (4,740 kB/s)
Selecting previously unselected package nodejs.
(Reading database ... 46236 files and directories currently installed.)
Preparing to unpack .../nodejs_4.8.2~dfsg-1_arm64.deb ...
Unpacking nodejs (4.8.2~dfsg-1) ...
Setting up nodejs (4.8.2~dfsg-1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for man-db (2.7.6.1-2) ...
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/npm -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/npm/bin/npm-cli.js
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/npx -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/npm/bin/npx-cli.js
+ npm@6.11.2
updated 1 package in 23.572s
Now install Node-RED
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red-pi -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/bin/node-red-pi
+ node-red@0.20.7
updated 1 package in 21.741s
0.20.7 
Now create basic package.json for the user and move any global nodes
Now add the shortcut and start/stop/log scripts to the menu
Now add systemd script and configure it for mendel
Now add launcher to top bar, add cpu temp example, make sure ping works
Finished : Wed Aug 28 14:05:52 CDT 2019

Tried the full manual, no luck, back in the not fully installed loop :frowning:

mendel@Coral:~$ sudo npm i -g --unsafe-perm node-red
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red-pi -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/bin/node-red-pi
+ node-red@0.20.7
updated 1 package in 22.774s
mendel@Coral:~$ node-red-start

Node-RED is not yet fully installed

Fetching Node-RED update.

I'm stuck and stumped. The Coral Development board would make a nice AI host, cost is good for the performance considering it has the TPU "built-in", but its a weird system and documenting how to set it up so a "normal" person could just buy one and follow along and expect it to work at the end is beyond me at this point.

I can do what I do with node-red in other ways, but the strength of the node-red that I use is its "portability" I've used it on Jetson Nano, Odroid XU-4, AtomicPi, I3 "MiniPC" along with my desktop development system. The dashboard let me make a simple UI that "normal" people can use to control the system from a cell phone web browser.

Ok so nodejs is ok. Try the manual install commands I posted above.

I just did, it was the last cut and paste command and output I posted.

Here it is again:

mendel@Coral:~$ sudo npm i -g --unsafe-perm node-red
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red-pi -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/bin/node-red-pi
+ node-red@0.20.7
updated 1 package in 22.774s


mendel@Coral:~$ node-red-start

Node-RED is not yet fully installed

Fetching Node-RED update.

and just - node-red command ?

mendel@Coral:~$ node-red
-bash: node-red: command not found

I bet this is a clue :slight_smile:
Where is it supposed to be installed. its not in /usr/bin

mendel@Coral:~$ ls -l /usr/bin/no*
lrwxrwxrwx 1 root root       50 Aug 27 15:02 /usr/bin/node -> /home/mendel/ai/node-v10.16.3-linux-arm64/bin/node
lrwxrwxrwx 1 root root       50 Aug 28 14:29 /usr/bin/nodejs -> /home/mendel/ai/node-v10.16.3-linux-arm64/bin/node
-rwxr-xr-x 1 root root 10407264 Apr  4  2017 /usr/bin/nodejs_4.8.2
-rwxr-xr-x 1 root root      328 Aug 28 14:07 /usr/bin/node-red-log
-rwxr-xr-x 1 root root       99 Aug 28 14:07 /usr/bin/node-red-restart
-rwxr-xr-x 1 root root     4574 Aug 28 14:07 /usr/bin/node-red-start
-rwxr-xr-x 1 root root      228 Aug 28 14:07 /usr/bin/node-red-stop
-rwxr-xr-x 1 root root    31456 Feb 22  2017 /usr/bin/nohup

and sudo systemctl start nodered ?

the install reported

/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js
/home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/bin/node-red-pi -> /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/bin/node-red-pi

so it has installed them... just not added the links into /usr/bin... odd

Is this progress?

mendel@Coral:~$ sudo systemctl start nodered


mendel@Coral:~$ systemctl status nodered
â—Ź nodered.service - Node-RED graphical event wiring tool
   Loaded: loaded (/lib/systemd/system/nodered.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-08-28 15:10:30 CDT; 18s ago
     Docs: http://nodered.org/docs/hardware/raspberrypi.html
  Process: 26115 ExecStart=/usr/bin/env node-red-pi $NODE_OPTIONS $NODE_RED_OPTIONS (code=exited, status=127)
 Main PID: 26115 (code=exited, status=127)

Aug 28 15:10:30 Coral systemd[1]: nodered.service: Failed with result 'exit-code'.
Aug 28 15:10:30 Coral systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Aug 28 15:10:30 Coral systemd[1]: Stopped Node-RED graphical event wiring tool.
Aug 28 15:10:30 Coral systemd[1]: nodered.service: Start request repeated too quickly.
Aug 28 15:10:30 Coral systemd[1]: Failed to start Node-RED graphical event wiring tool.
Aug 28 15:10:30 Coral systemd[1]: nodered.service: Unit entered failed state.
Aug 28 15:10:30 Coral systemd[1]: nodered.service: Failed with result 'exit-code'.

not really... - it's the failure for the install to add the links into the correct place that is the problem.
can you try the raw command node /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js

That got it.

mendel@Coral:~$ node /home/mendel/AI/LorexAI/node-v10.16.3-linux-arm64/lib/node_modules/node-red/red.js
28 Aug 15:26:12 - [info] 

Welcome to Node-RED
===================

28 Aug 15:26:12 - [info] Node-RED version: v0.20.7
28 Aug 15:26:12 - [info] Node.js  version: v10.16.3
28 Aug 15:26:12 - [info] Linux 4.9.51-imx arm64 LE
28 Aug 15:26:13 - [info] Loading palette nodes
28 Aug 15:26:15 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
28 Aug 15:26:15 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
28 Aug 15:26:16 - [info] Settings file  : /home/mendel/.node-red/settings.js
28 Aug 15:26:16 - [info] Context store  : 'default' [module=memory]
28 Aug 15:26:16 - [info] User directory : /home/mendel/.node-red
28 Aug 15:26:16 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Aug 15:26:16 - [info] Flows file     : /home/mendel/.node-red/flows_Coral.json
28 Aug 15:26:16 - [info] Creating new flow file
28 Aug 15:26:16 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

28 Aug 15:26:16 - [info] Starting flows
28 Aug 15:26:16 - [info] Started flows
28 Aug 15:26:16 - [info] Server now running at http://127.0.0.1:1880/

How do I fix it so the "normal" node-red-start and systemctl enable commands work?

What symlinks do I need to make, or scripts do I need to edit to make up for what the installer script failed to do?

create symlinks to both of those lines above - one to /usr/bin/node-red the second to /usr/bin/node-red-pi

1 Like

Thanks for all you help.

It appears to be working correctly now. I'll know for sure after I reboot it, but the sudo systemctl enable nodered.service seems to have completed without errors. I installed the dashboard and a couple of other extra nodes I use.

1 Like