1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

HyperCon Hyperion hangs up after few days

Discussion in 'Software Support' started by breaked, 21 January 2018.

  1. breaked

    breaked New Member

    Messages:
    3
    Hardware:
    RPi1/Zero, RPi2, RPi3, +PhilipsHue
    Hey everyone.

    Hyperion was such a great project I love it! But I have some trouble with it.
    It runs on a Raspberry Pi 3 with Raspbian Stretch. After a few days the Hyperion service isn't reachable. The Pi is still up. I use the external video grabber "LogiLink Audio und Video Grabber USB 2.0".



    A status of Hyperion with "sudo service hyperion status" outputs this:
    Code:
    [email protected]:~ $ 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 Thu 2018-01-18 14:24:14 UTC; 2 days ago
    
      Process: 16260 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=ABRT)
    
    Main PID: 16260 (code=killed, signal=ABRT)
    
    
    Jan 18 14:24:13 raspberrypi systemd[1]: hyperion.service: Main process exited, code=killed, status=6/ABRT
    
    Jan 18 14:24:13 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    
    Jan 18 14:24:13 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: Stopped Hyperion Systemd service.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: hyperion.service: Start request repeated too quickly.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    
    Jan 18 14:24:14 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.
    
    I already had installed hyperion on openelec but also here the same problem. I don't know wheres the problem ...
    I configured Hyperion with Hypercon.
    Hopefully someone can help me.

    hyperion.config.json:
     
  2. breaked

    breaked New Member

    Messages:
    3
    Hardware:
    RPi1/Zero, RPi2, RPi3, +PhilipsHue
    Could anyone give me a hint?
     
  3. Akriss

    Akriss Active Member

    Messages:
    322
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Well it restart with "sudo service hyperion restart" ?

    I'm not positive this will help, you could try to add "RestartSec=15" to the startup file "/etc/systemd/system/hyperion.service".
    The default restart time is 5 sec, this add 10 sec to the restart time.

    This line in the log hints that it may help
     
  4. Breaked92

    Breaked92 New Member

    Messages:
    1
    Thanks for your reply. I will have a try.

    With "sudo service hyperion restart" it restart and works to 99,9%.
     
  5. breaked

    breaked New Member

    Messages:
    3
    Hardware:
    RPi1/Zero, RPi2, RPi3, +PhilipsHue
    So, it worked for a few days now. Today it stopped. Thats the log:

    Code:
    [email protected]:~ $ sudo service hyperion status
    ● hyperion.service - Hyperion Systemd service
       Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: signal) since Sun 2018-01-28 09:16:42 UTC; 5s ago
      Process: 2658 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=ABRT)
    Main PID: 2658 (code=killed, signal=ABRT)
    
    Jan 28 09:16:42 raspberrypi systemd[1]: hyperion.service: Main process exited, code=killed, status=6/ABRT
    Jan 28 09:16:42 raspberrypi systemd[1]: hyperion.service: Unit entered failed state.
    Jan 28 09:16:42 raspberrypi systemd[1]: hyperion.service: Failed with result 'signal'.
    What can I do?!
     
  6. musicmagic

    musicmagic New Member

    Messages:
    5
    Hardware:
    RPi1/Zero
    I would like to push the last query. I had a working system (WS2801 stripe, RPI 1) for months, including a working (+calibrated) hyperion config.
    After watching this year's Eurovision Song Contest (with my parents in law..) I turned off the system (made pi powerless) for the first time in a while.
    Since then the system has not been working. I get the same error logs as user breaked. LEDs are all shining in blue but no rainbow swirl and/or no colors adjustable. I re-installed osmc numerous times (each time following Brindoschs Tutorials), I double-checked the wiring (multimeter indicates sufficient potential between GRND and 5V). I can even grab an image from my grabber, I'm just not able to transfer the signal to the stripe.
    I used another pi, same results.
    I tried manually adding the dtparam=spi=on to config.txt , only to find that it was already there. I also tried to use the appropriate settings from within OSMC. No luck.

    Has anybody got more ideas or can tell me what other logs to paste here that might be helpful?
    Cheers.
     
    Last edited: 2 July 2018
  7. Lyr3x

    Lyr3x New Member

    Messages:
    9
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino, +PhilipsHue
    may you post your log file?
     
  8. musicmagic

    musicmagic New Member

    Messages:
    5
    Hardware:
    RPi1/Zero
    There you go.
    Code:
    [email protected]:~$ sudo service hyperion restart
    [email protected]:~$ sudo service hyperion status
    * hyperion.service - Hyperion Systemd service
       Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: signal) since Sun 2018-07-01 15:07:25 CEST; 2s ago
      Process: 1980 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=ABRT)
    Main PID: 1980 (code=killed, signal=ABRT)
    
    Jul 01 15:07:25 Ambilight systemd[1]: hyperion.service: Unit entered failed state.
    Jul 01 15:07:25 Ambilight systemd[1]: hyperion.service: Failed with result 'signal'.
    
     

    Attached Files:

  9. musicmagic

    musicmagic New Member

    Messages:
    5
    Hardware:
    RPi1/Zero
    and another log from today. I added the solution-attempt from https://hyperion-project.org/threads/hyperion-not-starting.2719/ to my config and got the log afterwards.

    Code:
    SSH Traffic:
    ssh connected
    ssh out:     sudo journalctl -u hyperion.service 2>/dev/null
    ssh in:     -- Logs begin at Thu 2016-11-03 18:16:43 CET, end at Mon 2018-07-02 10:54:33 CEST. --
    ssh in:     Jul 02 10:53:16 Ambilight systemd[1]: Started Hyperion Systemd service.
    ssh in:     Jul 02 10:53:18 Ambilight hyperiond[227]: Hyperion Ambilight Deamon (227)
    ssh in:     Jul 02 10:53:18 Ambilight hyperiond[227]:         Version   : V1.03.4 (brindosch-c750c41/dc6a602-1522918225
    ssh in:     Jul 02 10:53:18 Ambilight hyperiond[227]:         Build Time: Apr  5 2018 01:57:25
    ssh in:     Jul 02 10:53:18 Ambilight hyperiond[227]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: HYPERION INFO: ColorTransform 'default' => [0; 95]
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: HYPERION INFO: ColorCorrection 'default' => [0; 95]
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: HYPERION INFO: ColorAdjustment 'default' => [0; 95]
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: LEDDEVICE INFO: configuration:
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: {
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]:         "colorOrder" : "rgb",
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]:         "name" : "MyHyperionConfig",
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]:         "output" : "/dev/spidev0.0",
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]:         "rate" : 1000000,
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]:         "type" : "ws2801"
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: }
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: INFO: Creating linear smoothing
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    ssh in:     Jul 02 10:53:19 Ambilight hyperiond[227]: EFFECTENGINE INFO: Initializing Python interpreter
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: INFO: Hyperion started and initialised
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: BLACKBORDER INFO: threshold set to 0.14 (36)
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: BLACKBORDER INFO: mode:default
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: started
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: INFO: Json server created and started on port 19444
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: INFO: Proto server created and started on port 19445
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in:     Jul 02 10:53:20 Ambilight hyperiond[227]:   what():  V4L2GRABBER ERROR: Cannot identify '/dev/video0' ERROR 2, No such file or directory
    ssh in:     Jul 02 10:53:20 Ambilight systemd[1]: hyperion.service: Main process exited, code=killed, status=6/ABRT
    ssh in:     Jul 02 10:53:20 Ambilight systemd[1]: hyperion.service: Unit entered failed state.
    ssh in:     Jul 02 10:53:20 Ambilight systemd[1]: hyperion.service: Failed with result 'signal'.
    ssh in:     Jul 02 10:54:10 Ambilight systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in:     Jul 02 10:54:10 Ambilight systemd[1]: Stopped Hyperion Systemd service.
    ssh in:     Jul 02 10:54:10 Ambilight systemd[1]: Started Hyperion Systemd service.
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: Hyperion Ambilight Deamon (414)
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         Version   : V1.03.4 (brindosch-c750c41/dc6a602-1522918225
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         Build Time: Apr  5 2018 01:57:25
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: HYPERION INFO: ColorTransform 'default' => [0; 95]
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: HYPERION INFO: ColorCorrection 'default' => [0; 95]
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: HYPERION INFO: ColorAdjustment 'default' => [0; 95]
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: LEDDEVICE INFO: configuration:
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: {
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         "colorOrder" : "rgb",
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         "name" : "MyHyperionConfig",
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         "output" : "/dev/spidev0.0",
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         "rate" : 1000000,
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]:         "type" : "ws2801"
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: }
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Creating linear smoothing
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: EFFECTENGINE INFO: Initializing Python interpreter
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Hyperion started and initialised
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: BLACKBORDER INFO: threshold set to 0.14 (36)
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: BLACKBORDER INFO: mode:default
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: started
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Json server created and started on port 19444
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: INFO: Proto server created and started on port 19445
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: V4L2GRABBER INFO: width=720 height=576
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: V4L2GRABBER INFO: pixel format=YUYV
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: BLACKBORDER INFO: threshold set to 0.14 (36)
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: BLACKBORDER INFO: mode:default
    ssh in:     Jul 02 10:54:11 Ambilight hyperiond[414]: V4L2GRABBER INFO: signal threshold set to: {0,0,0}
    ssh in:     Jul 02 10:54:12 Ambilight hyperiond[414]: V4L2GRABBER INFO: started
    ssh in:     Jul 02 10:54:12 Ambilight hyperiond[414]: INFO: V4L2 grabber created and started
    ssh in:     Jul 02 10:54:12 Ambilight hyperiond[414]: BORDER SWITCH REQUIRED!!
    ssh in:     Jul 02 10:54:12 Ambilight hyperiond[414]: CURRENT BORDER TYPE: unknown=0 hor.size=0 vert.size=0
    ssh in:     Jul 02 10:54:12 Ambilight hyperiond[414]: V4L2GRABBER INFO: stopped
    ssh in:     Jul 02 10:54:15 Ambilight hyperiond[414]: EFFECTENGINE INFO: effect finished
    ssh in:     Jul 02 10:54:15 Ambilight hyperiond[414]: V4L2GRABBER INFO: started
    
    Needless to say: I didn't see any swirl.
     
  10. musicmagic

    musicmagic New Member

    Messages:
    5
    Hardware:
    RPi1/Zero
    I solved the problem.
    After changing virtually every single component of the setup I found a faulty stripe-part (the first one).
    I replaced it and there was the rainbow.