All feed fetch attempts are currently failing
with google.appengine.runtime.apiproxy_errors.ResponseTooLargeError: The
response from API call urlfetch.Fetch() was too large. The limit is
apparently 1MB or 32MB (it was increased at some point) and the feeds the
hub is trying to fetch are way below that.

Nothing recently has changed in the fetching code. I also trying rolling
back to the last version (pushed 2 weeks ago) with no success.

I'm still trying to figure out what's going on.

Roman.

On Tue, Jul 10, 2012 at 9:06 PM, Julien Genestoux <
[email protected]> wrote:

> I'm with Mario here, looks like there is a big problem with the blogger
> feeds.
> We have reduced our polling period down to 15 mins for these as well, but
> we are being server cached cnotent as well...
> Thanks
>
>
>
> On Tue, Jul 10, 2012 at 7:42 PM, Mario Menti <[email protected]> wrote:
>
>>  Roman,
>>
>> further to this, there appear to be a very large number of feeds that
>> have stopped working, we're getting increasing numbers of problem reports,
>> and looking at our logs, it appears the number of new post notifications
>> received today is a very small percentage of what we usually get.
>>
>> Thanks,
>> Mario.
>>
>>  On 10/07/2012 16:16, Roman wrote:
>>
>> Hi YC,
>>
>>  This might be related to a problem I've been trying to fix today. Could
>> you post a couple of feed topics that are supposed to work for you but
>> don't?
>>
>>  Roman.
>>
>> On Tue, Jul 10, 2012 at 3:59 PM, YC <[email protected]> wrote:
>>
>>> Hi there, anyone else not receiving updates from blogger.com blogs
>>> now?
>>> My web app is not getting notification from all of my subscribed blog in
>>> pubsubhubbub.appspot.com.
>>>
>>>  All of my subscribed blog In Publisher Diagnostics (
>>> https://pubsubhubbub.appspot.com/publish) have the following result:
>>>  Topic Details - http://devhubbub.blogspot.com/feeds/posts/default
>>> Fetch from domain: BLOCKED
>>>
>>>  My web app is able to get notification from superfeedr but not
>>> pubsubhubbub.appspot.com now. This issue just started today. Anyone
>>> know how to fix this?
>>>
>>
>>
>>
>

Reply via email to