Ok, I've never had a problem like this before, but with a brand new installation of drupal 4.6.2 I'm getting the following errors in my admin log when trying to update some rss feeds:
Failed to parse RSS feed slashdot.org: 13 Permission denied.
fsockopen() [function.fsockopen]: unable to connect to slashdot.org:80 (Permission denied) in /var/www/html/drupal/includes/common.inc on line 268.
The rss feeds I'm trying to update are:
http://www.theserverside.com/rss/theserverside-rss2.xml
These exact same feeds are working in an older installation (4.6.0) I have on another server, so I know that they should work with what I've got. But they're not :(
Has anyone ever seen this before or have any idea why the core library is trying to say that it can't connect to port 80 on these sites? Thanks in advance for any replies whatsoever.
Comments
Server IP may be banned
How often are you pulling the feed with the aggregator? You may be pulling it too often. See also: Slashdot's FAQ on RSS feed banning.
(Username formerly my full name, Richard Eriksson.)
Feed refresh set for 6 hours
Thanks for the info. I had no idea that sites were starting to ban specific IP addresses for simply pulling an extremely small file from their servers to often (sheesh). Nonetheless, my settings only pull any one of the feeds I've setup once every 6 hours. If I try to manually update the feed through the aggregator admin area I get the same error as well.
The strange thing is that I've even setup a feed source from my company's web site and it also receives the exact same permission denied error. Either there is something strange about the topology of the network my server is setup on or there is something wrong with this code in common.inc. As far as the network setup goes, this server is just a desktop pc (running fedora core 4) and hooked into the company's internal network behind the firewall. This exact same setup has worked forever with an installation of 4.6.0, pulling the exact same RSS feeds, so you can see why I'm baffled here.
Does anyone know of any kind of firewall or local NIC settings that could cause this?
Nevermind, I figured it out
In Fedora Core 4 (versus 2, which I had on the other system) I was able to turn off SELinux to fix the problem. I basically just turned if off completely instead of trying to figure out what specific option was causing the denial. This is ok in my case because this box is only going to be used internally for a small group of people and we still have the firewall on to limit what ports are open for access.
I got the same situation
Hi, I have a hosting provider, how can i solve the same problem, is there some configuration issue that I have to work it out with the provider or it is something I can do? thanks for any help
Same problem
I am having the same problem and have a hosting provider as well. Any help would be appreciated.
-Thad