Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Node-red addon not starting after update to 7.2.9

See original GitHub issue

Updated Node-red addon from 7.2.8 to 7.2.9 Now the addon refuse to start.

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: 7.2.9
 You are running the latest version of this add-on.
 System: HassOS 4.16  (amd64 / qemux86-64)
 Home Assistant Core: 0.117.6
 Home Assistant Supervisor: 2020.11.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... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing... 
patching file nodes/ui_base.html
Hunk #1 FAILED at 531.
1 out of 1 hunk FAILED -- saving rejects to file nodes/ui_base.html.rej
[cont-init.d] node-red.sh: exited 1.
[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.

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:14 (3 by maintainers)

Top GitHub Comments

10reactions

frenckcommented, Nov 18, 2020

The issue has been located, fix made. Awaiting development builds now…

6reactions

frenckcommented, Nov 18, 2020

Fixed in:

⬆️ Node-RED v7.2.10

https://github.com/hassio-addons/addon-node-red/releases/tag/v7.2.10

Edit: The release is now available. If you don’t see the upgrade yet, please reload/refresh the add-on store. Go to the add-on store, click on the 3 dots menu in the top left and reload it. Next, refresh/reload your browser page and the upgrade should show up immediately.

Top Results From Across the Web

HOLD YOUR UPDATE! 7.2.9 node-red not starting! MAJOR ...

9 You are running the latest version of this add-on. System: HassOS 4.16 (amd64 / qemux86-64) Home Assistant Core: 0.117.6 Home Assistant ...

Running Node-RED locally

If you are using Windows, do not start the command with sudo . That command will install Node-RED as a global module along...

NGinx attempting to load when flows startup - I don't use ...

I am using Node Red in conjunction with "Home Assistant." To isolate the problem I did a 100% minimalist rebuild installing only Home...

Node-red doesn't start - General

I start node-red but i have this error and the web interface is not loading nothing. How can I fix this?

After upgrade UI stops working - General - Node-RED Forum

Mar 8 09:59:31 server systemd[1]: node-red.service: Scheduled restart job, restart counter is at 34. Is this most probably a plugin problem and should...