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

CTRL+C to stop hass does not work anymore #2136

Closed
Nutti85 opened this issue May 22, 2016 · 5 comments
Closed

CTRL+C to stop hass does not work anymore #2136

Nutti85 opened this issue May 22, 2016 · 5 comments

Comments

@Nutti85
Copy link

Nutti85 commented May 22, 2016

Home Assistant release:
0.20

Python release:
3.4.2

Description of problem:
CTRL+C does not work running on Pi2 loaded with Jessie. Stopped working after I updated hass to 0.20

Additional info:
I've seen other report this as well.

@balloob
Copy link
Member

balloob commented May 22, 2016

So what happens instead?

On Sun, May 22, 2016, 14:39 Nutti85 [email protected] wrote:

Home Assistant release (hass --version):
0.20

Python release (python3 --version):
3.4.2

Description of problem:
CTRL+C does not work running on Pi2 loaded with Jessie. Stopped working
after I updated hass to 0.20

Additional info:
I've seen other report this as well.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#2136

@jaharkes
Copy link
Contributor

The only platform where I expect ^C to possibly have an issue is on Windows where we still have a 2 process setup to handle restarts, with the 9-line daemon runner using subprocess. I assume subprocess will handle properly passing interrupts to child processes.

As far as any other, it should be just as reliable (or flaky) as it was with the 2 process setup because there the parent would simply catch the interrupt and forward it to the child, and now we just took that parent process out of the loop. There may be situations where third party modules are blocking on DNS or socket connections, I've noticed after network discovery my hass process tries to connect to one or two uPNP services that responded to the multicast query over IPv6 but are not actually accessible using IPv6 so the process blocks and times out after a bit.

I tried to ping you this morning on gitter.im to get more info, you must have missed my message.

Works for me. When I hit ^C I see

^CINFO:homeassistant.core:Stopping
INFO:homeassistant.core:Bus:Handling <Event homeassistant_stop[L]>
INFO:homeassistant.components.recorder:Closing database

The first two lines are pretty much immediate, the last one takes a couple of seconds.
what is the system you are trying to run on? Windows?

@Nutti85
Copy link
Author

Nutti85 commented May 23, 2016

@balloob Nothing happens. Hass just runs as normal. I tried several times and waited several minutes but nothing happes. Might not be a problem with hass but it happened after the 0.20 update ..so yeah...

@happyleavesaoc
Copy link
Contributor

I have this problem as well.

@jaharkes
Copy link
Contributor

Fixed in 0.20.2

@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants