livepeer / go-livepeer

Official Go implementation of the Livepeer protocol
http://livepeer.org
MIT License
541 stars 169 forks source link

unexpected EOF - couldnt read request body #2185

Open JJassonn69 opened 2 years ago

JJassonn69 commented 2 years ago

Describe the bug When the orchestrator gets the segment it doesnt transcode, instead it shows the error

l0114 16:46:50.136605 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/480p0/3.ts I0114 16:46:50.136605 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/240p0/3.ts I0114 16:46:50.137117 4560 player.go:105] LPMS got HTTP request @ /stream/c3ce2d94/360p0/3.ts

I0114 16:46:50.190671 4560 segment_rpc.go:95] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Received segment dur=1.6s

I0114 16:46:50.190671 4560 census.go:1055] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentEmerged... duration=1.6

E0114 16:46:50.476482 4560 segment_rpc.go:129] manifestID=0777scz7psr051nu seqNo=5 orchSessionID=c3ce2d94 Could not read request body - err="unexpected EOF"

I0114 16:46:50.707621 4560 segment_rpc.go:135] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Downloaded segment dur=516.4441ms

I0114 16:46:50.707621 4560 census.go:1110] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentDownloaded... dur=516.4441ms

I0114 16:46:50.709782 4560 orchestrator.go:483] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Starting to transcode segment

I0114 16:46:50.709782 4560 orchestrator.go:492] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Submitted segment to transcode loop

I0114 16:46:50.710300 4560 lb.go:60] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 LB: Using existing transcode session for key=c3ce2d94_0 ... I0114 16:46:50.823788 4560 orchestrator.go:575] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Transcoding of segment took=113.4876ms

I0114 16:46:50.823788 4560 census.go:1197] manifestID=0777scz7psr051nu seqNo=4 orchSessionID=c3ce2d94 Logging SegmentTranscode nonce=0 seqNo=4 dur=113.4876ms trusted=true verified=true

To Reproduce Steps to reproduce the behavior: I have the portforwarding such that the traffic is redirected from a server in singapore to my orchestrator in another location using VPN

Expected behavior No such error

Desktop (please complete the following information):

hthillman commented 2 years ago

@JJassonn69 can you add some more details about when this happens? is this persistent or intermittent? does it usually happen after some specific action?

JJassonn69 commented 2 years ago

@hthillman the error occurs frequently, it is transcoding well one second and suddenly it starts showing many errors with that msg, It started after VPN setup and I don't see such errors in other orchestrators which are not connected through a VPN. Maybe something to do with the encryption of VPN?

JJassonn69 commented 2 years ago

@hthillman what other information can I provide for further clarification on the issue?

hthillman commented 2 years ago

whoops, I missed these notifications, sorry for the delay!

Does the segment still transcode correctly? Based on the logs above, this looks more like a warning than a crash?

JJassonn69 commented 2 years ago

@hthillman I just get logs with the error message and nothing else. The above logs are just a clip from a long list of error.

darkdarkdragon commented 2 years ago

@JJassonn69 This error means that server wasn't able to read whole segment from the network. Probably VPN messes with connection somehow.

JJassonn69 commented 2 years ago

@hthillman anything I can do to fix it, aside from VPN disabling?

darkdarkdragon commented 2 years ago

@JJassonn69 maybe try to use another VPN? Otherwise you need to find out why VPN drops connections.