I’ve recently upgraded to Home Assistant 0.102.3 and at the same time I upgraded my Python version to 3.7 (from 3.6). As part of the upgrade I also needed to change to the mobile_app for my iOS devices.
As a result, I’m finding my instance crashes at least once a day with the following:
hass[5021]: 2019-12-06 11:27:30 ERROR (MainThread) [homeassistant.helpers.condition] Error during template condition: Undefined
hass[5021]: 2019-12-06 11:27:30 ERROR (MainThread) [homeassistant.helpers.condition] Error during template condition: Undefined
hass[5021]: 2019-12-06 11:27:30 ERROR (MainThread) [homeassistant.helpers.condition] Error during template condition: Undefined systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV systemd[1]: [email protected]: Failed with result ‘signal’.
I’ve looked through the logs and can’t find any offending component or stray config, and have read through the documents and haven’t really been able to find anything else that may have broken this (apart from maybe the Python upgrade?)
I was wondering if anyone else has this issue, or if anyone may be able to shed some light on why this might be happening?
I’m running on a NUC, on Ubuntu 18.04 (in Proxmox container). I’ve also tried to disable components one by one, however the only addition since the upgrade was the mobile_app: component as per the recent article on how to enable this component. I can manually start HA, and it’ll work for a while but after some time (sometimes same day, sometimes next day) it will crash with the above error.
Thanks in advance!
Those errors are from my battery_level templates which would be a different issue - I’ve had these errors since years ago when I first put the templates in and agree, they do flood my logs so I should really fix them…
I don’t believe they would be causing the more recent crashes…
Update: Looks like could be something about how mobile_app connects as I’ve only had SEG faults since using the mobile_app?
Most recent error logs before it fails each time:
2019-12-09 11:16:26 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error in data received
Traceback (most recent call last):
File “/usr/local/lib/python3.7/asyncio/sslproto.py”, line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File “/usr/local/lib/python3.7/asyncio/sslproto.py”, line 207, in feed_ssldata
self._sslobj.unwrap()
File “/usr/local/lib/python3.7/ssl.py”, line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2580)
Dec 09 11:19:45 HAS systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV
Dec 09 11:19:45 HAS systemd[1]: [email protected]: Failed with result ‘signal’.
Hello [cquadalti]! Welcome to the community… maybe provide some logs for the community to have a look at.
I’ve since:
rebuilt my HASS box
reverted back to Python 3.6
Failing the above, I can’t really go back to the old iOS app, and I’ve been stubborn enough to stay on 0.102.3 for now. The rebuild with python 3.6 still had crashing issues, but only after what seemed like a longer uptime. Upgraded Python to 3.7 as a result, and same outcome. Appears the rebuild has just made the issue occur less frequent for now, so it looks like it might just be the mobile_app in conjunction with the combination of components I am running.
I do note that using the mobile_app, I mainly use it to look at my foscam feeds during the day to check up on my pups etc, and that the failures happen after using the mobile_app a few times. The days I don’t actively open the app, it feels like these days I have no crashes…
Will keep logging and looking for a resolution - although I hope no one else has this issue, I’m hoping someone can help table some ideas to fix it…
Still having issues here. I’ve been away for a week and my HASS instance was up the entire time as I was using a web browser to log in - no issues at all.
The issue only occurs when I use the mobile app to connect to my HASS instance, and this is the only error I get:
Dec 30 11:36:00 HASS systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV
Dec 30 11:36:00 HASS systemd[1]: [email protected]: Failed with result 'signal'.
Does anyone else experience this issue? Is there any way to debug what the mobile app could be doing to make my HASS instance crash?