BAlGaInTl 279 Posted March 16, 2017 Share Posted March 16, 2017 Oops... My Live TV is dead after update to server 3.2.8.0 There don't seem to be any channels to map. I tried re-initializing in the HDHomerun ap, re-syncing the guide data, and trying to re-map channels. I'm using Docker and Legacy (HDHR3-US) tuners. Here is the log file. EmbyLogLiveTVDead.txt Link to comment Share on other sites More sharing options...
Luke 37112 Posted March 16, 2017 Share Posted March 16, 2017 From 3.2.7 to 3.2.8 is merely a version increment without any code changes, FYI. Link to comment Share on other sites More sharing options...
BAlGaInTl 279 Posted March 16, 2017 Author Share Posted March 16, 2017 From 3.2.7 to 3.2.8 is merely a version increment without any code changes, FYI. Well darn. Something certainly happened... glad I haven't shut down my tvheadend server yet. Link to comment Share on other sites More sharing options...
KeyserSoze1 2 Posted March 16, 2017 Share Posted March 16, 2017 Bug found! @@Luke should have it fixed soon. Link to comment Share on other sites More sharing options...
Solution Luke 37112 Posted March 16, 2017 Solution Share Posted March 16, 2017 Thanks. The short answer is we're caching data for just a little bit longer than we should. It has nothing to do with the release. Although that is the downside of doing a release at all, everything is always blamed on the release. In any event, your issue should resolve itself, within some period of time less than 24 hours, but then you may experience it again 24 hours from there. There is a window of time each 24 hours where you may see it, and the rest of the day it will be fine. Until we have a new release with the caching shortened, you can work around it by deleting this folder under server program data before the guide refresh runs: /cache/httpclient As well as restarting the server before the refresh runs. This only applies to legacy HD Homerun tuners so those are the only users that will see this. 1 Link to comment Share on other sites More sharing options...
BAlGaInTl 279 Posted March 16, 2017 Author Share Posted March 16, 2017 Thanks. The short answer is we're caching data for just a little bit longer than we should. It has nothing to do with the release. Although that is the downside of doing a release at all, everything is always blamed on the release. In any event, your issue should resolve itself, within some period of time less than 24 hours, but then you may experience it again 24 hours from there. There is a window of time each 24 hours where you may see it, and the rest of the day it will be fine. Until we have a new release with the caching shortened, you can work around it by deleting this folder under server program data before the guide refresh runs: /cache/httpclient As well as restarting the server before the refresh runs. This only applies to legacy HD Homerun tuners so those are the only users that will see this. That seems to have fixed the problem. Will this affect scheduled recordings? Am I better off keeping TVHeadend for show/series recording for the mean time? Link to comment Share on other sites More sharing options...
Luke 37112 Posted March 16, 2017 Share Posted March 16, 2017 No, it will only affect the refresh guide process. Link to comment Share on other sites More sharing options...
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