Service is killed when restart GUI

#1

Guys, since version 2022.x when I restart home assistant inside gui the whole process is killed giving the error:

Feb 16 15:34:44 Raspberrypi4 hass[1055]: 2022-02-16 15:34:44 WARNING (MainThread) [homeassistant.core] Timed out waiting for shutdown stage 1 to complete, the shutdown will continue
Feb 16 15:35:44 Raspberrypi4 hass[1055]: 2022-02-16 15:35:44 WARNING (MainThread) [homeassistant.core] Timed out waiting for shutdown stage 2 to complete, the shutdown will continue
Feb 16 15:36:14 Raspberrypi4 hass[1055]: 2022-02-16 15:36:14 WARNING (MainThread) [homeassistant.core] Timed out waiting for shutdown stage 3 to complete, the shutdown will continue
Feb 16 15:36:16 Raspberrypi4 systemd[1]: [email protected]: Main process exited, code=exited, status=100/n/a
Feb 16 15:36:16 Raspberrypi4 systemd[1]: [email protected]: Failed with result ‘exit-code’.
Feb 16 15:36:16 Raspberrypi4 systemd[1]: [email protected]: Consumed 4h 30min 48.115s CPU time.

But if I do a server restart “systemctl restart [email protected]” home assistant is restarted without any issue.

Any clues?

#2

Hi, same here.
I can restart from GUI in Version 2021.12.9 but doing the same thing in Version 2022.2.9 the software does not come back showing the following error:
● [email protected] - Home Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-02-20 08:50:18 CET; 1s ago
Process: 21666 ExecStart=/srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant (code=exited, status=100)
Main PID: 21666 (code=exited, status=100)

Here an Picture from yesterday:

grafik
grafik1588×373 51.4 KB

Doing sudo systemctl restart [email protected] from console works.

#3

Good to see that I am not the only one.

I think it will be a good idea to open a ticket to git

#4

Hi, this worked for me Autostart using systemd

1 Like
#5

Here the ticket I opened to get help https://github.com/home-assistant/core/issues/66923

1 Like
#6

Thanks my friend.
This solved the issue for me too.