Closed (won't fix)
Project:
FeedAPI
Version:
5.x-1.2
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 May 2008 at 17:43 UTC
Updated:
17 Dec 2008 at 15:32 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedCan you please check if you have the following set in a individual feed:
Refresh feed on creation - checkmarked
Update existing feed items - checkmarked
Pause automatic feed update - unchecked
And then see if the feed refreshes on cron?
You might want different settings later, but it should run cron as far as I know.
Comment #2
goodwillhinton commentedYep, I checked those items again and they are all checked appropriately.
Is is ok to use poormanscron for this?
Here is what I am seeing in my log:
Details
Type cron
Date Wednesday, May 7, 2008 - 6:30pm
User Anonymous
Location http://newtmt.goodwillhinton.com/
Referrer
Message Executed feedapi_cron via poormanscron, took 0 sec..
Severity notice
Hostname 208.66.64.4
Operations
I'm wondering if the fact that it is running as Anonymous user is the problem. I also notice that it took 0sec. So that is obviously a problem too.
I'm really stumped over this.
Comment #3
Anonymous (not verified) commentedAs far as I know (I have never had problems with it.)
I have the same thing and it is working.
Do you have a lot of other modules running? Maybe it is not getting the cron time. You can change this in FeedApi setting as well. Maybe that will work.
Which parser are you using?
Comment #4
goodwillhinton commentedI do have a lot of other modules running. Here is what the log looks like during a cron run:
cron 05/07/2008 - 11:05pm Cron run completed (via poormanscron). Anonymous
cron 05/07/2008 - 11:05pm Executed feedapi_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed votingapi_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed update_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed trigger_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed trackback_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed system_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed statistics_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed simplenews_cron via poormanscron, ... Anonymous
cron 05/07/2008 - 11:05pm Executed search_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed poll_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed ping_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed persistent_login_cron via ... Anonymous
cron 05/07/2008 - 11:05pm Executed node_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed image_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed googleanalytics_cron via ... Anonymous
cron 05/07/2008 - 11:05pm Executed friend_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed filter_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed event_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed dblog_cron via poormanscron, took ... Anonymous
cron 05/07/2008 - 11:05pm Executed aggregator_cron via poormanscron, ... Anonymous
It appears that every one of these show only 0sec. I checked the FeedAPI setting and have it set to 75%. Most of these other cron runs appear to be for core modules.
Comment #5
goodwillhinton commentedActually I took a closer look....it appears that update_cron is working and took 15sec....but all of the other cron jobs show 0sec.
Comment #6
Anonymous (not verified) commentedAggregator and FeedAPI running together: I am not sure they should or can. That might be causing your problem. Otherwise I wouldn't know. But it should run on 6.2 afaik.
Good luck
Edit: Try running manual cron a couple of times after each other. See if that helps. Consider finding more information on the FeedAPI/ Aggegrator combination first though.
Comment #7
cercamon commentedI have the same problem but in Drupal 5.7.
I only can refresh manually but I neen to do automaticaly. I also have:
Refresh feed on creation - checkmarked
Update existing feed items - checkmarked
Pause automatic feed update - unchecked
Any idea ?
Thanks in advance
Comment #8
aron novakWell, the real problem is poormanscron:
http://drupal.org/node/235328
I reported here a bug, I have never received any response.
cron_semaphore is an important part of Drupal core cron, it cannot be ignored by poormanscron.
Sorry, at the moment, FeedAPI and poormanscron are not compatible with each other.
I set this ticket to "won't fix", because i won't create a workaround for poormanscron.
Comment #9
abqaria commentedanyone solved the problem of cron and updating feeds
Comment #10
aron novakNo. poormanscron maintainer didn't accept my patch.
I really suggest you to use an outside hosted cron service, some of them are free, for example:
http://www.cronjobs.org/index.php
http://hostedcron.com/
Comment #11
aron novakComment #12
abqaria commentedyes i used cron on my server and it worked
Comment #13
netentropy commentedso is the consensus that poormanscron and FeedAPI do not work together?
How does this make sense since all poormascron does is run cron.php correct?
Comment #14
bcobin commentedHas anyone figured out a workaround or a fix for this? With all the development happening with FeedAPI, I would think lots of users are running into the FeedAPI/Poormanscrons issue.
I'll make a support request in the poormanscron issues queue - thanks!
Comment #15
gpk commentedFor those following along at home, poormanscron could do with a maintainer to fix this problem in the 5.x branch. Amy volunteers?
Note that if you run your site on 6.x and use poormanscron 6.x-1.x-dev then it *has* been fixed.
More info: #119094: Use drupal_cron_run() (fixes FeedAPI compatibility problem and multiple simultaneous runs).