Upgrade to 0.97.0 from 0.93.1 caused the following issue. I was able to upgrade and it worked the first time. But since I restarted Homeassistant, I keep getting segmentation fault. Please help.
pi@hassbian:~ $ halog
-- Logs begin at Fri 2019-08-23 10:03:01 CDT. --
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setting up lovelace
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds.
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setting up updater
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (SyncWorker_4) [homeassistant.loader] Loaded hikvision from homeassistant.components.hikvision
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setting up group
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.0 seconds.
Aug 23 10:03:31 hassbian hass[508]: 2019-08-23 10:03:31 INFO (MainThread) [homeassistant.setup] Setting up discovery
Aug 23 10:03:32 hassbian systemd[1]: [email protected]: Main process exited, code=killed, status=11/SEGV
Aug 23 10:03:32 hassbian systemd[1]: [email protected]: Unit entered failed state.
Aug 23 10:03:32 hassbian systemd[1]: [email protected]: Failed with result 'signal'.
What platform are you running HA on.
Your Systemd service file is causing your problem. Can you start HA manually. If so check the contents of your Systemd file and edit out the offending section.
I am running on RPi 3B+.
I did a fresh install of 0.97.0 and did multiple system restarts and HA restarts and its responding well. So looks like one of the components crapped out on me when moving from 0.93.1 to 0.97.0.
I am slowly enabling each component to see which one created an issue.
Will update soon.
Till now what I have seen is, if the issue comes once, it never goes away. I couldnt locate the culprit configuration but lately when I enabled cover component, the issue started. So I am rebuilding again! and will avoid putting that component in and try everything else.
@ConcordGE I looked through systemd folder and couldnt really find any issue. Can you guide me what I am looking for?
Looking at similar issue across this forum I have not seen a proper solution other than installing another HA version. It would be great if core devs can chip in to this issue and provide their insight.
Following is my configuration.yaml file.
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Konnected.yaml entry
konnected: !include konnected.yaml
# Set up notifications
notify: !include pushbullet.yaml
camera: !include camera.yaml
binary_sensor: !include binary_sensor.yaml
alert: !include alert.yaml
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
My process to install the new HA version:
1 - Login as pi user
2 - Remove all files in HA home directory:
sudo rm -rf <HA-home>/* <HA-home>/.*
3 - Remove HA virtual env
sudo rm -rf /srv/homeassistant
4 - Create HA directory
sudo mkdir /srv/homeassistant
5 - Change homeassistant directory permission to HA user
sudo chown -R homeassistant:homeassistant /srv/homeassistant
6 - Switch to HA user
sudo -u homeassistant -H -s
7 - Create HA virtual env
python3 -m venv /srv/homeassistant
8 - Activate HA virtual env
source /srv/homeassistant/bin/activate
9 - Upgrade pip
pip install --upgrade pip
10 - Install HA 0.97.0
pip3 install homeassistant==0.97.0
11 - exit and reboot
exit
sudo reboot
You didn’t mention if you can start HA manually
Yes I can, but it fails almost immediately.
Current status:
I have enabled all the components EXCEPT cover and everything is working fine. I can almost guarantee it is cover component that is breaking the hassbian virtual environment.
Cover worked in 0.93.1 but seem to break 0.97.0.
All you can do is check for breaking issues in between each release now that you have narrowed down the offending component.
Yes, I’ll do that . thanks.