# Node-Red don't longer start

**URL:** <https://discourse.nodered.org/t/node-red-dont-longer-start/52590>\
**Category:** General\
**Created:** [22 October 2021 19:16 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590 "2021-10-22T19:16:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [22 October 2021 19:16 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/1 "2021-10-22T19:16:43Z")

</div>

Sorry to seek your help. I can no longer get Node-Red to start up.  
During all my free time in over a week, I try in vain to find a way out by myself.  
The misery started in an attempt to install the 'Palette Manager'. In the meantime I have 'uninstalled' and 'installed' Node Red several times.  
Here is the message I get on the instruktions

- Node-Red and

- Start-node-red.

```auto
Start Node-RED 
Once Node-RED has started, point a browser at http://192.168.0.128:1880 On Pi Node-RED works better with the Firefox or Chrome browser
 
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
 
To find more nodes and example flows - go to http://flows.nodered.org
 
Starting as a systemd service.
Started Node-RED graphical event wiring tool.
/usr/lib/node_modules/node-red/node_modules/fs-extra/node_modules/universalify/index.js:15
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.

```

```auto
pi@raspberrypi:~ $ node-red
/usr/lib/node_modules/node-red/node_modules/fs-extra/node_modules/universalify/index.js:15
  }, 'name', { value: fn.name })
                         ^

TypeError: Cannot read property 'name' of undefined
    at exports.fromCallback (/usr/lib/node_modules/node-red/node_modules/fs-extra/node_modules/universalify/index.js:15:26)
    at Object.<anonymous> (/usr/lib/node_modules/node-red/node_modules/fs-extra/lib/fs/index.js:57:27)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/lib/node_modules/node-red/node_modules/fs-extra/lib/index.js:5:6)
pi@raspberrypi:~ $

```

NB: How can I change my username at the forum please?

Thanks in advance.

Jack

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [22 October 2021 21:11 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/2 "2021-10-22T21:11:15Z")

</div>

Something is messed up in the folder `/usr/lib/node-modules/node-red`. I suggest deleting that folder and running the pi node-red install script to re-install it.

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 14:14 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/3 "2021-10-23T14:14:30Z")

</div>

The /usr/lib/node\_modules/node-red directory has been emptied.  
The directories themselves could not be deleted.  
After installing node-red, the following message appears.  
How is this solved or is it absolutely necessary that the folders are actually removed?

```auto
pi@raspberrypi:~ $ node-red-start

Node-RED is not yet fully installed
/usr/bin/node-re`Preformatted text`d-start: line 91: update-nodejs-and-nodered: command not found pi@raspberrypi:~ $

```

Thank you very much.

Jack

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 14:19 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/4 "2021-10-23T14:19:57Z")

</div>

> [@fredshortlv129bis](#):
>
> After installing node-red,

How did you do that? The _exact_ commands please.

Please post the file `/var/log/nodered-install.log` if it exists.

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 15:21 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/5 "2021-10-23T15:21:27Z")

</div>

> [@Colin](#):
>
> the file `/var/log/nodered-install.log` if it exists.

The file '/var /log/nodered-install.log' does not currently exist.

The following instructions were executed :

````auto
pi@raspberrypi:~ $ sudo find /usr/lib/node-modules/node-red/ -mindepth 1 -delete

pi@raspberrypi:~ $ sudo apt install build-essential git curl

pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
```Preformatted text

After sending the present message, the following was also performed.

`pi@raspberrypi:~ $ sudo npm install -g --unsafe-perm node-red`

With thanks.

Jack
````

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 15:30 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/6 "2021-10-23T15:30:03Z")

</div>

Small correction to the above.  
The first instruction was exactly

```
  ` pi@raspberrypi:~ $ sudo find /usr/lib/node_modules/node-red/ -mindepth 1 -delete`

```

Thanks

Jack

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 15:47 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/7 "2021-10-23T15:47:23Z")

</div>

You could have used `rm -rf` to remove the folder.

What do you see on screen when you run the bash curl command?

> [@fredshortlv129bis](#):
>
> The file '/var /log/nodered-install.log' does not currently exist.

Are you certain of that?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [23 October 2021 16:02 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/8 "2021-10-23T16:02:40Z")

</div>

I am puzzled by the error message "/usr/bin/node-red-start: line 91: update-nodejs-and-nodered: command not found..."  
Please can you show the result of this command

`wc /usr/bin/*node-red*`

> [@fredshortlv129bis](#):
>
> The file '/var /log/nodered-install.log' does not currently exist.

EDIT: NB no space between var and /log

What about /var/log/nodered-install.log.1 ?  
Is /var/log a tmpfs?  
Please run these two commands

```auto
ls -l /var/log/*nodered*
df -h

```

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 16:14 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/9 "2021-10-23T16:14:15Z")

</div>

```auto
pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)e[2 q
 
This script checks the version of node.js installed is 12 or greater. It will try to
install node 14 if none is found. It can optionally install node 12, 14 or 16 LTS for you.
 
If necessary it will then remove the old core of Node-RED, before then installing the latest
version. You can also optionally specify the version required.
 
It also tries to run 'npm rebuild' to refresh any extra nodes you have installed
that may have a native binary component. While this normally works ok, you need
to check that it succeeds for your combination of installed nodes.
 
To do all this it runs commands as root - please satisfy yourself that this will
not damage your Pi, or otherwise compromise your configuration.
If in doubt please backup your SD card first.
 
See the optional parameters by re-running this command with --help
 
Are you really sure you want to do this ? [y/N] ? y

Would you like to install the Pi-specific nodes ? [y/N] ? y
/dev/fd/63: regel 211: /usr/bin/id: kan binair bestand Verkeerd uitvoerbaar bestand niet uitvoeren

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

Nodejs 8 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:~ $

```

* * *

```auto
Already have nodejs v8.11.1
OLD nodejs 8 :
NEW nodejs :
Nodejs 8 too old and new version not specified - exiting
Already have nodejs v8.11.1
OLD nodejs 8 :
NEW nodejs :
Nodejs 8 too old and new version not specified - exiting
Already have nodejs v8.11.1
OLD nodejs 8 :
NEW nodejs :
Nodejs 8 too old and new version not specified - exiting

```

I don't know the correct syntax how to use 'rm -rf'.

Thanks.

Jack

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [23 October 2021 16:17 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/10 "2021-10-23T16:17:39Z")

</div>

You can force it to install nodejs version 12 by this command

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

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 16:21 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/11 "2021-10-23T16:21:27Z")

</div>

Just to clarify the message you saw, it is saying that you can't use nodejs 8 and must update it to at least 12. I recommend 14, but 12 is ok.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [23 October 2021 16:22 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/12 "2021-10-23T16:22:37Z")

</div>

It would be useful to see the results of these commands too:

```auto
cat /sys/firmware/devicetree/base/model

grep PRETTY_NAME /etc/os-release

```

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 17:00 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/13 "2021-10-23T17:00:02Z")

</div>

```auto
pi@raspberrypi:~ $ wc /usr/bin/*node-red*
  494 1572 18711 /usr/bin/node-red
   13 50 328 /usr/bin/node-red-log
   43 170 1271 /usr/bin/node-red-pi
  104 558 4572 /usr/bin/node-red-start
    8 28 226 /usr/bin/node-red-stop
  662 2378 25108 totaal
pi@raspberrypi:~ $

```

```auto
pi@raspberrypi:~ $ ls -l /var/log/*nodered*
-rw-r--r-- 1 root root 342 okt 23 17:56 /var/log/nodered-install.log
pi@raspberrypi:~ $ df -h
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/root 14G 4,6G 7,9G 38% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 91M 373M 20% /dev/shm
tmpfs 464M 18M 446M 4% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p6 65M 23M 43M 35% /boot
tmpfs 93M 0 93M 0% /run/user/1000
/dev/mmcblk0p5 30M 1,6M 27M 6% /media/pi/SETTINGS
pi@raspberrypi:~ $

```

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 17:03 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/14 "2021-10-23T17:03:15Z")

</div>

OK Thank you.  
Jack

Eureka there is progress I think....

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

  Stop Node-RED ✔
  Remove old version of Node-RED ✔
/dev/fd/63: regel 408: /usr/bin/head: kan binair bestand Verkeerd uitvoerbaar bestand niet uitvoeren
  Remove old version of Node.js ✔ v8.11.1
  Install Node.js 14 LTS ✘ Bad install: Node.js v8.11.1 Npm missing - Exit
  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:~ $

```

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 17:31 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/15 "2021-10-23T17:31:37Z")

</div>

```auto
(Database wordt ingelezen ... 20%
(Database wordt ingelezen ... 25%
(Database wordt ingelezen ... 30%
(Database wordt ingelezen ... 35%
(Database wordt ingelezen ... 40%
(Database wordt ingelezen ... 45%
(Database wordt ingelezen ... 50%
(Database wordt ingelezen ... 55%
(Database wordt ingelezen ... 60%
(Database wordt ingelezen ... 65%
(Database wordt ingelezen ... 70%
(Database wordt ingelezen ... 75%
(Database wordt ingelezen ... 80%
(Database wordt ingelezen ... 85%
(Database wordt ingelezen ... 90%
(Database wordt ingelezen ... 95%
(Database wordt ingelezen ... 100%
(Database wordt ingelezen ... 85661 bestanden en mappen momenteel geïnstalleerd.)
libc-ares2:armhf (1.14.0-1~bpo9+1) wordt verwijderd ...
libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) wordt verwijderd ...
nodejs-doc (8.11.1~dfsg-2~bpo9+1) wordt verwijderd ...
Bezig met afhandelen van triggers voor libc-bin (2.24-11+deb9u4) ...
Segmentation fault
Grab the LTS bundle

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

Pakketlijsten worden ingelezen...
Boom van vereisten wordt opgebouwd...
De statusinformatie wordt gelezen...
curl is reeds de nieuwste versie (7.52.1-5+deb9u16).
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.

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

## Populating apt-get cache...

+ apt-get update
Geraakt:1 http://archive.raspberrypi.org/debian stretch InRelease
Geraakt:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Geraakt:3 https://repos.influxdata.com/debian stretch InRelease
Fout:4 https://repo.mosquitto.org/debian jessie InRelease
  De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
Fout:5 https://repo.mosquitto.org/debian stretch InRelease
  De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
Segmentation fault
Pakketlijsten worden ingelezen...
W: Er is een fout opgetreden bij de controle van de ondertekening. De pakketbron is niet bijgewerkt en de oude indexbestanden zullen worden gebruikt. GPG-fout: https://repo.mosquitto.org/debian jessie InRelease: De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Er is een fout opgetreden bij de controle van de ondertekening. De pakketbron is niet bijgewerkt en de oude indexbestanden zullen worden gebruikt. GPG-fout: https://repo.mosquitto.org/debian stretch InRelease: De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van https://repo.mosquitto.org/debian/dists/jessie/InRelease is mislukt De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van https://repo.mosquitto.org/debian/dists/stretch/InRelease is mislukt De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van sommige indexbestanden is mislukt. Deze zijn of genegeerd, of er zijn oudere versies van gebruikt.
main: /usr/bin/lsb_release: +usr'àin/pØthoN3: ongeldige interpreter: Bestand of map bestaat niet
main: /usr/bin/lsb_release: +usr'àin/pØthoN3: ongeldige interpreter: Bestand of map bestaat niet

## Confirming "" is supported...

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

## Your distribution, identified as "", 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.

Pakketlijsten worden ingelezen...
Boom van vereisten wordt opgebouwd...
De statusinformatie wordt gelezen...
De volgende extra pakketten zullen geïnstalleerd worden:
  libc-ares2 libhttp-parser2.8 nodejs-doc
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  libc-ares2 libhttp-parser2.8 nodejs nodejs-doc
0 opgewaardeerd, 4 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
Er moeten 5.001 kB aan archieven opgehaald worden.
Na deze bewerking zal er 22,0 MB extra schijfruimte gebruikt worden.
Ophalen:1 http://archive.raspberrypi.org/debian stretch/main armhf libc-ares2 armhf 1.14.0-1~bpo9+1 [80,7 kB]
Ophalen:2 http://archive.raspberrypi.org/debian stretch/main armhf libhttp-parser2.8 armhf 2.8.1-1~bpo9+1 [19,3 kB]
Ophalen:3 http://archive.raspberrypi.org/debian stretch/main armhf nodejs armhf 8.11.1~dfsg-2~bpo9+1 [4.126 kB]
Ophalen:4 http://archive.raspberrypi.org/debian stretch/main armhf nodejs-doc all 8.11.1~dfsg-2~bpo9+1 [775 kB]
/usr/bin/locale: 1: /usr/bin/locale: ELF!: not found
/usr/bin/locale: 2: /usr/bin/locale: Syntax error: word unexpected (expecting ")")
N: Negeren van bestand 'mosquitto-jessie.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.6' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.5' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.4' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.3' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
5.001 kB opgehaald in 4s (1.005 kB/s)
Voorheen niet geselecteerd pakket libc-ares2:armhf wordt geselecteerd.
(Database wordt ingelezen ... 
(Database wordt ingelezen ... 5%
(Database wordt ingelezen ... 10%
(Database wordt ingelezen ... 15%
(Database wordt ingelezen ... 20%
(Database wordt ingelezen ... 25%
(Database wordt ingelezen ... 30%
(Database wordt ingelezen ... 35%
(Database wordt ingelezen ... 40%
(Database wordt ingelezen ... 45%
(Database wordt ingelezen ... 50%
(Database wordt ingelezen ... 55%
(Database wordt ingelezen ... 60%
(Database wordt ingelezen ... 65%
(Database wordt ingelezen ... 70%
(Database wordt ingelezen ... 75%
(Database wordt ingelezen ... 80%
(Database wordt ingelezen ... 85%
(Database wordt ingelezen ... 90%
(Database wordt ingelezen ... 95%
(Database wordt ingelezen ... 100%
(Database wordt ingelezen ... 85531 bestanden en mappen momenteel geïnstalleerd.)
Uitpakken van .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb wordt voorbereid...
Bezig met uitpakken van libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Voorheen niet geselecteerd pakket libhttp-parser2.8:armhf wordt geselecteerd.
Uitpakken van .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb wordt voorbereid...
Bezig met uitpakken van libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Voorheen niet geselecteerd pakket nodejs wordt geselecteerd.
Uitpakken van .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb wordt voorbereid...
Bezig met uitpakken van nodejs (8.11.1~dfsg-2~bpo9+1) ...
Voorheen niet geselecteerd pakket nodejs-doc wordt geselecteerd.
Uitpakken van .../nodejs-doc_8.11.1~dfsg-2~bpo9+1_all.deb wordt voorbereid...
Bezig met uitpakken van nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Instellen van nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Bezig met afhandelen van triggers voor libc-bin (2.24-11+deb9u4) ...
Bezig met afhandelen van triggers voor man-db (2.7.6.1-2) ...
Instellen van libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Instellen van libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Instellen van nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: /usr/bin/nodejs wordt gebruikt om in de automatische modus in /usr/bin/js (js) te voorzien.
Bezig met afhandelen van triggers voor libc-bin (2.24-11+deb9u4) ...
Segmentation fault

Versions: node:v8.11.1 npm:missing

```

The log was far too large. I tried to transfer it in three parts, but apparently that didn't work. Shall I try again?  
Jack

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [23 October 2021 19:17 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/16 "2021-10-23T19:17:17Z")

</div>

I don't know if the current Node-Red is compatible with RPiOS 9 (Stretch)  
Raspberry Pi OS 10 (Buster) was released in June 2019 and any month now 11 (Bullseye) will be released.

It would no doubt cause less problems if you can start again with a fresh RPiOS installation.  
I suppose that depends how much extra stuff you have installed. There is no easy upgrade path.

But back to Node-Red:  
I suspect you will have to install npm manually, no idea how to do that with an out of date OS.  
Maybe - sudo apt install npm, but the OS version might cause difficulties.  
I vaguely recall that I used to have to install npm before node-red on RPiOS Lite v9

Your /usr/bin/node-red\* files are different sizes to the ones I get with a new install.  
That suggests that the installation script does not replace those files.  
Maybe after installing npm try this

```auto
sudo rm rf /usr/lib/node_modules/node-red
sudo rm /usr/bin/node-red*
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node12

```

And then post the contents of /var/log/nodered-install.log

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 20:38 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/18 "2021-10-23T20:38:22Z")

</div>

> [@fredshortlv129bis](#):
>
> `Segmentation fault`

That is bad.

First run  
`sudo apt-get update`  
If that shows no errors then what do these show  
`apt-cache policy nodejs`  
`apt-cache policy npm`

**[Edit]** Also show us the result of the apt-get command even if it is ok.

---

<div class="post-metadata">

**Author:** ![fredshortlv129bis](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fredshortlv129bis](https://discourse.nodered.org/u/fredshortlv129bis)\
**Post date:** [23 October 2021 20:50 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/19 "2021-10-23T20:50:15Z")

</div>

Mosquitto apparently causes many error messages. I do not use that programme any more. I can delete it. Is that useful?  
Jack

```auto
pi@raspberrypi:~ $ sudo apt-get update
Geraakt:1 http://archive.raspberrypi.org/debian stretch InRelease
Geraakt:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease                      
Geraakt:3 https://repos.influxdata.com/debian stretch InRelease                           
Ophalen:4 https://repo.mosquitto.org/debian jessie InRelease [11,0 kB]
Ophalen:5 https://repo.mosquitto.org/debian stretch InRelease [12,4 kB]
Fout:4 https://repo.mosquitto.org/debian jessie InRelease       
  De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
Fout:5 https://repo.mosquitto.org/debian stretch InRelease
  De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
23,4 kB opgehaald in 5s (4.649 B/s)
Segmentation fault
Pakketlijsten worden ingelezen... Klaar
N: Negeren van bestand 'mosquitto-jessie.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.6' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.5' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.4' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.3' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
W: Er is een fout opgetreden bij de controle van de ondertekening. De pakketbron is niet bijgewerkt en de oude indexbestanden zullen worden gebruikt. GPG-fout: https://repo.mosquitto.org/debian jessie InRelease: De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Er is een fout opgetreden bij de controle van de ondertekening. De pakketbron is niet bijgewerkt en de oude indexbestanden zullen worden gebruikt. GPG-fout: https://repo.mosquitto.org/debian stretch InRelease: De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van https://repo.mosquitto.org/debian/dists/jessie/InRelease is mislukt De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van https://repo.mosquitto.org/debian/dists/stretch/InRelease is mislukt De volgende ondertekeningen waren ongeldig: EXPKEYSIG 61611AE430993623 Mosquitto Apt Repository <repo@mosquitto.org>
W: Ophalen van sommige indexbestanden is mislukt. Deze zijn of genegeerd, of er zijn oudere versies van gebruikt.
pi@raspberrypi:~ $

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 20:59 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/20 "2021-10-23T20:59:44Z")

</div>

> [@fredshortlv129bis](#):
>
> `De volgende ondertekeningen waren ongeldig`

Apparently you have not been keeping your system up to date. Mosquitto changed their key in 2019 I believe. Run  
`wget -O - http://repo.mosquitto.org/debian/mosquitto-repo.gpg.key | sudo apt-key add -`  
which should fix that. Then run the `apt-get update` again. If that is ok then run  
`sudo apt-get dist-upgrade`  
to bring your system up to date. If that all goes ok then try the script again.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2021 21:07 UTC](https://discourse.nodered.org/t/node-red-dont-longer-start/52590/21 "2021-10-23T21:07:21Z")

</div>

Sorry, I missed the fact that you aren't using mosquitto any more (I don't think I imagined anyone would stop using mosquitto, why woud anyone do that?). To remove it you can first remove the package  
`sudo apt-get remove mosquitto mosquitto-clients`  
then you must remove the references to the repository. Look in the folder `/etc/apt/sources.list.d` and there should be a file with mosquitto in the name. Remove that and run the `apt-get update` again.

[Next page](https://discourse.nodered.org/t/node-red-dont-longer-start/52590.md?page=2)