Jump to content

HDHomeRun rejecting request logs


FordGT90Concept

Recommended Posts

FordGT90Concept

Edit: Both of the HDHomeRun errors below resulted in a scheduled program not getting recorded.  A second HDHomeRun was available to handle it...but not used!

 

Emby server is running on 192.168.0.128 and no other software reaches out to the HDHomeRuns from that IP other than to update firmware...

20171017-01:59:59 Tuner: tuner1 tuning 14.1 KMEG-DT (8vsb:623MHz-3)
20171017-01:59:59 Tuner: tuner1 streaming http to 192.168.0.128:57345
20171017-02:00:59 Tuner: tuner0 tuning 9.1 KCAU-TV (8vsb:189MHz-3)
20171017-02:00:59 Tuner: tuner0 streaming http to 192.168.0.128:57416
20171017-02:00:59 HTTP: rejecting request from 192.168.0.128 - all tuners in use

Note the time stamps on those last three...Emby should have the presence of mind to know it should move to the next tuner since this tuner is busy.

 

Similar thing happened a day later:

20171018-01:00:00 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20171018-01:00:00 Tuner: tuner0 streaming http to 192.168.0.128:63300
20171018-01:00:01 Tuner: tuner1 tuning 14.1 KMEG-DT (8vsb:623MHz-3)
20171018-01:00:01 Tuner: tuner1 streaming http to 192.168.0.128:63302
20171018-01:00:01 HTTP: rejecting request from 192.168.0.128 - all tuners in use

I believe these timestamps are GMT and I'm at CDT/CST so 5 hour adjustment...8pm on the 17th...

2017-10-17 20:00:00.093 Info App: Recording timer fired.
2017-10-17 20:00:00.093 Info App: Recording timer fired.
2017-10-17 20:00:00.093 Info App: Recording timer fired.

4.1: E:\Recordings\This Is Us\Season 2\This Is Us S02E04 Still There.ts

14.1: E:\Recordings\Bull\Season 2\Bull S02E04 The Illusion of Control.ts

4.2: ???

2017-10-17 20:00:01.411 Error HttpClient: Error ProtocolError getting response from http://192.168.0.160:5004/auto/v4.2
*** Error Report ***
Version: 3.2.33.11
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
User Interactive: 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.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
System.Net.WebException
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

2017-10-17 20:00:01.412 Error App: Error copying live stream.
*** Error Report ***
Version: 3.2.33.11
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
User Interactive: 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.Model.Net.HttpException: The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
    --- End of inner exception stack trace ---
    at Emby.Server.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__22.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.HttpClientManager.HttpClientManager.<SendAsync>d__19.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.LiveTv.TunerHosts.HdHomerun.HdHomerunHttpStream.<>c__DisplayClass6_0.<<StartStreaming>b__0>d.MoveNext()
MediaBrowser.Model.Net.HttpException
    at Emby.Server.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__22.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.HttpClientManager.HttpClientManager.<SendAsync>d__19.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.LiveTv.TunerHosts.HdHomerun.HdHomerunHttpStream.<>c__DisplayClass6_0.<<StartStreaming>b__0>d.MoveNext()
InnerException: System.Net.WebException
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
    at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

Having difficulty figuring out what was supposed to record on 4.2.  I think this narrows it down...

2017-10-17 07:21:12.850 Info App: Creating recording timer for 93df020a0031970cb2ba04b279698cb6, Bull. Timer will fire in 758.78582643 minutes
2017-10-17 07:21:12.850 Info App: Creating recording timer for ea435f297e711ed239642ffb30a50e26, This Is Us. Timer will fire in 758.78582643 minutes
2017-10-17 07:21:12.850 Info App: Creating recording timer for 4bbb53a132b61bc993d889d07398b584, DC's Legends of Tomorrow. Timer will fire in 758.78582643 minutes

Checking the DC's Legends of Tomorrow folder...

10/10/2017 "DC's Legends of Tomorrow S03E01 Aruba-Con" is the most recent recording...

https://en.wikipedia.org/wiki/List_of_Legends_of_Tomorrow_episodes#Season_3_.282017.29

I definitely do not have "Freakshow" which aired on the 17th.  "Legends of Tomorrow" failed to record on 4.2.

 

So...this collision definitely results in recordings not happening!  It's failing to rollover to the next HDHomeRun (192.168.0.161) on error!

 

 

Edit: for the first set...

2017-10-16 02:57:44.541 Info App: Creating recording timer for 1e8c083746d5216255ade5312d5721eb, Scorpion. Timer will fire in 1082.25764444833 minutes
2017-10-16 02:57:46.855 Info App: Creating recording timer for 78a8d832f1eb21a5666c8119673615d1, The Brave. Timer will fire in 1083.21907428167 minutes
2017-10-16 02:57:46.681 Info App: Creating recording timer for 74ebaa35c3faef3c48ba4207ee5205e1, The Good Doctor. Timer will fire in 1083.22197705167 minutes

"The Brave" failed to record on 4.1 with similar error messages and failure to roll over to 192.168.0.161.

 

 

Edit: Attached logs from Emby and HDHRs.

logs.zip

Edited by FordGT90Concept
Link to comment
Share on other sites

maegibbons

Hi

 

Whilst you have two tuners, HDHR recordings is broken for a few of us at the moment in a tuner overload situation .i.e. attempting to record 3 or more programs.

 

See:

 

https://emby.media/community/index.php?/topic/51815-recordings-didnt-release-tunerother-recordings-failed-to-start/&do=findComment&comment=498696

 

As I said yours is slightly different as you have two HDHR devices but these issues are probably related.

 

Krs

 

Mark

Link to comment
Share on other sites

FordGT90Concept

The errors do look very similar but the circumstances are different.  In either case, the management of tuners and devices could/should be improved.

 

Whomever has it in that thread should grab the logs off their HDHomeRun.  It's at log.html on the device.

 

 

Edit: Should be noted that this is going back 3-4 days.  If the issue was fixed in a beta since then...

Edited by FordGT90Concept
Link to comment
Share on other sites

maegibbons

No - still present in current bata.  My logs on the HDHR show the same rejected request as yours.

 

Emby HDHR tuner brokering above two channels is currently broken

 

Krs

 

Mark

  • Like 1
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...