Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodered is crashing daily #1669

Open
Jens-Wymeersch opened this issue Oct 27, 2024 · 2 comments
Open

Nodered is crashing daily #1669

Jens-Wymeersch opened this issue Oct 27, 2024 · 2 comments

Comments

@Jens-Wymeersch
Copy link

Jens-Wymeersch commented Oct 27, 2024

Describe the bug

Basically I've been extremely happy with the NR addon within homeassistant.
It started a few weeks ago when I couldn't access NR within HA anymore - this is still the case.
However since a few days, I've been experiencing a lot of trouble with the addon.
Sometimes it goes down - even with restarting the addon it doesn't come up again. Only when I restart homeassistant, I get it going again.

To Reproduce

No response

Expected behavior

No response

Screenshots

No response

Example Flow

No response

Environment Information

Homeassistant 2024.10.4
Supervisor 2024.10.3
Operating System 13.2
NR v4.0.3 - latest addon available in home assistant
Using the NR companion integration

Additional context

Relevant logs:

27 Oct 16:14:24 - [info] [server:Home Assistant Main] Connecting to http://supervisor/core
27 Oct 16:14:24 - [info] [server:Home Assistant Main] Connected to http://supervisor/core
[16:14:24] INFO: Service Node-RED exited with code 256 (by signal 9)

It stays into a loop and doesn't stop.

@zachowj
Copy link
Owner

zachowj commented Oct 28, 2024

This error is often caused by a memory issue, such as a memory leak in one of your flows or a runaway flow consuming all available memory. You can try disabling flows to help identify which one might be causing the problem.

@Jens-Wymeersch
Copy link
Author

Thank you for the suggestion. I'll look into it. Anything I should be looking for specifically ? It only started happening after the latest add-on release.
Is there a way to add more resources from HA to the add on ? Or would a separate instance of NR on docker be a better solution ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants