# Unable to start node-red on boot on a Raspberry pi 4

**URL:** <https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838>\
**Category:** General\
**Created:** [21 August 2020 14:12 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838 "2020-08-21T14:12:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vongomben](https://avatars.discourse-cdn.com/v4/letter/v/a4c791/32.png) [@vongomben](https://discourse.nodered.org/u/vongomben)\
**Post date:** [21 August 2020 14:12 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838/1 "2020-08-21T14:12:49Z")

</div>

Hi forum.  
Not sure whether this is hardware-related, but I'm not able to see my node-red run on boot all the times i boot it. It dows a good 50% of times (I'm afraid too unreliable).

I'm on the latest raspby OS and on Raspberry pi 4.  
Based on [this thread](https://discourse.nodered.org/t/unable-to-start-node-red-upon-boot/17353/15), I did:

run

> pi@raspberrypi:~$ sudo systemctl status nodered.service

```auto
● nodered.service - Node-RED graphical event wiring tool
   Loaded: loaded (/lib/systemd/system/nodered.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Fri 2020-08-21 15:59:37 CEST; 10min ago
     Docs: http://nodered.org/docs/hardware/raspberrypi.html
  Process: 357 ExecStart=/usr/bin/env node-red-pi $NODE_OPTIONS $NODE_RED_OPTIONS (code=killed, signal=INT)
 Main PID: 357 (code=killed, signal=INT)

Aug 21 15:59:36 raspberrypi systemd[1]: Started Node-RED graphical event wiring tool.
Aug 21 15:59:37 raspberrypi systemd[1]: nodered.service: Main process exited, code=killed, status=2/INT
Aug 21 15:59:37 raspberrypi systemd[1]: nodered.service: Succeeded.

```

if I run

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

Started Node-RED graphical event wiring tool.
nodered.service: Main process exited, code=killed, status=2/INT
nodered.service: Succeeded.

```

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

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.8.111: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.
21 Aug 16:11:43 - [info]
Welcome to Node-RED
===================
21 Aug 16:11:43 - [info] Node-RED version: v1.0.6
21 Aug 16:11:43 - [info] Node.js version: v10.21.0
21 Aug 16:11:43 - [info] Linux 5.4.51-v7l+ arm LE
21 Aug 16:11:45 - [info] Loading palette nodes
21 Aug 16:11:48 - [info] +-----------------------------------------------------
21 Aug 16:11:48 - [info] | uibuilder initialised:
21 Aug 16:11:48 - [info] | root folder: /home/pi/.node-red/uibuilder
21 Aug 16:11:48 - [info] | version . .: 2.0.8
21 Aug 16:11:48 - [info] | packages . : vue,bootstrap,bootstrap-vue,socket.io
21 Aug 16:11:48 - [info] +-----------------------------------------------------
21 Aug 16:11:49 - [info] Settings file : /home/pi/.node-red/settings.js
21 Aug 16:11:49 - [info] Context store : 'default' [module=memory]
21 Aug 16:11:49 - [info] User directory : /home/pi/.node-red
21 Aug 16:11:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
21 Aug 16:11:49 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
21 Aug 16:11:49 - [info] Server now running at http://127.0.0.1:1880/
21 Aug 16:11:49 - [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.
---------------------------------------------------------------------
21 Aug 16:11:49 - [info] Starting flows
      pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /home/pi/.node-red/node_modules/node-red-node-pi-neopixel/neopix.py 8 40 pixels 100 true
pam_unix(sudo:session): session opened for user root by (uid=0)
21 Aug 16:11:49 - [info] Started flows
      pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /home/pi/.node-red/node_modules/node-red-node-pi-neopixel/neopix.py 8 40 pixels 100 true
pam_unix(sudo:session): session opened for user root by (uid=0)

```

Any help appreciated

---

<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:** [21 August 2020 14:55 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838/2 "2020-08-21T14:55:09Z")

</div>

Have a look in /var/log/syslog at the time 15:59 and see if there is any other information. Probably it is trying to run before something that your node red needs has become available.

---

<div class="post-metadata">

**Author:** ![vongomben](https://avatars.discourse-cdn.com/v4/letter/v/a4c791/32.png) [@vongomben](https://discourse.nodered.org/u/vongomben)\
**Post date:** [21 August 2020 15:06 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838/3 "2020-08-21T15:06:54Z")

</div>

this is what is around that time on var/log/syslog

```auto
Aug 21 02:13:15 raspberrypi rngd[364]: stats: Entropy starvations: 0
Aug 21 02:13:15 raspberrypi rngd[364]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Aug 21 02:17:01 raspberrypi CRON[3881]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 21 02:51:35 raspberrypi dhcpcd[881]: eth1: fe80::210:20ff:fe30:4050 is reachable again
Aug 21 03:13:15 raspberrypi rngd[364]: stats: bits received from HRNG source: 360064
Aug 21 03:13:15 raspberrypi rngd[364]: stats: bits sent to kernel pool: 304096
Aug 21 03:13:15 raspberrypi rngd[364]: stats: entropy added to kernel pool: 304096
Aug 21 03:13:15 raspberrypi rngd[364]: stats: FIPS 140-2 successes: 18

```

---

<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:** [21 August 2020 15:17 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838/4 "2020-08-21T15:17:10Z")

</div>

That is 03:13 not 15:59, which is when it failed

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 October 2020 15:17 UTC](https://discourse.nodered.org/t/unable-to-start-node-red-on-boot-on-a-raspberry-pi-4/31838/5 "2020-10-20T15:17:20Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.