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

Addon watchdog #318

Open
chrodriguez opened this issue Mar 13, 2024 · 3 comments
Open

Addon watchdog #318

chrodriguez opened this issue Mar 13, 2024 · 3 comments

Comments

@chrodriguez
Copy link

Hello, I've been using this addon for six months and it works great. Sometimes when homeassistant machine restarts, asterisk addon remains stopped. But, I've configured:

image

This watchdog setting makes me go and read Home Assistant add-on configuration, and I've detected that this entry is not configured in asterisk/config.yaml. May be I'm wrong, but it may be helpful to add something like:

watchdog: tcp://[HOST]:5060

Thanks in advance

@felipecrs
Copy link
Collaborator

That's a great idea. Feel free to contribute as a PR. The most difficult part is testing, I suppose.

@TECH7Fox
Copy link
Owner

I don't know why it doesn't say it on the docs already, but the watchdog option is obsolete.

The watchdog option in the GUI (should) simply restarts the add-on when it crashes and stops. No idea why you are having problems though. Do you see any related errors / warnings in the supervisor logs?

@TECH7Fox TECH7Fox closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2024
@felipecrs
Copy link
Collaborator

@TECH7Fox we could still add a HEALTHCHECK though, to detect situations where the add-on is stuck.

Example:

@TECH7Fox TECH7Fox reopened this Jul 10, 2024
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

Successfully merging a pull request may close this issue.

3 participants