core: 0.80.x - Python General Protection Error/Crash
Home Assistant release with the issue: 0.80.x (Tested .0 and .2 - Both have issue) Last working Home Assistant release (if known): 0.79.3
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: N/A
Description of problem: General Protection errors and HA crash since update to 0.80.x. Never saw this on any release prior. I did not make any changes to the HA configuration or add any components/features except I did the Google Assistant migration.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
N/A
Traceback (if applicable):
Oct 17 14:53:49 host kernel: [2132473.430583] traps: python[74992] general protection ip:7f2736446529 sp:7ffe926205b0 error:0
Oct 17 14:53:49 host kernel: [2132473.430588] in libc-2.24.so[7f2736412000+195000]
Oct 17 15:15:04 host kernel: [2133748.423099] traps: python[78985] general protection ip:7fefabe19529 sp:7fff63bca400 error:0
Oct 17 15:15:04 host kernel: [2133748.423119] in libc-2.24.so[7fefabde5000+195000]
Additional information:
HA - 0.80.2 :latest docker image
$ sudo docker exec home-assistant python3 -V
Python 3.6.6
No observation of any increased CPU load, memory usage, etc. No logs in HA indicating any errors. Only the syslog messages noted above.
Same exact components loaded as previous 0.79.3 version.
alarm_control_panel
alarm_control_panel.ifttt
apcupsd
api
auth
automation
binary_sensor
binary_sensor.apcupsd
binary_sensor.ffmpeg_noise
binary_sensor.mqtt
binary_sensor.nest
binary_sensor.ping
binary_sensor.template
binary_sensor.workday
calendar
calendar.google
camera
camera.ffmpeg
camera.generic
camera.nest
cast
climate
climate.generic_thermostat
climate.nest
config
config.auth
config.auth_provider_homeassistant
config.automation
config.config_entries
config.core
config.customize
config.device_registry
config.entity_registry
config.group
config.script
config.zwave
cover
cover.zwave
custom_updater
device_tracker
dialogflow
fan
fan.xiaomi_miio
feedreader
ffmpeg
frontend
google
google_assistant
group
hangouts
history
http
hue
ifttt
influxdb
input_boolean
input_number
input_select
input_text
intent_script
joaoapps_join
light
light.group
light.hue
light.mqtt_json
light.zwave
lock
logger
lovelace
map
media_extractor
media_player
media_player.cast
media_player.kodi
media_player.samsungtv
mqtt
nest
notify
notify.file
notify.hangouts
notify.joaoapps_join
notify.rest
notify.smtp
notify.twilio_sms
onboarding
panel_custom
panel_iframe
proximity
python_script
recorder
remote
remote.harmony
rss_feed_template
script
sensor
sensor.airvisual
sensor.alpha_vantage
sensor.apcupsd
sensor.command_line
sensor.cpuspeed
sensor.darksky
sensor.dnsip
sensor.file
sensor.filesize
sensor.glances
sensor.google_geocode
sensor.google_travel_time
sensor.gtfs
sensor.min_max
sensor.moon
sensor.mqtt
sensor.nest
sensor.noaa_tides
sensor.pi_hole
sensor.pollen
sensor.rest
sensor.season
sensor.systemmonitor
sensor.template
sensor.time_date
sensor.torque
sensor.uptime
sensor.version
sensor.waze_travel_time
sensor.worldtidesinfo
sensor.wunderground
sensor.zestimate
shell_command
sun
switch
switch.gmusic
switch.mqtt
switch.template
switch.wemo
switch.zoneminder
switch.zwave
system_log
tts
twilio
vacuum
vacuum.xiaomi_miio
webhook
weblink
websocket_api
wemo
zha
zone
zoneminder
zwave
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 28 (28 by maintainers)
FYI: I also replaced my ping sensors with the pre-0.80 code and re-enabled them, and I can confirm that after a number of hours there has been no issue.