With FeedAPI enabled, including the feed->node and element mapper, cron is not able to complete on my site. I have 9 feeds which are brought into nodes upon updating. I verified that it was FeedAPI causing the cron problems by modifying module.inc to report module calls and returns. FeedAPI never returns and causes cron to cease working.

I'm not sure what other information I can provide but this is bringing my site to a halt.

Thanks

Comments

mstef’s picture

Also, it seems that whenever I run cron manually, there are no problems - not yet at least. What does that mean?

mstef’s picture

Yea - only happens when I run cron with crond. Tried with both wget and php - same result.

Weird

alex_b’s picture

Status: Active » Closed (duplicate)
mstef’s picture

that's not what is happening...

it doesn't return at all. i have to kill the cron process, delete the semaphor, and run it manually.

simon_s’s picture

Exactly the same problem with 6.x-1.7-beta1. When FeedAPI parses to many feeds at once (in my case about 20 feeds) it causes the cron to hang up. Only deleting the cron semphore and serveral manual cron re-runs help.

Is it planned to implement a limit setting, e.g. that you can tell FeedAPI only to parse max. 10 feeds at one cron run?

momper’s picture

only as a small notice and excursion (i don't know a place where to put elsewhere):

- we have got a dedicated, managed server with a default memory_limit of 60MB and a short max_execution_time
-> we had trouble to run the cron with 250 feeds

- with a php.ini in the drupal root folder we increased the max_execution_time + the memory_limit for drupal in general
-> now it works, if we start the cron manually (not by crontab)
-> it does not work with the crontab cron, because he has other memory_limits by the server and we thought it was not possible to increase it ...

... but we now use PHP-Cli (Shell):

example.sh:

#!/bin/bash
php5 -c /www/xxx.xx/cms/scripts/special-php.ini -f /www/xxx.xx/cms/cron.php

... and call a special php.ini with a higher max_execution_time + the memory_limit then the rest of the drupal installation ...
-> now it works with the crontab cron

... i don't know if this is a robust solution - i will follow and report ...