Jump to content
speedingcheetah

Record failing at random times/closed connection

Recommended Posts

speedingcheetah

I have having recording failures. Sometimes its 40 min, sometimes 15min.

The server reports stream  server closed connection. and it retries, but gets 403 error. and quits after 435ms.

I need this to be much longer and have it try more....

From the log, i gather my iptv service is dropping connection, and it take several seconds for it to accept a new connection.

here is what log says, removed the iptv url.

2020-07-13 16:15:53.562 Info SharedHttpPipelineSource: Remote server closed stream http://
2020-07-13 16:15:53.563 Info SharedHttpPipelineSource: Retry opening stream http://
2020-07-13 16:15:53.563 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://
2020-07-13 16:15:53.563 Info HttpClient: GET http:/
2020-07-13 16:15:53.999 Info HttpClient: Http response 403 from http:// after 435ms. HeadersServer=nginx, Date=Mon, 13 Jul 2020 21:15:53 GMT, Connection=close, Access-Control-Allow-Origin=*
2020-07-13 16:15:54.001 Error SharedHttpPipelineSource: Give up retries copying live stream http://
    *** Error Report ***
    Version: 4.4.3.0
    Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
    Operating system: Unix 5.3.0.62
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///opt/emby-server/system/System.Private.CoreLib.dll
    System.Environment.Version: 3.1.2
    Processor count: 4
    Program data path: /var/lib/emby
    Application directory: /opt/emby-server/system
    MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Forbidden
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
       at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.OpenStream(IDisposable connectionContext, MediaSourceInfo mediaSource, String url, MediaProtocol protocol, CancellationToken cancellationToken, Int32 recursion)
       at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.<>c__DisplayClass8_0.<<StartStreaming>b__0>d.MoveNext()
    Source: Emby.Server.Implementations
    TargetSite: Void MoveNext()
    
2020-07-13 16:15:54.003 Error SharedHttpPipelineSource: Error copying live stream.
    *** Error Report ***
    Version: 4.4.3.0
    Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
    Operating system: Unix 5.3.0.62
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///opt/emby-server/system/System.Private.CoreLib.dll
    System.Environment.Version: 3.1.2
    Processor count: 4
    Program data path: /var/lib/emby
    Application directory: /opt/emby-server/system
    MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Forbidden
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
       at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.OpenStream(IDisposable connectionContext, MediaSourceInfo mediaSource, String url, MediaProtocol protocol, CancellationToken cancellationToken, Int32 recursion)
       at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.<>c__DisplayClass8_0.<<StartStreaming>b__0>d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.<>c__DisplayClass8_0.<<StartStreaming>b__0>d.MoveNext()
    Source: Emby.Server.Implementations
    TargetSite: Void MoveNext()
    
2020-07-13 16:15:54.003 Info SharedHttpPipelineSource: SharedHttpPipelineSource is done streaming.

 

Share this post


Link to post
Share on other sites
speedingcheetah

any input here? can u make the retry rate longer/more....or even better, user adjustable?

Share this post


Link to post
Share on other sites
Luke

Please go over an example and attach the complete emby server log. thanks.

Share this post


Link to post
Share on other sites
speedingcheetah
Posted (edited)
49 minutes ago, Luke said:

Please go over an example and attach the complete emby server log. thanks.

that is the whole section on the recording where it failed. ur looking at the example. 

and no, not gonna send a full log. as it woudl have hundreds of lines where the U/P is listed. (and this is a public form)

simple request clear as day in the log posted. retry time is too short when emby detects remote server closed connection.

it happens when just live watching sometimes, part of the nature if iptv i guess....and i have to wait like 5 secs before i can tune again.

 

 

Edited by speedingcheetah

Share this post


Link to post
Share on other sites
Luke

I would really need to see the complete log file. You can always send it over PM. Thanks.

Share this post


Link to post
Share on other sites
speedingcheetah
Posted (edited)
1 hour ago, Luke said:

I would really need to see the complete log file. You can always send it over PM. Thanks.

Normally, for all the other possible issues, i woudl agree, however, this is stratightforward.

Emby opened the stream at approx 16:00, used it for nearly 16min time, (before log segment) then at 16:15:53.562, lost connection...Emby re-tried and after only 435ms, determined the connection to be 403 error,   and gave up trying, ending it recording.

The items before the paste, normal recording lines, the items after it, it saving the files to disk, and the meta data things etc.

There is littereraly NOTHING relevant other than this. Everything before and after the pasted log is normal.

 Info HttpClient: Http response 403 from http:// after 435ms. HeadersServer=nginx, Date=Mon, 13 Jul 2020 21:15:53 GMT, Connection=close, Access-Control-Allow-Origin=*
2020-07-13 16:15:54.001 Error SharedHttpPipelineSource: Give up retries copying live stream http:/

I am not saying that Emby caused the connection to drop, and that is what needs investigating....I know for a fact it is my iptv service, as it happens often on certain channels, sometimes, i guess if the provider is under load, idk. but it does it no matter what player i use to view the channel.

435ms worth of re-trying to connect to a data stream, is far to short and is not usefull at all.

All i ask is you to confirm this is what it means/is doing and explain why you have your program set to such a short retry time, and if you please, increase said retry rate and time.

Edited by speedingcheetah

Share this post


Link to post
Share on other sites
speedingcheetah

here is a large segment of another example. the original log file is over 5 million lines.

 

 

 

log.txt

Share this post


Link to post
Share on other sites
Luke

It looks like your live stream provider started sending back 403 forbidden errors. Have you consulted with them on why they would do that?

Share this post


Link to post
Share on other sites
speedingcheetah
9 minutes ago, Luke said:

It looks like your live stream provider started sending back 403 forbidden errors. Have you consulted with them on why they would do that?

They don't respond with anything usefull, they won't comment on using anything other than their own app (which is crap).

It can happen, far as i can tell, if i exceed my connection limit of 2. it will terminate the first connection...but that is not what is happening here, as Emby is the only connection using the account. I can only figure there is some sort of drop or something on the provider end. some times things are just not that stable based on server load maybe? idk. 

Share this post


Link to post
Share on other sites
Luke

Yea it looks like there was a stream disconnection and then as part of the retry process to re-open, they started sending back 403 forbidden.

Share this post


Link to post
Share on other sites
speedingcheetah
Just now, Luke said:

Yea it looks like there was a stream disconnection and then as part of the retry process to re-open, they started sending back 403 forbidden.

yea. and it sometimes takes several seconds for it to clear up and connect again.

it happens some times when viewing live, video just pauses. i close out then re-open, and sometimes Emby says cant tune channel at this time. wait like 5- 10 secs. then it loads.

Share this post


Link to post
Share on other sites
Luke

Thanks for the info. We can't control how strict they are about this, but hopefully we can continue to find new workarounds. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...