-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transcoder failure - no TS found at start of file, duration not set #2769
Comments
Thanks for the report @eliteprox - there are some known bugs in Mist that occasionally causes us to receive invalid segments. The team are working on them at the moment and aiming to get them resolved by the end of the month, so I'll leave this open and then check back in once we've shipped a fix. |
Also getting these error reports from Transcoders as well |
Also getting this error may be similar issue?
|
I think they are from different causes, but you can see this same error in my transcoder logs prior to the crash. The primary difference between these two errors is the one you referenced is non-fatal and the one I've come across is fatal. I think the ideal bug fix from transcoder side will be to find a way to reproduce this and handle the error gracefully so it doesn't crash. I think both errors are handled through similar code in livepeer and/or lpms. |
Describe the bug
There seems to be an issue with some segments arriving without necessary keyframe information, such as duration. When this happens, it is possible for a transcoder to fail. Transcoder has failed with the following message. See attached logs also.
To Reproduce
Expected behavior
Transcoding process should not crash. Possibly reject incomplete segments that are missing information.
Desktop (please complete the following information):
Additional context
04:39:22
127.0.0.1:57032
around04:39:22
The text was updated successfully, but these errors were encountered: