I think that this is "critical." CSP feeds are not updating. I have about 25 of these: Meanwhile, I will roll-back to a prior version.

Type php
Date Monday, October 13, 2008 - 14:08
User Anonymous
Location http://tips-q.com/cron.php
Referrer
Message fclose(): supplied argument is not a valid stream resource in /var/www/queer/sites/all/modules/feedapi/parser_common_syndication/parser_common_syndication.module on line 139.
Severity error
Hostname 65.98.66.188

Please note that I never upgraded from 1.2 to 1.3.

Comments

eyecon-1’s picture

eyecon-1 commented

It's a trio of errors on each CSP feed refereshed:

1. Type php
Date Monday, October 13, 2008 - 14:15
User Anonymous
Location http://tips-q.com/cron.php
Referrer
Message fopen(/5959b8e10df059570d07f5478762361d) [function.fopen]: failed to open stream: Permission denied in /var/www/queer/sites/all/modules/feedapi/parser_common_syndication/parser_common_syndication.module on line 137.
Severity error
Hostname 65.98.66.188

2. Type php
Date Monday, October 13, 2008 - 14:15
User Anonymous
Location http://tips-q.com/cron.php
Referrer
Message fclose(): supplied argument is not a valid stream resource in /var/www/queer/sites/all/modules/feedapi/parser_common_syndication/parser_common_syndication.module on line 139.
Severity error
Hostname 65.98.66.188

3. Type php
Date Monday, October 13, 2008 - 14:15
User Anonymous
Location http://tips-q.com/cron.php
Referrer
Message fwrite(): supplied argument is not a valid stream resource in /var/www/queer/sites/all/modules/feedapi/parser_common_syndication/parser_common_syndication.module on line 138.
Severity error
Hostname 65.98.66.188

TKS’s picture

TKS commented

This was happening to me too -- fresh install of Drupal 5.11, with FeedAPI 5.x-1.4 modules (FeedAPI, FeedAPI-node, FeedAPI-inherit, FeedAPI Aggregator and Common Syndication Parser) the only contrib items loaded or activated.

In my case, it WAS creating the nodes for each story (I was creating full-blown feeds, not light-weight, aggregator style ones), but I'd get the same set of error messages that eyecon mentions above.

Oddly, when I turned on Clean URLs, the problem went away.

pmusaraj’s picture

pmusaraj commented

I have this issue as well, and on my Drupal I have Clean URLs on, yet the problem persists.

eyecon-1’s picture

eyecon-1 commented

Aron to the white courtesy phone please. Any progress on this issue?

aron novak’s picture

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

1) Please make sure that you have a writable and sane file directory. (admin/settings/file-system). Maybe the problem is this.
2) If the 1) is not the problem, please install devel module and execute: dprint_r(_parser_common_syndication_sanitize_cache()); . The output of this could be important.
3) If the output of 2) is FALSE, you can create manually a "parser_common_syndication_cache" directory under your files directory and give the php user right to write it. Then also, you can check if the problem has gone away.

eyecon-1’s picture

eyecon-1 commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Thanks. That pointed me in the right direction. The cache permissions were 600. I changed them to 666 and everything is fine.

adub’s picture

adub commented
Status: Closed (fixed) » Active

Not sure if this should bea separate issue but I seem to be having a lot of cron timeouts since upgrading from 5.x-1.2. Using simplepie, simplepie_cache perms are 755 with webserver as the owner and step 2 above returns 'files/simplepie_cache'.

adub’s picture

adub commented
Status: Active » Postponed (maintainer needs more info)

Hmm... unable to clearly replicate this on another site with more feeds and more frequent cron. There was a cron hiccup but seems to have corrected itself. The site with the problem just has a couple of fairly infrequent feeds, just wondering if _not_ adding nodes could cause something to hang. Will continue to look through other modules in the meantime to see if I can get to the bottom of it.

(Leaving semi-open in case anyone has any ideas about feedapi as it seemd to affect a couple of others here.)

adub’s picture

adub commented
Status: Postponed (maintainer needs more info) » Active

Spoke too soon, the other site now has cron errors. So we can say this problem has been replicated. (Other upgrades performed on both - drupal core, CCK, Devel, Calais.)

Update: switched off the module and cron is back to normal so it looks like this is definitely feedapi-related. I'm thinking this could well be time related as there seemed to be increasing numbers of cron error messages after a while regardless of the timing of cron jobs as if there was some kind of feedback loop. A couple of possible factors: I am on php 5.1.2 which has more primitive timezone handling and the clocks went back by an hour around the time this started.

adub’s picture

adub commented
Status: Active » Closed (fixed)

(think I've tied this issue to feedapi workflow module)