-
Notifications
You must be signed in to change notification settings - Fork 178
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
Segments fail to upload on commit 73aaca8c3da1f5269fe059dd03b0cbf4d6796a1c #2582
Comments
It looks like the branch has been removed, but it contained all of the commits which are now in the master branch which got added after v0.5.34. It seems that one of the commits added after this release was causing this issue |
i deployed 2 days ago the linux 0.5.34-3ff79bd7 version because this one fix the estimation gas error. |
@oscar-davids @cyberj0g The only commits that came in since 0.5.34 are #2381 and #2568 - I know there's not a lot to go on here, but would appreciate any thoughts on what might be that cause / what info we could ask for to help us debug |
The issue of difficulty to keep streams has been fixed by #2586. The uploading segment failure issue has been fixed by #2591. |
Nice! I'll run the latest master build on my orch nodes and will report if anything breaks |
Immediately got 30 |
@stronk-dev thank you for testing immediately. |
Will take a while since i can't build go-livepeer from source on Arch, will probably give it a go later today |
Just switched all of my nodes to commit 6c49c04 (retrieved the binary from discord builds channel). Results:
|
@stronk-dev can you give me dashboard link? |
Yea, my dashboard is publicly available at: https://grafana.stronk.tech/d/71b6OZ0Gz/orchestrator-overview It has all info and error logs pulled from Loki and a counter for specific errors which you can unfold: |
All Orchestrator nodes were operating fine on 0.5.34, except for Boston, which was running on a special version version of 0.5.34
Almost all segments fail to upload, causing test stream scores to plummet. Weirdly enough, it did not seem to affect my actual transcoding work. One other Orchestrator also confirmed this issue while he was on above version and also rolled back to 0.5.34 to fix the issue
I don't much info to give you, as the code does not print the actual error message when it fails...
The text was updated successfully, but these errors were encountered: