By Anonymous (not verified) on

Installed drupal and set it up with no problems. However when creating news feeds, I noticed that nothing seemed to be happening... The admin error log was recording update errors, so i removed the @error supressor on the fopen function in import.module (the most obvious place to look). Here's what i found:

warning: php_hostconnect: connect failed in htdocs/modules/import.module on line 174.

warning: fopen("http://www.drop.org/module.php?mod=node&op=feed", "r") - Bad file descriptor in /modules/import.module on line 174.

Any ideas what might be causing this? Is it something to do with certain things being disabled in php4? anything i can fix within the drupal module code itself? Having working news feeds would be awesome...

Comments

dries’s picture

dries commented

If you are using PHP 4.0.6, it might be this PHP bug.

Ian Ward’s picture

Ian Ward commented

On both a 4.2 and 4.3.1 Drupal installation I receive errors when I add an RSS feed to the site and then select to update the feed. Below is the error on the 4.3.1 version of Drupal:

"warning: php_network_getaddresses: getaddrinfo failed: Name or service not known in /var/www/idpsanew/modules/import.module on line 313.

warning: fopen("http://xml.newsisfree.com/feeds/60/860.xml", "r") - Bad file descriptor in /var/www/idpsanew/modules/import.module on line 313."

I've tried several valid feeds, but receive the same error.
Apache 2 and PHP 4.3 are used. I am also using the 'poormanscron' module. Any ideas?

dries’s picture

dries commented

I just tried parsing that feed and I don't get any warnings/errors. This might be caused by your PHP configuration -- maybe your hosting company forbids you to resolve hostnames?

Ian Ward’s picture

Ian Ward commented

Thank you. DNS is not configured properly on the server of the installations, thus it would be unable to resolve hostnames - likely the problem. I suppose the above user could also have had problems with import module because of temporary DNS issues somewhere? Seems likely not to be a Drupal module issue. Thanks again.