Hyperion won't start - Segmentation Fault

Help and Support
1

Hi,

I have been using Hyperion for over a year. I had some issues with my OSMC build and decided to do a clean install.

After the clean install I wanted to setup Hyperion again, but I can’t get it to work. Not with my old config file, and not with a new one either.

The error I’m getting is

ssh in: Nov 23 22:41:48 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
ssh in: Nov 23 22:41:48 osmc systemd[1]: Unit hyperion.service entered failed state.

When I manually try to start any of the hyperion files (such as hyperion-remote to test) I just get “Segmentation Fault”
When I do sudo hyperion-remote i get no output.

systemctl status hyperion.service returns:
osmc@osmc:~$ systemctl status hyperion.service

  • hyperion.service - Hyperion Systemd service
    Loaded: loaded (/etc/systemd/system/hyperion.service; enabled)
    Active: failed (Result: start-limit) since Thu 2017-11-23 22:41:48 CET; 1min 39s ago
    Process: 2776 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=SEGV)
    Main PID: 2776 (code=killed, signal=SEGV)

Besides using the Hypercon installer, I also tried installing the old way (http://www.vervelendemensen.nl/2014/03/how-to-install-hyperion-on-the-raspberry-pi-for-ambilight/)

Hope someone can help!

2

Hi,

Whats the output of:

sudo journalctl -u hyperion.service

Thanks Tom.

3

Hey Tom, thanks for helping.

Its the same as the log I posted afaik:

Nov 23 21:17:16 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:17:16 osmc systemd[1]: Started Hyperion Systemd service.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
Nov 23 21:17:17 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service holdoff time over, scheduling restart.
Nov 23 21:17:17 osmc systemd[1]: Stopping Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Started Hyperion Systemd service.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
Nov 23 21:17:17 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service holdoff time over, scheduling restart.
Nov 23 21:17:17 osmc systemd[1]: Stopping Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Started Hyperion Systemd service.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
Nov 23 21:17:17 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service holdoff time over, scheduling restart.
Nov 23 21:17:17 osmc systemd[1]: Stopping Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Started Hyperion Systemd service.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
Nov 23 21:17:17 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:17:17 osmc systemd[1]: hyperion.service holdoff time over, scheduling restart.
Nov 23 21:17:17 osmc systemd[1]: Stopping Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:17:17 osmc systemd[1]: hyperion.service start request repeated too quickly, refusing to start.
Nov 23 21:17:17 osmc systemd[1]: Failed to start Hyperion Systemd service.
Nov 23 21:17:17 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:20:04 osmc systemd[1]: Stopped Hyperion Systemd service.
Nov 23 21:23:14 osmc systemd[1]: Stopped Hyperion Systemd service.
Nov 23 21:24:11 osmc systemd[1]: Starting Hyperion Systemd service…
Nov 23 21:24:11 osmc systemd[1]: Started Hyperion Systemd service.
Nov 23 21:24:11 osmc systemd[1]: hyperion.service: main process exited, code=killed, status=11/SEGV
Nov 23 21:24:11 osmc systemd[1]: Unit hyperion.service entered failed state.
Nov 23 21:24:11 osmc systemd[1]: hyperion.service holdoff time over, scheduling restart.

4

Hi,

It doesn’t help much does it…

I see you’ve posted on the Hyperion forums, they can probably advise better.

But saying that it does seem another osmc reported a similar issue:

https://github.com/hyperion-project/hyperion/issues/540

Thanks may.

Thanks Tom.

5

Still no response on hyperion or anywhere else for that matter.

I’ve seen the link you posted, but it’s a different problem. Do you have any insight into what segmentation fault actually means under these circumstances?