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

Regular crashes after recent updates #1987

Open
stefanbode opened this issue Oct 29, 2024 · 3 comments
Open

Regular crashes after recent updates #1987

stefanbode opened this issue Oct 29, 2024 · 3 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@stefanbode
Copy link

stefanbode commented Oct 29, 2024

The last messages before automatic shutdown are following. Currently watchdog mitigate the issue. Anyhow the restart is new to my system

{"type":"result","success":false,"error":{"code":3,"message":"Connection lost"}}
29 Oct 01:01:17 - [red] Uncaught Exception:
29 Oct 01:01:17 - [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 "#".
[01:01:18] INFO: Service Node-RED exited with code 1 (by signal 0)

Happy to help debugging

@zachowj
Copy link
Contributor

zachowj commented Oct 29, 2024

Possibly related to this issue: home-assistant/home-assistant-js-websocket#533

@stefanbode
Copy link
Author

some additional logs after activating watchdog and auto restart:
29 Oct 22:33:11 - [error] [api-call-service:Schliessen] HomeAssistantError
29 Oct 23:09:32 - [error] [api-call-service:Schliessen] HomeAssistantError
29 Oct 23:33:07 - [error] [api-call-service:Schliessen] HomeAssistantError
30 Oct 03:17:35 - [error] [api-call-service:Schliessen] HomeAssistantError
30 Oct 07:51:35 - [error] [api-call-service:Schliessen] HomeAssistantError

Copy link

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!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

2 participants