Node-RED crashed, halting add-on

Problem/Motivation

For a few days now I have problems with node-red. Everything is up to date with the latest version but now the addon is always giving an error and shuts down without me knowing what it is.

I didn’t make any changes to node-red, I just made updates.

thanks

`s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/00-banner.sh

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

Add-on version: 13.2.0 You are running the latest version of this add-on. System: Debian GNU/Linux 11 (bullseye) (amd64 / qemux86-64) Home Assistant Core: 2022.7.7 Home Assistant Supervisor: 2022.07.0

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

cont-init: info: /etc/cont-init.d/00-banner.sh exited 0 cont-init: info: running /etc/cont-init.d/01-log-level.sh cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0 cont-init: info: running /etc/cont-init.d/customizations.sh cont-init: info: /etc/cont-init.d/customizations.sh exited 0 cont-init: info: running /etc/cont-init.d/nginx.sh cont-init: info: /etc/cont-init.d/nginx.sh exited 0 cont-init: info: running /etc/cont-init.d/node-red.sh patching file nodes/ui_base.html Hunk #1 succeeded at 1164 (offset 633 lines). up to date, audited 151 packages in 1s 34 packages are looking for funding run npm fund for details found 0 vulnerabilities cont-init: info: /etc/cont-init.d/node-red.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun nginx (no readiness notification) services-up: info: copying legacy longrun nodered (no readiness notification) s6-rc: info: service legacy-services successfully started [23:23:16] INFO: Starting Node-RED…

start node $NODE_OPTIONS node_modules/node-red/red.js “–settings” “/etc/node-red/config.js” 27 Jul 23:23:17 - [info] Welcome to Node-RED =================== 27 Jul 23:23:17 - [info] Node-RED version: v3.0.1 27 Jul 23:23:17 - [info] Node.js version: v16.16.0 27 Jul 23:23:17 - [info] Linux 5.10.0-9-amd64 x64 LE 27 Jul 23:23:18 - [info] Loading palette nodes 27 Jul 23:23:21 - [info] Dashboard version 3.1.7 started at /endpoint/ui 27 Jul 23:23:21 - [info] Settings file : /etc/node-red/config.js 27 Jul 23:23:21 - [info] Context store : ‘default’ [module=memory] 27 Jul 23:23:21 - [info] User directory : /config/node-red/ 27 Jul 23:23:21 - [warn] Projects disabled : editorTheme.projects.enabled=false 27 Jul 23:23:21 - [info] Flows file : /config/node-red/flows.json 27 Jul 23:23:21 - [info] Server now running at http://127.0.0.1:/ 27 Jul 23:23:22 - [info] Starting flows [23:23:22] INFO: Starting NGinx… 27 Jul 23:23:23 - [info] [cronplus:c.] createTask - index: 0, static: true, opt: {“name”:“schedule1”,“topic”:“schedule1”,“payloadType”:“default”,“payload”:“”,“expressionType”:“cron”,“expression”:"0 * * * “,“location”:”",“offset”:“0”,“solarType”:“all”,“solarEvents”:“sunrise,sunset”} 27 Jul 23:23:23 - [info] Started flows 27 Jul 23:23:23 - [info] [mqtt-broker:.] Connected to broker: mqtt://*:1883 27 Jul 23:23:27 - [info] [server:Home Assistant] Connecting to http://supervisor/core 27 Jul 23:23:27 - [info] [server:Home Assistant] Connected to http://supervisor/core Received state update for unknown entity sensor.template_sidebar Received event for unknown subscription 3. Unsubscribing. Received event for unknown subscription 3. Unsubscribing. Received event for unknown subscription 3. Unsubscribing. Received event for unknown subscription 3. Unsubscribing. 27 Jul 23:24:00 - [red] Uncaught Exception: 27 Jul 23:24:00 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason “#<Object>”. [23:24:00] WARNING: Node-RED crashed, halting add-on s6-rc: info: service legacy-services: stopping [23:24:00] INFO: Node-RED stoped, restarting… [23:24:00] INFO: Node-RED stoped, restarting… s6-svwait: fatal: supervisor died s6-rc: info: service legacy-services 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 fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

[miraixyz]

I am having the same issue with Node Red v.13.2. Seems to have started every since I upgraded to 2022.8.x. Every time I restart HA or after random period of time, the addon crashes, and all of my flows stop. I usually reload the integration and restart the web UI to get it working again, but this is getting to a bit annoying now. Not using any experimental nodes that I know of, and everything seems to be up-to-date. Hope we can get a resolution soon!

[github-actions[bot]]

There hasn’t been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!