Jump to content

Live TV Instability


nominion

Recommended Posts

nominion

After upgrading to server version 3.2.1.0 running on Windows 10, I have noticed a lot of instability with Live TV.  Tonight, I was watching a TV show on one of my Nvidia Shield boxes and at 21:32, the show stopped playing and the Emby app returned to the guide.  When I tried to start the show again, all I got was the spinning wheel.  The HDHomeRun Prime box only showed one tuner in use which was for a scheduled recording.  This actually happened 3 different times today.  The Emby app on my Shield is the latest stable release and the firmware on my HDHomeRun is 20161117.  

 

I've attached the sever logs for that time.  You can see @ 21:32:15.7612 there is an error.  The server's IP is .10.  The HDHomeRun's IP is .125.  The Shield's IP is .159.  There are more errors @ 21:35:32.3559 which I assume is when I tried to tune to the channel again.  

 

Does anyone have any thoughts?  Thanks in advance!

 

server-63622702574.txt

Link to comment
Share on other sites

nominion

It happened again tonight.  This time, when I hit play to start the TV show again, my Nvidia Shield reported "video error".  In order to get Live TV to work again, I have to restart Emby on the server.  I've enable debug logging in the Emby app and I will upload the logs when it happens again.

 

Thoughts?

Edited by nominion
Link to comment
Share on other sites

nominion

Great!  Thank you!  I did manage to catch the problem and upload the debug logs from the Emby App.  If you need any other details, please let me know.

Link to comment
Share on other sites

Great!  Thank you!  I did manage to catch the problem and upload the debug logs from the Emby App.  If you need any other details, please let me know.

 

Hi.  What time was this, what were you playing and what was the name of the Emby user that was logged in?  Thanks.

Link to comment
Share on other sites

nominion

Hi.  What time was this, what were you playing and what was the name of the Emby user that was logged in?  Thanks.

The user was "nvs".  I *think* I was watching ESPN and the issue happened at 21:32.  

 

I was also having problems yesterday.  The first time it happened, I enabled debug logging on the server and the Emby client.  I restarted the server at 11:21, tuned to NGEO, and shortly thereafter, the problem occurred.  I uploaded the debug logs from the Emby client and I've attached the server logs here.  

 

What is very curious is I see this in the log when searching for NGEO:

 

2017-02-18 11:22:25.0563 Debug App: Channels from http://192.168.11.125: 

 

but continuing to search the log, and I see this:

 

2017-02-18 11:55:27.3642 Debug App: Channels from http://169.254.140.67: 

 

This makes me wonder if the HDHR is dropping off the network for some reason.  I'm going to continue to research that today.

server-63623004738.txt

server-63623013680.txt

Link to comment
Share on other sites

nominion

I think the problem might be the HDHR.  Here are the log entries from this morning:

 

20170219-08:36:16 System: network link down
20170219-08:36:19 System: network link 1000f
20170219-08:36:20 System: network link down
20170219-08:36:23 System: network link 1000f
20170219-08:36:45 System: ip address obtained: 169.254.140.67 / 255.255.0.0
20170219-08:37:04 System: myhdhomerun_sync: webclient error (dns failed)
20170219-08:47:39 System: myhdhomerun_sync: webclient error (dns failed)
20170219-08:48:24 System: ip address obtained: 192.168.11.125 / 255.255.255.0
 
And I found this thread on their forum:  https://forum.silicondust.com/forum/viewtopic.php?f=113&t=63510
 
That thread pretty much describes what I see in the logs on the HDHR and likely why Live TV stops working for me in Emby.
 
I'm going to try a few things that people suggest and I will report back.
  • Like 1
Link to comment
Share on other sites

nominion

Found this in the Windows event log on the Emby server this morning when it wasn't reachable on the network.:

 

Log Name:      System
Source:        Tcpip
Date:          2/19/2017 7:49:43 AM
Event ID:      4199
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      home-emby-svr
Description:
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 00-18-DD-31-EC-F3. Network operations on this system may be disrupted as a result.
 
00-18-DD-31-EC-F3 is the MAC address of the HDHR.  
 
It appears that the HDHR is sending gratutious ARP packets with 0.0.0.0 as the source address, which causes Windows to think there is an IP conflict.
 
As stupid as it is, I've set the network port on my switch to 100/Full for the HDHR and it hasn't had any issues for most of the day.  If it goes 2 days, I will say they problem is resolved.  
Edited by nominion
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...