Luke 37251 Posted November 12, 2015 Share Posted November 12, 2015 I'm pretty sure I found the problem, thanks. it's resolved for the next release. Thank you for helping to chase it down. Link to comment Share on other sites More sharing options...
venom986 2 Posted November 12, 2015 Share Posted November 12, 2015 (edited) I swapped to windows with drivepool instead of freenas - for several reasons, this being one of them. Sent from my iPhone using Tapatalk Edited November 12, 2015 by venom986 Link to comment Share on other sites More sharing options...
Snapper 20 Posted November 12, 2015 Author Share Posted November 12, 2015 I'm pretty sure I found the problem, thanks. it's resolved for the next release. Thank you for helping to chase it down. Good to hear Luke. Thanks for the update. Link to comment Share on other sites More sharing options...
Snapper 20 Posted November 17, 2015 Author Share Posted November 17, 2015 I'm pretty sure I found the problem, thanks. it's resolved for the next release. Thank you for helping to chase it down. Hi Luke, I updated to 5781.2, and it seems to have resolved some of the issue. I am now getting guide data for several channels. There are a few that I am not. Some of them are due to SD not having guide data for those channels, but some of the others are due to an error. I posted the log from the guide update for your review. I also asked rkulagow if he can check the SD side. guide_update_11-17-15_5781-2.log Thanks, Brian Link to comment Share on other sites More sharing options...
Luke 37251 Posted November 17, 2015 Share Posted November 17, 2015 I do stand by my original assessment of networking problems on your machine. The only thing my fix did was explicitly specify the dates we want from SchedulesDirect instead of taking the default 14, that way if you specify 3 days of guide data we're only downloading 3 days. This change has made the connection timeouts less likely to happen, but they could still happen and this log is showing that. Some of the requests in this log are still using the default 20 second timeout length, I can bump those up just like I did the others and that will make this less likely to happen. I am guessing there is nothing for rkulagow to look at and that he is going to come back and say that everything looks fine from the SD side. Link to comment Share on other sites More sharing options...
Snapper 20 Posted November 18, 2015 Author Share Posted November 18, 2015 You are correct. Jumbo frames was causing issues for whatever reason. I didn't notice any issues with other services, but all seems well now. Thanks for your help. 1 Link to comment Share on other sites More sharing options...
Luke 37251 Posted November 18, 2015 Share Posted November 18, 2015 Well done 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