Live TV went unresponsive, server restart fixed it

[FordGT90Concept 61]

It started acting up between 5-6 pm local time, restarted shortly after 7 pm. She was trying to watch Jeopardy on KMEG 14.1 but it wouldn't give her a stream on one of the SHIELDs.

unresponsive.zip

[Luke 37022]

Hi, there's a lot of log files here. Can you tell us exactly which one(s) correspond to the time of the problem? thanks.

[FordGT90Concept 61]

server-63637315200.txt no doubt has record of whatever happened.

 

Glancing at the FFMPEG logs, they look like they're referencing recordings on E:\ which aren't relevant. Live TV/transcoding is on C:\

 

You know what would be really handy? When it gives these lines:

2017-08-03 17:36:45.7538 Info HttpServer: HTTP Response 204 to 192.168.0.217. Time: 10ms. http://192.168.0.128:8096/emby/Sessions/Playing/Progress 
2017-08-03 17:37:00.7651 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.0; SHIELD Android TV Build/NRD90M)

It should give the client IP too. It would be easy for me to look up what SHIELD is on what IP address and single out what is relevant from not relevant. Alternatively, the SHIELD's device name would be super handy if you can get that.

 

 

Don't quote me on this but here is the last reference to live TV on 14.1 and it is immediately followed by an error. Coincidence? Hope not:

2017-08-03 19:06:54.8087 Info App: Streaming Channel hdhr_14.1_7b8bfe52571255b9d7d0bcae0d2516a2
2017-08-03 19:06:54.8087 Info App: Live stream c6332bb1afae4a9689bf25ec68da9467heavy_de4654ba03d9b61a33941902fa73ad91_48a893682be5723f92e738d9d73fb103 consumer count is now 6
2017-08-03 19:06:54.8087 Info MediaEncoder: C:\Users\Lee\AppData\Roaming\Emby-Server\ffmpeg\20170308\ffprobe.exe -analyzeduration 3000000 -i "http://127.0.0.1:8096/LiveTv/LiveStreamFiles/de9c9c5d6614465eb3ff15d7ede99c58/stream.ts" -threads 0 -v info -print_format json -show_streams -show_format
2017-08-03 19:06:54.8087 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 3.2.26.12
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	64-Bit OS: True
	64-Bit Process: True
	Processor count: 8
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application directory: C:\Users\Lee\AppData\Roaming\Emby-Server\system
	System.ObjectDisposedException: Cannot access a disposed object.
	Object name: 'SocketHttpListener.Net.HttpListenerResponse'.
	   at SocketHttpListener.Net.HttpListenerResponse.CheckDisposed()
	   at SocketHttpListener.Net.HttpListenerResponse.set_ContentType(String value)
	   at Emby.Server.Implementations.Services.ResponseHelper.<WriteToResponse>d__0.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__76.MoveNext()
	System.ObjectDisposedException
	   at SocketHttpListener.Net.HttpListenerResponse.CheckDisposed()
	   at SocketHttpListener.Net.HttpListenerResponse.set_ContentType(String value)
	   at Emby.Server.Implementations.Services.ResponseHelper.<WriteToResponse>d__0.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__76.MoveNext()

There's a bunch more errors after that.

 

This is not long before server restart occurred, I think the original problem has to be back further...

 

So the problem likely occurred between this and the above:

2017-08-03 17:17:39.2908 Info App: Opening channel stream from Emby, external channel Id: hdhr_14.1_7b8bfe52571255b9d7d0bcae0d2516a2
2017-08-03 17:17:39.2908 Info App: Streaming Channel hdhr_14.1_7b8bfe52571255b9d7d0bcae0d2516a2
2017-08-03 17:17:39.2908 Info App: Live stream c6332bb1afae4a9689bf25ec68da9467heavy_de4654ba03d9b61a33941902fa73ad91_48a893682be5723f92e738d9d73fb103 consumer count is now 2

Without making a program to do it, I can't really distinguish the activity of the two shields. One (the one that had the problem) was watching live TV, the other was watching recordings. The recordings one is probably irrelevant to the live TV problem.

 

 

Actually, it seems like there's really nothing in the logs. I think what I posted above about tuning to 14.1 never actually succeeded.

 

 

 

Side note: could you change these errors into warnings:

2017-08-03 15:31:49.6718 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 3.2.26.12
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	64-Bit OS: True
	64-Bit Process: True
	Processor count: 8
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application directory: C:\Users\Lee\AppData\Roaming\Emby-Server\system
	MediaBrowser.Common.Extensions.ResourceNotFoundException: KCAU9 News at 6pm does not have an image of type Primary
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at MediaBrowser.Api.Images.ImageService.Get(GetItemImage request)
	   at Emby.Server.Implementations.Services.ServiceExecGeneral.<Execute>d__2.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__76.MoveNext()
	MediaBrowser.Common.Extensions.ResourceNotFoundException
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at MediaBrowser.Api.Images.ImageService.Get(GetItemImage request)
	   at Emby.Server.Implementations.Services.ServiceExecGeneral.<Execute>d__2.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.<ProcessRequestAsync>d__15.MoveNext()
	--- End of stack trace from previous location where exception was thrown ---
	   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
	   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__76.MoveNext()

There's a lot of missing picture errors logged and they're not really errors at all. Edited August 4, 2017 by FordGT90Concept

[Luke 37022]

@@FordGT90Concept has this happened again? Thanks !

[FordGT90Concept 61]

Not recently, no.

[Luke 37022]

Thanks for the feedback.