Node-red add-on not running

Third party integrations Node-RED
21

After the update I did on Home, Node also had this problem, does anyone know of a solution?

Node-RED LOG

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 2
You are running the latest version of this add-on.
System: Home Assistant OS 10.0 (amd64 / generic-x86-64)
Home Assistant Core: 2023.4.5
Home Assistant Supervisor: 2023.04.0

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] customizations.sh: executing…
[cont-init.d] customizations.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing…
patch: **** out of memory
[cont-init.d] node-red.sh: exited 2.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…

            Oops! Something went wrong.

We are so sorry, but something went terribly wrong when
starting or running this add-on.

Be sure to check the log above, line by line, for hints.

[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

22

Could you find a solution?

23

Hi Home Assistant Node-Red Users,

It’s disappointing to me that Node-Red is such a problem child. I been having had the same problem as other users for some time now with recent and not so recent versions of the Node-Red add-on. For an add-on that offers so much, it has lost all of its shine for me. Looking at the above posts it appears that nobody has found “the” fix for the “Node-red add-on not running” post.

Over a number of years I have developed a many nodes, Java scripts, HA sensors, and mqtt links to HA sensors doing lots of critical stuff for me. For no apparent reason Node-Red has quietly stopped at no particular time. Right now Node-Red is good as dead.

I’ve been trying lots of things to bring it back to life. Tried Chrome, no good. Unwound back to ver 14.3.0, no good. Updated again to current version: 14.5.0, no good. Recently while trying to access Node-Red after a restart I got a banner " 504 Gateway Time-out" with a small font ‘nginx’ at the bottom of the banner. The last three entries in the add-on log were:

24 Sep 19:43:25 - [info] Starting flows
[19:43:25] INFO: Starting NGinx...
24 Sep 19:43:26 - [info] Started flows
24 Sep 19:43:26 - [info] [mqtt-broker:MQTT HomeAssistRPi2] Connected to broker: mqtt://192.168.4.109:1883

Prior to Node_Red failure the function nodes and flows appear to be functioning normally. I have a green dot in the top right of the Node-Red add-on Info tab indicating its running. From the log it looks to me like NGinx hasn’t started properly (there is no log entry saying it has started), but I’m not sure how to find out. I don’t know if I have a problem in one of the nodes or Java scripts.

Most recently an issue has been logged on starting Node-Red.

2023/09/25 19:05:21 [error] 443#443: *11 upstream timed out (110: Operation timed out) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:46836/", host: "192.168.4.109:8123". I don't know what client 172.30.32.2 does and what went wrong with its connection.

So what now? I am at a loss to know where to next. Is this problem unique to HA or is it common to other home automation systems (e.g. OpenHab)? Is anyone in HA’s development team able to cast light on this?

24

I had the same problem - set up config as above and it worked, but now it’s fallen over again. I have ‘Error loading settings file /etc/node-red/config.js’ though I’ve not changed anything from when it was running… (FYI I did have it running on my open energy monitor system before getting HA - it still works fine on that)

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 14.6.3
You are running the latest version of this add-on.
System: Home Assistant OS 11.1 (aarch64 / odroid-n2)
Home Assistant Core: 2023.10.5
Home Assistant Supervisor: 2023.10.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

up to date, audited 184 packages in 5s

7 packages are looking for funding
run npm fund for details

8 moderate severity vulnerabilities

To address issues that do not require attention, run:
npm audit fix

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[03:55:32] INFO: Starting Node-RED…

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

Error loading settings file: /etc/node-red/config.js
/config/node-red/settings.js:198
default: {
^^^^^^^

SyntaxError: Unexpected token ‘default’
at internalCompileFunction (node:internal/vm:73:18)
at wrapSafe (node:internal/modules/cjs/loader:1178:20)
at Module._compile (node:internal/modules/cjs/loader:1220:27)
at Module._extensions…js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:119:18)
at Object. (/etc/node-red/config.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
[03:55:33] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[03:55:33] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

25

my log is here:

no starting up. Already deleted nodered add on and reinstalled it. not working anymore:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 15.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 11.1 (amd64 / generic-x86-64)
Home Assistant Core: 2023.11.1
Home Assistant Supervisor: 2023.10.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

26

found it, i changed the config " safe_mode" true , then i founhd the problem flows and restarted with safe mode false

27

I disabled “ssl” under “Configuration” of Node-RED and it started working.