8000 Installation of pywebpush takes very long, HASS entered failed state · Issue #3599 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Installation of pywebpush takes very long, HASS entered failed state #3599

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.

Sign up for GitHub

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

Jump to bottom
Closed
Atrejoe opened this issue Sep 29, 2016 · 13 comments
Closed

Installation of pywebpush takes very long, HASS entered failed state #3599

Atrejoe opened this issue Sep 29, 2016 · 13 comments

Comments

@Atrejoe
Copy link
Atrejoe commented Sep 29, 2016

Home Assistant release (hass --version):
0.29.3

Python release (python3 --version):
2.7.9

Component/platform:
pywebpush

Description of problem:
After upgrade, upon first start, installation of pywebpush takes forever.

Additional info:
I have installed HASS as autostarting as instructed on:
https://home-assistant.io/getting-started/autostart-systemd/

HASS is started after upgrade manually by:
sudo systemctl start home-assistant@[myuser]

Output (obtained by sudo journalctl -p debug -f -u home-assistant@[myuser]):

...
Sep 29 19:21:40 raspberrypi hass[15723]: INFO:homeassistant.util.package:Attempting install of https://github.com/web-push-libs/pywebpush/archive/e743dc92558fc62178d255c0018920d74fa778ed.zip#pywebpush==0.5.0

Which takes a long time, without giving any feedback. I then stopped HASS, and installed pywebpush manually, by using:

sudo pip3 install pywebpush

Which also took a long time (hour or so). I then started HASS, hoping that my requirement would have been met, but unfortunately currently the log indicates an attampt to install pywebpush using the github url again.

After waiting some time I get a notification that HASS is up, but the web ui is unresponsive (ERR_CONNECTION_REFUSED) and the log shows:

Sep 29 21:12:44 raspberrypi hass[20111]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=3052545424-1>
Sep 29 21:12:44 raspberrypi hass[20111]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=automation.start_notification, new_state=<state automation.start_notification=on; friendly_name=Start notification, last_triggered=2016-09-29T23:12:44.865105+02:00 @ 2016-09-29T23:12:43.328449+02:00>, old_state=<state automation.start_notification=on; friendly_name=Start notification, last_triggered=None @ 2016-09-29T23:12:43.328449+02:00>>
Sep 29 21:12:45 raspberrypi systemd[1]: home-assistant@pi.service: main process exited, code=killed, status=11/SEGV
Sep 29 21:12:45 raspberrypi systemd[1]: Unit home-assistant@pi.service entered failed state.```

I hope to figure this out tomorrow
@Atrejoe
Copy link
Author
Atrejoe commented Sep 29, 2016

After starting HASS again, it suddenly became responsive again :|

@Atrejoe Atrejoe closed this as completed Sep 29, 2016
@Atrejoe
Copy link
Author
Atrejoe commented Sep 30, 2016

HASS has spontaneously eneterd failed state again:

Sep 30 01:02:00 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1279): 192.168.1.139
Sep 30 01:02:00 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting
8000
 new HTTP connection (1): 192.168.1.1
Sep 30 01:02:10 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1280): 192.168.1.139
Sep 30 01:02:12 raspberrypi hass[463]: INFO:homeassistant.components.device_tracker.ddwrt:Checking ARP
Sep 30 01:02:12 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 192.168.1.1
Sep 30 01:02:20 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1281): 192.168.1.139
Sep 30 01:02:24 raspberrypi hass[463]: INFO:homeassistant.components.device_tracker.ddwrt:Checking ARP
Sep 30 01:02:24 raspberrypi hass[463]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 192.168.1.1
Sep 30 01:02:30 raspberrypi systemd[1]: home-assistant@pi.service: main process exited, code=killed, status=11/SEGV
Sep 30 01:02:30 raspberrypi systemd[1]: Unit home-assistant@pi.service entered failed state.

@Atrejoe Atrejoe reopened this Sep 30, 2016
@Atrejoe
Copy link
Author
Atrejoe commented Sep 30, 2016

(This may be two separate issues)

@partofthething
Copy link
Contributor
partofthething commented Sep 30, 2016 •
edited
Loading

I'm seeing the spontaneous kill also on 0.29.4. Has happened 4 times in a row, about 15 minutes after starting hass. I did not have pywebpush issue (so they're probably separate issues).

Main home-assistant log shows nothing of interest before the crash. Last thing that happened was

16-09-29 23:10:06 homeassistant.components.device_tracker.nmap_tracker: nmap scan successful

Syslog shows:

Sep 29 23:10:26 tau avahi-daemon[449]: Received packet from invalid interface.
Sep 29 23:10:30 tau lircd-0.9.0-pre1[481]: removed client
Sep 29 23:10:30 tau rsyslogd-2007: action 'action 17' suspended, next retry is Thu Sep 29 23:12:00 2016 [try http://www.rsyslog.com/e/2007 ]
Sep 29 23:10:30 tau systemd[1]: home-assistant@pi.service: main process exited, code=killed, status=11/SEGV
Sep 29 23:10:30 tau systemd[1]: Unit home-assistant@pi.service entered failed state.

@Atrejoe
Copy link
Author
Atrejoe commented Sep 30, 2016

I'm seeing a lot of messages regarding a locked db too.
For the rest nothing that announces or logs the crash.

@Atrejoe
Copy link
Author
Atrejoe commented Sep 30, 2016

the before-last line seems to indicate a segmentation fault: Sep 30 14:04:12 raspberrypi systemd[1]: home-assistant@pi.service: main process exited, code=killed, status=11/SEGV Sep 30 14:04:12 raspberrypi systemd[1]: Unit home-assistant@pi.service entered failed state.
Could it be that the core rewrite needs some polish?

@partofthething
Copy link
Contributor

Possibly. Yeah I ran it in a console in debug mode for a while and it was working working working for an hour and then BAM! Segfault. I'm on fully-up-to-date Raspberry Pi 2 Jessie.

INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: new_state=<state sensor.cpu_use=8; unit_of_measurement=%, friendly_name=CPU Use, icon=mdi:memory @ 2016-09-30T20:23:30.703582-07:00>, old_state=<state sensor.cpu_use=7; unit_of_measurement=%, friendly_name=CPU Use, icon=mdi:memory @ 2016-09-30T20:23:00.632325-07:00>, entity_id=sensor.cpu_use>
Segmentation fault

@Atrejoe
Copy link
Author
Atrejoe commented Oct 1, 2016

Maybe we should compare oud setups, hardware and used components. I'm running on a Pi 1 B, my components follow

@Atrejoe
Copy link
Author
Atrejoe commented Oct 1, 2016

the issue of the segmentation fault is wel known and addressed here #3453

@partofthething
Copy link
Contributor

You're right. Applying the patch from there works for me. No more crashes so far. Yay. Looks like it just went out as 0.29.6

@ktpx
Copy link
ktpx commented Oct 2, 2016

Long install + fail of pywebpush is known. There's another thread on it..I had the same issue. But then again I've dropped html5 and using simplenotify.io which has less footprint and works much better.

@Spartan-II-117
Copy link
Contributor

Can this issue be closed?

@Atrejoe
Copy link
Author
Atrejoe commented Mar 14, 2017

I haven't seen it in a long time, so I guess so

@Atrejoe Atrejoe closed this as completed Mar 14, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Jul 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Atrejoe @ktpx @Spartan-II-117 @partofthething
0