Hyperiond crashes

peter · 11. Januar 2017

Hyperiond service is crashing when I switch between static color (colors) and other modes (effects, live view, etc). I must reboot my RPi.

Please, where hyperiond stores logs?
I would like to try to find the reason of crashes by myself, too. Thanks

TPmodding · 11. Januar 2017

https://hyperion-project.org/wiki/Hyperion-Log did you try with this method?

peter · 12. Januar 2017

Zitat von TPmodding

https://hyperion-project.org/wiki/Hyperion-Log did you try with this method?

Yes, I did.

I hoped for more detailed log but ssh returned (se below) the same log as I can find in system logs in /var/log
In ssh log there is just information about trying of restart hyperiond service, but no information why it terminated.

Code

ssh in:     Jan 12 12:58:09 pi hyperiond[480]: terminate called after throwing an instance of 'std::runtime_error'
ssh in:     Jan 12 12:58:09 pi hyperiond[480]: what():  VIDIOC_STREAMON ERROR 12, Cannot allocate memory
ssh in:     Jan 12 12:58:09 pi systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
ssh in:     Jan 12 12:58:09 pi systemd[1]: Unit hyperion.service entered failed state.
ssh in:     Jan 12 12:58:09 pi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in:     Jan 12 12:58:09 pi systemd[1]: Stopping Hyperion Systemd service...
ssh in:     Jan 12 12:58:09 pi systemd[1]: Starting Hyperion Systemd service...
ssh in:     Jan 12 12:58:09 pi systemd[1]: Started Hyperion Systemd service.
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: Hyperion Ambilight Deamon (1040)
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: Version   : V1.03.2 (brindosch-99d9396/d3713a8-1469452981
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: Build Time: Jul 25 2016 06:54:40
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: HYPERION INFO: ColorTransform 'default' => [0; 149]
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: HYPERION INFO: ColorCorrection 'default' => [0; 149]
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: HYPERION INFO: ColorAdjustment 'default' => [0; 149]
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: LEDDEVICE INFO: configuration:
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: {
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: "colorOrder" : "grb",
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: "leds" : 150,
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: "name" : "pi",
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: "type" : "ws281x"
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: }
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: whiteAlgorithm ::
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Creating linear smoothing
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: EFFECTENGINE INFO: Initializing Python interpreter
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Hyperion started and initialised
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: BLACKBORDER INFO: threshold set to 0.1 (26)
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: BLACKBORDER INFO: mode:default
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: started
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Json server created and started on port 19444
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: INFO: Proto server created and started on port 19445
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: V4L2GRABBER INFO: width=720 height=576
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: V4L2GRABBER INFO: pixel format=UYVY
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: BLACKBORDER INFO: threshold set to 0.1 (26)
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: BLACKBORDER INFO: mode:default
ssh in:     Jan 12 12:58:09 pi hyperiond[1040]: V4L2GRABBER INFO: signal threshold set to: {51,102,255}
ssh in:     Jan 12 12:58:09 pi systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
ssh in:     Jan 12 12:58:09 pi systemd[1]: Unit hyperion.service entered failed state.

Alles anzeigen

TPmodding · 12. Januar 2017

hmmm...did you try to kill all hyperion processes and start it manually? then you get maybe more information

peter · 12. Januar 2017

I started hyperiond manually.
Then I tried to go to static color and the back to live mode several times until this:
V4L2GRABBER ERROR: Frame too small: 705796 != 829440
V4L2GRABBER ERROR: Frame too small: 725796 != 829440
... a lot of these lines ...
V4L2GRABBER ERROR: Frame too small: 745796 != 829440
V4L2GRABBER ERROR: Frame too small: 715796 != 829440
V4L2GRABBER INFO: stopped (here I tried to go to static color again and then back to live mode)
V4L2GRABBER INFO: started (v4l2 grabber should be started, but when I go back to live mode, all LEDs are off with no color)
V4L2GRABBER INFO: stopped (and suddenly this happens and hyperiond definitelly crashed)
terminate called after throwing an instance of 'std:runtime_error'
what(): VIDIOC_STREAMON ERROR 12, Cannot allocate memory

Then when I try to start hyperiond manually again, It did not start and I see it stops initiating of hyperiond on line:
terminate called after throwing an instance of 'std::runtime_error'
what(): VIDIOC_STREAMON ERROR 12, Cannot allocate memory

peter · 12. Januar 2017

I think the whole problem is because of starting and stopping v4l2grabber each time you switch back from live to static/effect mode. The better would be to have v4l2grabber live mode always started, and when we choose static/effect color then just to tell to v4l2grabber part to not send data to LEDs (because of color/effect higher priority). This would probably solve this issue, because hyperiond should not need to reinitiate v4l2grabber again and again (v4l2grabber could be always initiated but just effects/static color will have just higher priority).

TPmodding · 13. Januar 2017

could you post the output from lsusb?

peter · 13. Januar 2017

yes please, here is lsusb:

Code

Bus 001 Device 004: ID 05e1:0408 Syntek Semiconductor Co., Ltd STK1160 Video Capture Device
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

redPanther · 13. Januar 2017

For frame to small increase width/height values of v4l config

TPmodding · 13. Januar 2017

https://hyperion-project.org/t…vice-failed-to-start.468/

stk1160 usb grabber makes this error...just use a fushicai

peter · 16. Januar 2017

Thanks @TPmodding, I will try it once I have it.

TPmodding · 16. Januar 2017

can you try to set the grabber to 240x192 ?

peter · 18. Januar 2017

Zitat von TPmodding

can you try to set the grabber to 240x192 ?

I tried, but the behaviour (of stk) is the same. I am waiting for fushicai to deliver.

Hyperiond crashes

Jetzt mitmachen!

Benutzer online in diesem Thema