Karyudo9 1 Posted March 16, 2019 Posted March 16, 2019 I'm a Lifetime Premium subscriber running Emby as a Docker under unRAID, with an HD Homerun device. Today I went to add a new scheduled recording, and I was dismayed to see that there was no guide info. I'm seeing a completely empty screen: no channels, no logos, no info, period. A few months ago, everything worked perfectly with Schedules Direct. Now, neither Schedules Direct nor new, native Emby guide info (yes, I've been reading the forum) is showing up for Live TV or DVR. I've chugged through several threads here that ultimately didn't help. Can I please get some help to troubleshoot this? This shouldn't be so difficult, especially on a system that I had working flawlessly. What am I doing wrong?
Luke 42085 Posted March 16, 2019 Posted March 16, 2019 Hi there, can you please go over a specific example? thanks !
Karyudo9 1 Posted March 16, 2019 Author Posted March 16, 2019 That *is* specific! Premiere user, unRAID, Docker, HDHR, used to work perfectly with Schedules Direct, now doesn't work at all with either SD or new Emby guide info... What else do you think would make this more specific than what I've already posted?! Can you please be more specific? Thanks!
Karyudo9 1 Posted March 16, 2019 Author Posted March 16, 2019 From the log (embyserver.txt): 2019-03-16 14:16:50.905 Error App: Error getting channel list *** Error Report *** Version: 4.0.2.0 Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /config -ffdetect -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartexitcode 3 Operating system: Unix 4.18.20.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 16 Program data path: /config Application directory: /usr/lib/emby-server System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: No route to host ---> System.Net.Sockets.SocketException: No route to host at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken) --- End of inner exception stack trace --- 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.HdHomerun.HdHomerunHost.GetModelInfo(TunerHostInfo info, Boolean throwAllExceptions, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.HdHomerun.HdHomerunHost.GetLineup(TunerHostInfo info, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.HdHomerun.HdHomerunHost.GetChannelsInternal(TunerHostInfo info, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.BaseTunerHost.GetChannels(TunerHostInfo tuner, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.BaseTunerHost.GetChannels(Boolean enableCache, CancellationToken cancellationToken) Source: System.Net.Http TargetSite: Void MoveNext() 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.HdHomerun.HdHomerunHost.GetModelInfo(TunerHostInfo info, Boolean throwAllExceptions, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.HdHomerun.HdHomerunHost.GetLineup(TunerHostInfo info, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.HdHomerun.HdHomerunHost.GetChannelsInternal(TunerHostInfo info, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.BaseTunerHost.GetChannels(TunerHostInfo tuner, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.BaseTunerHost.GetChannels(Boolean enableCache, CancellationToken cancellationToken) InnerException: System.Net.Sockets.SocketException: No route to host Source: System.Private.CoreLib TargetSite: Void Throw() at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken) 2019-03-16 14:16:50.905 Info App: Refreshing guide with 14 days of guide data 2019-03-16 14:16:50.907 Info TaskManager: Refresh Guide Completed after 0 minute(s) and 6 seconds 2019-03-16 14:16:50.907 Info TaskManager: ExecuteQueuedTasks 2019-03-16 14:16:55.807 Info HttpServer: HTTP GET http://192.168.1.201:8096/emby/Users/b8****************************f8. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36 2019-03-16 14:16:55.809 Info HttpServer: HTTP Response 200 to 192.168.1.206. Time: 1ms. http://192.168.1.201:8096/emby/Users/b8****************************f8 2019-03-16 14:16:55.809 Info HttpServer: HTTP GET http://192.168.1.201:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36 2019-03-16 14:16:55.809 Info HttpServer: HTTP GET http://192.168.1.201:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36 2019-03-16 14:16:55.810 Info HttpServer: HTTP Response 200 to 192.168.1.206. Time: 1ms. http://192.168.1.201:8096/emby/System/Configuration 2019-03-16 14:16:55.811 Info HttpServer: HTTP Response 200 to 192.168.1.206. Time: 2ms. http://192.168.1.201:8096/emby/System/Logs 2019-03-16 14:16:59.029 Info HttpServer: HTTP GET http://192.168.1.201:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36
Luke 42085 Posted March 17, 2019 Posted March 17, 2019 Is your hdhr down or disconnected from the network, or did it's ip address change? It looks like the server is unable to pull the channel list from your hdhr.
Solution Karyudo9 1 Posted March 17, 2019 Author Solution Posted March 17, 2019 You're right: it looks like the IP of the HDHR changed. I'd forgotten that because Emby originally didn't find the HDHR, I had to set it up (including putting in the IP) manually. And I guess at some point it was assigned a new IP: it was x.122; now it's x.123. Updated that, and now the grey bar sticks around longer than 6 seconds, and starts to turn green as it gets channels. Once that's done, everything works. Thanks for the diagnosis. (I guess I should update my router to assign a static IP to the HDHR devices, so this sort of thing doesn't happen again....) 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now