Boost comes with a module called "Boost Crawler". Boost crawler demands another module called "HTTP Parallel Request Library"

with Boost and these 2 mentioned modules activated i am getting that error code in the Status repport :

HTTPRL - Core drupal_http_request()
Your system or network configuration does not allow Drupal to access web pages. This could be due to your webserver configuration or PHP settings. Debug info:
Array
(
    [0] => Array
        (
            [count] => 1
            [time] => 6286.39
            [mode] => 2
            [blocking] =>
            [url] => http://46.16.233.27/admin/httprl-test?key=008a9a1bee68f9f5be28276cd6821090&id=httprl_3d0a9f7a0f6d1c8069e619a41a05b7fa
        )
    [1] => Array
        (
            [count] => 1
            [time] => 6310.36
            [mode] => 2
            [blocking] =>
            [url] => http://gymteam.metabolit.se/admin/httprl-test?key=008a9a1bee68f9f5be28276cd6821090&id=httprl_7285cbd7ea9beea83b3a8d32187399b2
        )
    [2] => Array
        (
            [count] => 1
            [time] => 6153.21
            [mode] => 2
            [blocking] => 1
            [url] => http://gymteam.metabolit.se/admin/httprl-test?key=008a9a1bee68f9f5be28276cd6821090&id=httprl_c14050e6edf700b514e647b02b09a48a
        )
    [3] => Array
        (
            [count] => 1
            [time] => 6128.05
            [mode] => 1
            [blocking] =>
            [url] => http://gymteam.metabolit.se/admin/httprl-test?key=008a9a1bee68f9f5be28276cd6821090&id=httprl_9255cad18c77bf726d0230ee829faac6
        )
)
For more info go here: "HTTP request status Fails" error

what is wrong?

Comments

Project:Boost» HTTP Parallel Request & Threading Library
Version:7.x-1.0-beta2» 7.x-1.x-dev
Component:Cron Crawler» Code

This seems specific to httprl, so I will move it to their issue queue.

If I understand correctly, it seems that your server does not allow outgoing http connections. Some hosting providers block outgoing connections to avoid unsecure applications from spamming the web. Another way to confirm, is if Drupal's "update" module can check for new versions of your installed modules.

Checking for updated versions of modules, themes or drupal core itself has never been a problem on that server. been using same hosting provider for quite a few years now ...

At the end of this message there is a link in that sentence "For more info go here: "HTTP request status Fails" error" taking you to

http://drupal.org/node/588186

In that thread there are several methods listed to resolve that ... like

1 - installing the module "http_request_fail_reset"
or
2 - adding a certain line of code at the end of the setting.php file
or
3 - adding the domain to the list of host addresses

method 1: there is no drupasl version of this module
method 2: does not help not help in my case either
method 3: does not help in my case either

The problem I have too, but never found a solution.

HTTPRL is testing to see if it can make a connection to its self. For some reason this is not working on your server (it is timing out). The boost crawler won't work as a result because it can not access the server it's hosted on via http requests.

The comments on http://drupal.org/node/588186 is where the real troubleshooting is happening. There are some good recommendations in there that might fix the issue.

Questions for the people who have this issue:
Who are you using for your hosting?
If you have shell access on the server that is throwing this error what happens when you wget your druapl site?

how would a "wget" commant in command line to a drupal site look like

> wget http://urlofmysite.com

or something like that? would that be correct?

That is correct :)

Running wget http://example.com
Outputs this to the command line.

--2012-11-10 18:32:39--  http://example.com/
Resolving example.com... 192.0.43.10
Connecting to example.com|192.0.43.10|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.iana.org/domains/example/ [following]
--2012-11-10 18:32:40--  http://www.iana.org/domains/example/
Resolving www.iana.org... 192.0.32.8
Connecting to www.iana.org|192.0.32.8|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'
    [ <=>                                                                                                 ] 2,966       --.-K/s   in 0s
2012-11-10 18:32:40 (579 KB/s) - `index.html' saved [2966]

similar result here (unfortunately text from terminal in swedish, do i need to translate) ?

# wget http://name.of.my.domain.com
--2012-11-11 01:07:06-- http://name.of.my.domain.com/
Slår upp name.of.my.domain.com... 46.xx.yyy.zz
Ansluter till name.of.my.domain.com|46.xx.yyy.zz|:80... ansluten.
HTTP-begäran skickad, väntar på svar... 302 Found
Adress: https://name.of.my.domain.com/ [följer]
--2012-11-11 01:07:07-- https://name.of.my.domain.com/
Ansluter till name.of.my.domain.com|46.xx.yyy.zz|:443... ansluten.
HTTP-begäran skickad, väntar på svar... 200 OK
Längd: ospecifierat [text/html]
Sparar till "index.html".

[ <=> ] 39 596 --.-K/s på 0,03s

2012-11-11 01:07:08 (1,09 MB/s) - "index.html" sparad [39596]

@bavarian
The interesting thing is you redirect all http traffic to https. This shouldn't cause a timeout though. On your status report admin/reports/status what does it say for HTTPRL? Do you get 4 messages with each one of them taking 6+ seconds?

You also can try setting an IP address and seeing if that fixes the issue admin/config/development/httprl

Funny, since there was no "support" for my issue here I had this module enabled for a couple of weeks now. Now when response started here in this issue, i re-enabled the module and NOW it is not generating that error message in the status report any longer .... for unknown reasons !

@bavarian
My best guess at to what could be causing the issue you're describing has something to do with a firewall. Hopefully it doesn't happen again.

Status:Active» Closed (cannot reproduce)

reopen if this happens again

nm

I do not know if there is a way to avoid this, but after messing around with this for an hour I ran across a not so closely related issue where it was the fact that they were in maintenance mode that was causing an http request to fail. So I gave it a try. Dropping out of maintenance mode fixed the problem. It appears that the http request is being rejected, probably because it is not authenticated in some way, when in maintenance mode.

I should have reopened the issue according to #12. See #14.

Title:HTTPRL - Core drupal_http_request() error in Status repportHTTPRL - Core drupal_http_request() error in Status repport (maintenance mode)
Status:Closed (cannot reproduce)» Active

This check happens in _menu_site_is_offline(). Thinking about not runing the check if the site is in maintenance mode.

Status:Active» Fixed
StatusFileSize
new915 bytes

This patch has been committed to 6.x & 7.x. Thanks for the feedback on this one :)

I've tested the dev release with #18 on both a test and production system. Looks good. Thanks.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.