I am getting messages in the watchdog like "FeedAPI cron processing run for 3E-05 seconds, processed 0 feeds, created 0 items, updated 0 items, expired 0 items". Still researching the problem, but wanted to post it here in case anyone else has seen the problem.

It was working fine before 5/28.

; Information added by drupal.org packaging script on 2008-01-25
version = "5.x-1.0"
project = "feedapi"
datestamp = "1201287617"

Thanks,
Aaron

Comments

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Assigned: Unassigned » aron novak
Status: Active » Postponed (maintainer needs more info)

How many rows do you have in {feedapi} table?
What do you see if you visit admin/content/feed? Do your feeds appear?
Certainly FeedAPI should process your previously added feeds.

spjsche’s picture

spjsche commented

Similar issue with feedapi not refreshing when cron runs. Never has worked since it was installed.

I have 5.x-1.2 and the watchdog shows "Executed feedapi_cron via poormanscron, took 0 sec

I have deleted/installed the feeds but to no avail.

denney’s picture

denney commented

I have the same problem as spjsche. Hasn't worked since install.

Using FeedAPI v5.x-1.2 with the Common syndication parser.

Visiting admin/content/feed shows me feeds and I can refresh them fine.

Watchdog shows "Executed feedapi_cron via poormanscron, took 0 sec." same as above.

There is 1 row, corresponding to my 1 feed in the {feedapi} table.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented

Please let me explain: http://drupal.org/node/235328
I added this fact to the release notes: http://drupal.org/node/246612
I could not do more. FeedAPI and poormanscron are simply not compatible. I don't want to argue for and against any module.
I'll start a web service for calling wget periodically for URLs for a low monthly price. ;)

aaron: do you also use poormanscron?

spjsche’s picture

spjsche commented

Apologies, I missed that in the release notes. Too keen to get it up and running.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented

Anyway, instead of poormanscron, you can use wide range of services:
http://www.onlinecronservices.com/ Some of them offers free account. In this way in a restrictive hosting environment you can do it in the regular way.

aaron’s picture

aaron commented

We're using cron the normal way. We currently have only 18 rows in {feedapi}. Feeds show up normally at /admin/content/feed. A manual refresh works fine, it's just the cron stopped working for feedapi. The cron was running, but the feedapi wasn't updating, and was giving the odd messages quoted above.

However, things mysteriously began working again, after about 2 weeks of not working. I know that's impossible to debug, and I'll be sure to keep an eye and if it happens again, try to do more troubleshooting.

aaron’s picture

aaron commented

Running cron manually, got this error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 3011 bytes) in /home/riverwired/www/sites/all/modules/feedapi/parser_simplepie/simplepie.inc on line 12852

aaron’s picture

aaron commented

I've also added some watchdogs in feedapi_cron, and this line never completes. (I put a watchdog before, and another after, but the one after never gets processed).

$counter = feedapi_invoke_feedapi('refresh', $feed, TRUE);

aaron’s picture

aaron commented

It's getting hung up somewhere in _feedapi_call_parsers, from $feed = _feedapi_call_parsers($feed, $feed->parsers, $feed->half_done ? FALSE : TRUE); in _feedapi_invoke_refresh. Sorting it out...

aaron’s picture

aaron commented

ok, more info. it's getting hung up on http://www.businesswire.com/portal/site/home/index.jsp?epi-content=XML&b... which is 554kb large. perhaps the feed is too large to process?

aaron’s picture

aaron commented
Status: Postponed (maintainer needs more info) » Fixed

in my particular case, bumping php memory up to 48MB solved the problem.

aaron’s picture

aaron commented
Title: FeedAPI cron not processing » FeedAPI cron crashes on large files
Status: Fixed » Active

so the client needs this feed, and we can't bump up memory for it. thus, we need to figure out a way to be able to parse a 500kb xml file on less than 32m. i figure i'll see if there's a way to refactor things using php5's built in xml parsing. are there other solutions available already?

mustafau’s picture

mustafau commented

Did you try http://drupal.org/project/zend_feed?

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Closed (won't fix)

I think it's about simplepie 's memory usage. aaron: you have not mentioned which parser do you use.