Skip to content

Python 3.6 + 0.45.1 - Segmentation Faults #7752

@arraylabs

Description

@arraylabs

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.45.1

Python release (python3 --version): 3.6.1

Component/platform:

Description of problem:
Docker file installed as explained in documentation. Getting segmentation faults after a couple hours of running. There are no messages in the HA error log when it seg faults. Only place I have seen it logged is in the messages log from dmesg. It contains the following:

May 23 23:02:46 hass kern.info kernel: [100410.601161] python[20759]: segfault at 8 ip 000076dfbbae97b2 sp 000076dfa8837ea0 error 6 in libpython3.6m.so.1.0[76dfbba45000+29a000]
May 23 23:02:46 hass kern.alert kernel: [100410.601196] grsec: Segmentation fault occurred at 0000000000000008 in /usr/local/bin/python3.6[python:20759] uid/euid:0/0 gid/egid:0/0, parent /usr/bin/docker-containerd-shim[docker-containe:4467] uid/euid:0/0 gid/egid:0/0
May 23 23:02:46 hass kern.alert kernel: [100410.601455] grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /usr/local/bin/python3.6[python:20759] uid/euid:0/0 gid/egid:0/0, parent /usr/bin/docker-containerd-shim[docker-containe:4467

Switching back to 0.44.2 all works without issue and 0.45.0/1 is the first time I have experienced any seg faults. Further info. I installed 0.45.0 (via docker rm, pull, run, etc) late saturday or early sunday on an ubuntu 16 esxi vm (my normal environment run HA without issue for the last year or so) and within a few hours it died with a seg fault error. Restarted HA, ran fine for a few hours then seg faulted again. At this point I moved back to 0.44.2 via docker and all ran fine. On monday i moved my HA docker install to a physical box running latest alpine linux with docker and version 0.44.2 (turning off my vm install) and it came up without issue and ran fine until I decided to try 0.45.1 again yesterday. So on the physical alpine linux box I again used docker to rm, pull, run, etc and move to 0.45.1. All came up fine then a few hours later the seg fault again occurred. Restarted the container, all was again fine for a few hours and again seg fault. Moved back to 0.44.2 and its been running without issue since then.

Seg faults on two different "machines" with two different operating systems concerns me.

Expected:
No seg faults

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy