Jump to content

LiveTV Streaming Issue


drunknarwhal

Recommended Posts

drunknarwhal

Hi,

 

I've noticed that after around 3 or 4 hours LiveTV stops working until I restart Emby completely(Any channel I visit it just sits there with the spinning circle). As soon as Emby restarts LiveTV works fine without any issues for another 3 or 4 hours.

 

I'm running Emby on a remote Linux server and I opened a support ticket to have them take a look to make sure there were no port issues etc. The IPTV stream i'm using is a m3u stream. I've tested the stream on my phone using  different app  and it had no issues loading so i'm not really sure what's going. Below are some background information my server host provided to me( I scrubbed it so it might be missing information just thought I would include it):

 

[asia ~] curl -v Removed
*   Trying 51.89.191.93...
* TCP_NODELAY set
* Connected to Removed (51.89.191.93) port 80 (#0)
> GET XXXXX HTTP/1.1
> Host: Removed
> User-Agent: curl/7.52.1
> Accept: */*
< HTTP/1.1 302 Found
< Server: nginx
< Date: Sun, 25 Aug 2019 10:48:44 GMT
< Content-Type: text/html; charset=UTF-8
< Connection: close
< Access-Control-Allow-Origin: *
* Curl_http_done: called premature == 0
* Closing connection 0
 
I've also attached my log file and you can see there are a lot of Error Reports. For the most part I assume all of these occurred while I tried watching a channel on LiveTV(I pulled this log after the very bottom error report generated).

 

 

Link to comment
Share on other sites

drunknarwhal

Hi Luke - sorry thought I attached the log initially, but looks like I didn't. I'm going to try to find another stream that doesn't require my login/password info that I can use. The log I attached is from last night. LiveTV worked fine for about 2- 3 hours then around the 4 hour mark below I just receive the spinning circle on any channel I try until I restart the server:

 

5d63e7ed07edb_Capture.png

embyserver.txt

Link to comment
Share on other sites

I think this is an issue in the .NET core runtime. I found a couple tickets related to it:

 

https://github.com/dotnet/corefx/issues/32971

https://github.com/dotnet/corefx/issues/33094

 

It looks like the fix will be in .NET Core 3.0, which will be released next month and we'll be using it on the beta channel very soon. Thanks.

Link to comment
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...