Node- red not staring after update 14.6.1 #1701
Comments
|
Confirming also having this issue. Image ghcr.io/hassio-addons/node-red/aarch64:14.6.1 does not exist for addon_a0d7b954_nodered Restored backup to 14.5.0 has fixed the issue. Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Confirming same issue. Failed to start add-on |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
Think i worked it out :) for those with the same question....., go to System > Backups > Tick the node red 14.5.0 back up, click into it >> tick the node red items and hit restore :) |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I had the same problem and by uninstalling and reinstalling the node-red add-on, it was fixed. I didn't need to save the code but I recommend backing it up, to be save. I have mine in a repository. |
|
For me, it also worked to uninstall and install node red. I did do a backup and restored that afterwards. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
ℹ️ What is going on here?
This is an issue with Home Assistant itself (or the Docker environment running underneath it). https://ghcr.io/hassio-addons/node-red/aarch64:14.6.1
As you can see, it had 13K downloads already... It most definitely exists 😄 As a matter of fact, I do test each aarch and amd64 build before shipping it to you. Cool Frenck, but how do I fix this?Some of you seems to tried a re-install, which indeed works for such cases. But might be a bit too much of an effort 😬. Home Assistant has a "fix" command that checks all add-ons, core, and what not, to ensure everything is working as expected. Run the following command from an available (web) terminal or SSH session:
Get yourself coffee, and by the time you're back at your desk, it should all be sorted. Thanks, but please don't do this again!I wish I could do anything about this. This problem is occurring outside of the add-on scope. From this end, there is nothing I can do. Sorry 😢 This issue can happen with any add-on, at any time. For Node-RED, it is one of the popular add-ons, so it just happens that more people run into things like this. But percentage-wise, it is pretty much the same compared to others. Why did you hide all these comments in this issue?I've hidden all "I have the same issue" kinda comments, or comment that are unrelated to issue triaging like... I did restore a backup! Cool, but that doesn't solve stuff or help with solving stuff. Finding an issue on a GitHub issue tracker that matches your problem is kinda nice: At least you know you are not alone. So, let's leave a commit with: "Yeah, I have the same issue", or "+1!!!". 🚫 No! Please do not create "I have the same issue" comments. Ever. Not just this issue or this project, but anywhere on GitHub or any issue tracker on the internet even. It doesn't add to triaging the issue. It only generates noise when reading / triaging the case. Instead, go to the top of the issue, and add a 👍 emoji reaction. That way, we can still see that you (and how many others) experience this issue while keeping the issue threads nice and clean. Thanks! ❤️ ../Frenck |
|
Hm, this seems a Supervisor issue indeed. It looks as if the download of the new Node RED version somehow did not complete/failed, and Supervisor tried to start nonetheless. Can someone create an issue in the Supervisor repository along with the complete Supervisor logs when this happened? Thanks! |
This comment has been minimized.
This comment has been minimized.
|
@atmurray that is not something I can do with the node-red add-on, hence marked offtopic. Feel free to provide information as request above or raise an feature request at the Home Assistant project. |
|
There is actually a Supervisor issue handling the "Image .. does not exist" problem, please refer to home-assistant/supervisor#4610. If someone just happens to come across, please attach the complete log as requested in home-assistant/supervisor#4610 (comment). |
|
My solution was: After updating NodeRed, I also had the described problem. From the backups I restored the state of NodeRed before the update and ran the update again. After that everything was fine and NodeRed works in version 14.6.1 Peter |
|
I am still getting the error after running "supervisor repair". It appears that NodeRed does start. but the logging stops within the console of the add-on.... It is not processing any triggers.. I am rolling back to previous. 2023-10-09 16:22:18.148 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/a0d7b954_nodered/stats - 404 Client Error for http+docker://localhost/v1.42/containers/addon_a0d7b954_nodered/json: Not Found ("No such container: addon_a0d7b954_nodered") Node Red Logs: s6-rc: info: service s6rc-oneshot-runner: starting
|
|
up to date, audited 395 packages in 2s
it is the same error? someone fix it? |
Using the command worked for me. Thx Frenck for your excellent work. Bas |
|
I run HAOS on bare metal and hard-rebooting my system resolved this issue for me when nothing else would. |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
and others
Problem/Motivation
My HAS updated to the new node red 14.6.1 Node-red is to working anymore
Expected behavior
program to start
Actual behavior
program not starting giving the following message
" Image ghcr.io/hassio-addons/node-red/aarch64:14.6.1 does not exist for addon_a0d7b954_nodered"
Steps to reproduce
Proposed changes
The text was updated successfully, but these errors were encountered: