Failed to start Hyperion

  • Hello,
    I´m trying to connect some ws2812b to Hyperion (Pin 12/Gpio 18 of my Rasberry Pi Zero W) but i keep getting this messages when starting Hyperion service:


    ssh in: mag 17 22:17:33 raspberrypi systemd[1]: Started Hyperion Systemd service.
    ssh in: mag 17 22:17:35 raspberrypi systemd[1]: hyperion.service: Main process exited, code=exited, status=203/EXEC
    ssh in: mag 17 22:17:35 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:35 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    ssh in: mag 17 22:17:36 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: mag 17 22:17:37 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    ssh in: mag 17 22:17:37 raspberrypi systemd[1]: Started Hyperion Systemd service.
    ssh in: mag 17 22:17:37 raspberrypi systemd[1]: hyperion.service: Main process exited, code=exited, status=203/EXEC
    ssh in: mag 17 22:17:37 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:37 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: Started Hyperion Systemd service.
    ssh in: mag 17 22:17:38 raspberrypi systemd[401]: hyperion.service: Failed at step EXEC spawning /usr/bin/hyperiond: Exec format error
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: hyperion.service: Main process exited, code=exited, status=203/EXEC
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:38 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Started Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Main process exited, code=exited, status=203/EXEC
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Started Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Main process exited, code=exited, status=203/EXEC
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Start request repeated too quickly.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: mag 17 22:17:39 raspberrypi systemd[1]: hyperion.service: Failed with result 'exit-code'.
    sftp Send Hyperion Config - Sourcepath: C:/Users/Ivan/Desktop, Targetpath: /etc/hyperion/, Filename: hyperion.config.json
    ssh out: sudo systemctl start hyperion.service 2>/dev/null ; sudo /etc/init.d/hyperion start 2>/dev/null ; sudo /sbin/initctl start hyperion 2>/dev/null
    ssh out: sudo journalctl -u hyperion.service 2>/dev/null




    Also when i send the config i get:


    sftp Send Hyperion Config - Sourcepath: C:/Users/****/Desktop, Targetpath: /etc/hyperion/, Filename: hyperion.config.json
    ssh out: sudo systemctl start hyperion.service 2>/dev/null ; sudo /etc/init.d/hyperion start 2>/dev/null ; sudo /sbin/initctl start hyperion 2>/dev/null

  • the same here. I get:


    pi@hyperion:~ $ 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 Mon 2019-05-27 05:23:48 BST; 1s ago
    Process: 9873 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=SEGV)
    Main PID: 9873 (code=killed, signal=SEGV)


    Mai 27 05:23:47 hyperion systemd[1]: hyperion.service: Failed with result 'signal'.
    Mai 27 05:23:48 hyperion systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Mai 27 05:23:48 hyperion systemd[1]: Stopped Hyperion Systemd service.
    Mai 27 05:23:48 hyperion systemd[1]: hyperion.service: Start request repeated too quickly.
    Mai 27 05:23:48 hyperion systemd[1]: Failed to start Hyperion Systemd service.
    Mai 27 05:23:48 hyperion systemd[1]: hyperion.service: Unit entered failed state.
    Mai 27 05:23:48 hyperion systemd[1]: hyperion.service: Failed with result 'signal'.


    my config attached below.


    Any hint or suggestions?

Jetzt mitmachen!

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