Hyperion "failed state 'signal'" starting issue

  • Hello,
    a friend of mine and me (German) are currently trying to install hyperion on raspbian and sadly encountered a strange problem.


    Hyperion sadly doesn't seem to start.


    First it seemed that we had trouble to parse the configuration file (which seemed to be a part which accidently wasn't commented out) but right now we are exiting the program with an error 'signal'.



    The configuration has been generated by hypercon but written manually into "/etc/hyperion/hyperion.config.json" since hypercon wasn't able to put it there somehow by it's own.



    We are currently running out of ideas and we are hoping that you can help us.


    Thanks.


    Sincerely.



    ******************************************
    sudo journalctl -u hyperion:


    Aug 29 01:08:16 raspberrypi systemd[1]: Started Hyperion Systemd service.
    Aug 29 01:08:16 raspberrypi hyperiond[1605]: Hyperion Ambilight Deamon (1605)
    Aug 29 01:08:16 raspberrypi hyperiond[1605]: Version : V1.03.4 (brindosch-c750c41/dc6a602-1522918225
    Aug 29 01:08:16 raspberrypi hyperiond[1605]: Build Time: Apr 5 2018 01:57:25
    Aug 29 01:08:16 raspberrypi hyperiond[1605]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Main process exited, code=killed, status=11/SEGV
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Aug 29 01:08:16 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Start request repeated too quickly.
    Aug 29 01:08:16 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.




    *******************************************
    sudo hyperion status:


    sudo service hyperion status
    ● hyperion.service - Hyperion Systemd service
    Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
    Active: failed (Result: signal) since Wed 2018-08-29 01:08:16 CEST; 25min ago
    Main PID: 1605 (code=killed, signal=SEGV)


    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Aug 29 01:08:16 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Start request repeated too quickly.
    Aug 29 01:08:16 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    Aug 29 01:08:16 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.

  • Hi, what does mean "preinstalled image"? Newly downloaded image of raspbian?


    I have same problem with raspbian (RPi3) and hyperion: "hyperion.service: main process exited, code=killed, status=11/SEGV"

  • Hi, what does mean "preinstalled image"? Newly downloaded image of raspbian?


    I have same problem with raspbian (RPi3) and hyperion: "hyperion.service: main process exited, code=killed, status=11/SEGV"


    plz run:

    Code
    sudo service hyperion status


    and then start the command of the output manually...


    for example

    Code
    /opt/hyperion/bin/hyperiond /opt/hyperion/config/hyperion.config.json 
    /usr/share/hyperion/hyperiond  /etc/hyperion/hyperion.config.json


    and post the output

  • new installation of LibreELEC (on Raspberry Pi Zero) and same behavior: "Segmentation fault"


    output of hyperiond:


    config:

  • The OP on the second post marked this solved.


    However, It seems as wandering necromancers like to resurrect this dead post.


    :whistle:

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!