You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 callingterminate()
from the former HA disconnect.You can easily identify this by adding a log entry for
initialize()
andterminate()
.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
The text was updated successfully, but these errors were encountered: