Anyone else been getting this when refreshing the cache since yesterday?

What version are you using and have you checked the latest release notes?

https://squarepenguin.co.uk/wiki/release293/

I am using the latest version (2.94) and reinstalled today to be sure. Followed the instructions in the release notes when I updated on release of 2.94. Was surprised that it suddenly started yesterday when it had been working fine all of July.

There does seem to be a problem. 

I got pretty much the same result. The cache does seem to be populated though.

(03-08-2015, 11:10 AM)There does seem to be a problem. 

Try opening some of those URLs in your browser. It looks like there is a problem with upstream connectivity, or perhaps with DNS.

I'm not seeing any issue my end and the URLs are opening fine for me. That might point to connectivity issues for some users.

The url's open fine in the browser.

Just for comparison these are the failures I got:

As tvfan the URLs seem to open fine but still getting the error both in the webpvr and also if refresh cache in get_iplayer window

I have just got a successful error free cache refresh after a few attempts. It could be that you might see the error if you refresh a few times.

You get those errors after each failed attempt to download a schedule file (3 total, with 20 second timeout).  Browsers are probably more forgiving than Perl, but this still points to upstream problems. The failed files aren't the same for tvfan and jfaust, which also suggests the problem is intermittent and lies between user and BBC.  If there were persistent problems at the BBC end, SP and I should get similar results.   Both tvfan and jfaust appear to be on Virgin Media, so the similar problems may not be a coincidence.

Thought I'd try a VPN to test user-2's idea re Virginmedia. Has refreshed without a problem so that would point to it being a Virginmedia issue.

Thanks

Quote:Thought I'd try a VPN to test user-2's idea re Virginmedia. Has refreshed without a problem so that would point to it being a Virginmedia issue.

Even with a VPN though you are still going through the same Virgin Media connection. As we are both seeing the same sort of errors though, I'm guessing it's a wider spread VM network issue than our connections.

Dinky also mentioned DNS earlier and if it worked through the VPN, that probably uses different DNS lookup methods to the VM methods so that sounds more like it could be the issue.

Also, while the TV cache is failing, the radio cache is refreshing with no issues.

(03-08-2015, 03:01 PM)Even with a VPN though you are still going through the same Virgin Media connection.

Sort of, you'll get an encrypted tunnel to the VPN provider over VM's network but to the web and the BBC you'll appear to 'be' the VPN. So if the issue is with VM network accessing the BBC content you'd be effectively bypassing (or tunnelling past) VM if you use the VPN.

Upshot is a VPN would effectively resolve this issue if the problem resides within VM's network.

It would have the side effect of solving a DNS issue if the two services used different DNS resolution.

If it is a DNS issue you could try changing yours yourself and seeing the results.

The same problem here in Manchester, also on a Virgin Media connection. Changing from Google to Virgin DNS servers made no difference.

I have just altered my Superhub firewall setting from medium to low. get_iplayer now appears to be working properly.

You only need to worry about these warnings if all 3 attempts to download any schedule file fail. My earlier post was unclear on this.  If you only saw 1-2 warnings for any given file, as was the case here, then the download ultimately succeeded and that file's data was cached.  The warnings indicated that some download attempts failed, but they were only a small fraction of the total.  There may be an overloaded switch or something like that upstream at Virgin, but it appears to be only a minor annoyance at the moment. To investigate further, you would need to employ a debugging proxy or network capture application like Wireshark.  You might also test with curl or wget to see if you can get similar failures with another command line downloader.

This may or may not be relevant, but I received something similar on my Mint box after the update to 2.94 what I did was to refresh a couple of single channels....did this a few times and then the cache seemed to update itself with the usual get-iplayer, no more problems since.

(04-08-2015, 11:48 AM)I have just altered my Superhub firewall setting from medium to low. get_iplayer now appears to be working properly.

That suggests the firewall itself was dropping or blocking connections. get_iplayer is only making HTTP requests on port 80, so firewall setting shouldn't matter in normal circumstances.  If you revert the setting, does the problem immediately return?  Test with:

That command works. The problem seems to be rtmdump. It hangs showing a "connecting..." message if the firewall security is medium, not when it is low.

(04-08-2015, 01:14 PM)That command works. The problem seems to be rtmdump. It hangs showing a "connecting..." message if the firewall security is medium, not when it is low.

That's a completely unrelated issue.  If you use the "medium" firewall setting you have to configure the RTMP port (1935) explicitly.  An old thread on that topic:
/thread-119.html