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

AD docker: terminate() gets triggered on HA startup like after reboot but not on disconnect. #2098

Open
mmattel opened this issue Sep 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@mmattel
Copy link

mmattel commented Sep 25, 2024

What happened?

References: #2016 (Shut down / restart appdaemon does not terminate in correct order)

When having AD as container (not running integrated in HA) and you reboot HA, you get the disconnect and reconnect messages and AD restarts all apps. Note that terminate() is NOT called.

If you are using the terminate() function to trigger a clean app shutdown, this function gets called AFTER HA has started and with that AFTER the apps just have started. Means, apps start because of AD reconnect and get immediately terminated afterwards because of calling terminate() from the former HA disconnect.

You can easily identify this by adding a log entry for initialize() and terminate().

Version

4.4.2

Installation type

Docker container

Relevant log output

No response

Relevant code in the app or config file that caused the issue

No response

Anything else?

No response

@mmattel mmattel added the bug Something isn't working label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant