Closed rwlove closed 1 year ago
Hi
I would like to validate and explore some things...
journalctl --since "1 hour ago" > journal.txt
Thank you!
Hi
I would like to validate and explore some things...
- I assume that the log is after you restartet CoreElec Hyperion, correct?
No, I'm keeping a browser tab open with the Hyperion NG debug log via the webui and I believe that I'm grabbing the log prior to the system coming back online and restarting the log. The debug log seems to be cached in the browser until the system comes back up and resets the log.
- Does the crash happens when do you specific activities via the Hyperion-UI?
No, the crashes are frequent and happen even when I don't have the webui open.
- Does the crash happens when watching a movie?
Yes. I primarily watch videos on a NFS drive, of varying qualities, but including 4k HDR video. I'm also getting crashes watching Youtube videos (vp9). The content doesn't seem to matter.
- Does it occur when you watch a specific file type, huge resolution video?
As mentioned on the previous answer, it seems to happen with any video files.
- Could you run the following command (via ssh) after the next crash and reboot and share the output file (you can contact me on https://hyperion-project.org/ and share details privately with me)
journalctl --since "1 hour ago" > journal.txt
Done. I'll figure out how to contact you on the project site.
Thank you!
No, thank you!
I'd like to add that today I've been playing around with the Display Decimation and Capture Frequency settings and none of these adjustments seem to help.
Someone on a CoreELEC thread suggested that the CPU is maxing out, but I don't observe the CPU being very high. Especially when I tune down the Capture Frequency to 20 and the Display Decimation to 26, I'm seeing less than 25% for kodi.bin and less than 25% for hyperiond. It's possible that they spike up before the crash and I'm just not seeing it, but I haven't observed that, for what it's worth.
Thanks for the answers.
on 1. There is no caching, if Hyperion fails the Web-page normally shows a disconnected view and if then the system comes up again , if refreshes automatically.
on 5. Unfortunately, it seems that the log is cleaned after reboot and there is no information prior reboot.
Would it be an option to run journalctl -f
via a terminal (which tracks the log output) and then share the terminal output after the system crsahed. E.g. putty keeps those messages. Then we hopefully see what is happening before the crash.
Edit: if you do not want having the terminal open all time, you could also do a
journalctl -f > journal2.txt &
and exit and after reboot crash get the file.
But maybe you start with terminal that nothing gets missed during file writing
I just captured two journals for two separate crashes. I'll send you the journals, but I don't think it's logging anything when the system crashes.
Unfortunately, the journal does not contain any error information nor are there any details that it is Hyperion that crashes your system.
The CoreElec team advised, that if your CoreElec crashes and reboots itself, you need to look at the dump. Please follow the instructions here: https://wiki.coreelec.org/coreelec:debuglogs#ramoops_panic_logger
If you had a Kernel Oops, you would have a folder in /sys/fs/pstore
with details.
If there is no subfolder, then it was not a Kernel Oops.
I suggest you start from a CoreElec perspective to find the root cause and if it is hyperion, we try to further explore.
Closing, as this is not a Hyperion issue, but a CoreElec one (see thread above).
Bug report
Hyperion NG as a Kodi plugin crashes CoreELEC 19.5-Matrix_rc2 on an ODroid N2+ w/ WLED 0.13.3.
Steps to reproduce
Enable Hyperion NG via webui Play video (youtube plugin or video file on NFS share) After some time, usually a few hours, but sometimes within minutes, CoreELEC crashes
What is expected?
Video playback with no crash
What is actually happening?
CoreELEC crashes and reboots
System
Hyperion Server:
Hyperion Server OS:
Debug Log
I had the same problem on my previous X96 Air (S905x3) box.
One curious thing that I noticed is that the resolution listed in Hyperion NG is 1920x1080, but the resolution could be as large as 3840x2160.
I’d be happy to provide additional logs or do some debugging, but I’m not sure what next steps I should take.