search

hassio-addons / addon-node-red

Node-RED - Home Assistant Community Add-ons
https://addons.community
MIT License
516 stars 118 forks source link

Node-Red broke after HASS operating system update #1554

Closed Ewoodster closed 1 year ago

Ewoodster commented 1 year ago

Problem/Motivation

Node-red won't start after Home Assistant operating system update. Even loading a back-up or reinstalling won't get it to work.

Expected behavior

Normal operation

Actual behavior

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.0.2 You are running the latest version of this add-on. System: Home Assistant OS 9.5 (aarch64 / raspberrypi4-64) Home Assistant Core: 2023.1.7 Home Assistant Supervisor: 2023.01.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 patching file nodes/ui_base.html Hunk #1 succeeded at 1164 (offset 633 lines). s6-rc: info: service init-nginx successfully started up to date, audited 3 packages in 2s found 0 vulnerabilities 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 [14:20:04] 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 [14:20:08] INFO: Service Node-RED exited with code 0 (by signal 0) [14:20:09] 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 [14:20:13] INFO: Service Node-RED exited with code 0 (by signal 0) [14:20:14] 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 [14:20:18] INFO: Service Node-RED exited with code 0 (by signal 0) [14:20:20] INFO: Starting Node-RED...

from here on it is stuck in a starting loop. Error message: Error loading settings file: /etc/node-red/config.js. I tried to manually copy the config.js into the folder /etc/node-red/ (didn't exist), but this didn't help either.

tabiznet commented 1 year ago

I'm having the exact same issue with a fresh install of ha

fogren commented 1 year ago

I'm also having the same problem with an updated Node Red on an updated Home assistant operating system running on an Rpi4.

Ewoodster commented 1 year ago

Hello,

is anyone looking into this? Seems like I am not the only one with this issue.

kohai-ut commented 1 year ago

I just went through a similar issue. I found the following.... I could not get Node Red to start in Home Assistant. I would get a 502 Bad Gateway if I clicked on the Node Red in HA. I found if I used the RESET config in Add-ons -> Node Red -> configuration tab (save your secret and paste it back in plus other settings you may want) that it would reset the add on nodes and they disappeared. Now I could get into Node Red in HA and it would complain the add-ons were missing. The 502 bad gateway will show up for about the first 20-30 seconds of starting so wait and then try to get in. THEN, once in Node Red, click in the top right menu and choose Manage Palette. In here, you can try to install nodes.

However, I found I was getting network errors according to the View Log in Node Red (also in the top right menu in NR). It seems the HA upgrade (?) enabled an IPv6 interface. In HA, go to settings and networking and disable the IP6 interface. I did a lot of upgrades today to my network, my HA, my node red, etc, so I'm not exactly sure which thing made all this bad stuff happen.

Ewoodster commented 1 year ago

Hi @kohai-ut,

thanks for your help. Unfortunately in my case, the error isn't network related. For almost three weeks now I can't start Node-Red. All of my automations are in there, so basically my house is dumb now. There is no way to get it running again. No reset, no fresh install, nothing...

Ewoodster commented 1 year ago

I was hopeful that the Version 14.0.3 would be working again, but unfortunately it still doesn't.

Ewoodster commented 1 year ago

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.0.3 You are running the latest version of this add-on. System: Home Assistant OS 9.5 (aarch64 / raspberrypi4-64) Home Assistant Core: 2023.3.0 Home Assistant Supervisor: 2023.01.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 patching file nodes/ui_base.html Hunk #1 succeeded at 1164 (offset 633 lines). s6-rc: info: service init-nginx successfully started up to date, audited 3 packages in 1s found 0 vulnerabilities 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 [10:39:06] 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 [10:39:10] INFO: Service Node-RED exited with code 0 (by signal 0) [10:39:11] 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 [10:39:15] INFO: Service Node-RED exited with code 0 (by signal 0) [10:39:16] 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 [10:39:20] INFO: Service Node-RED exited with code 0 (by signal 0)

Old core update broke my Node-Red, new core Update didn't fix it.

github-actions[bot] commented 1 year ago

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!