By tburton on

I was installing some contributed 6.6 modules to my recently upgraded 6.6 installation when my host (SiteGround) suspended my account because my site was eating their shared server resource. Initially they wanted to ban me from their shared servers and insisted I move to a dedicated server. After much haggling they have agreed to let me back on. The log recorded this as the problem: 67.15.XXX - - [29/Oct/2008:17:21:59 -0500] "GET /admin/reports/request-test HTTP/1.0" 503 1511 "-" "Drupal (+http://drupal.org/)" . Any thoughts what this means and what module is causing the grief?

⋅ Categories: Drupal 6.x

Comments

tburton’s picture

tburton commented

Here is a fix for this problem http://collectiveidentity.net/node/13/, Is this something to refer back to the core developers?

yelvington’s picture

yelvington commented

If a simple HTTP request kills your shared server, you have much bigger problems.

The code in question doesn't do ANYTHING that would be "eating their shared server resource." It simply attempts to verify that HTTP requests are possible from your server.

If they're not possible, then there's no point in trying again, so it sets a system flag that causes future attempts to be skipped. This disables the aggregator from fetching RSS feeds and the update checker from fetching status reports from Drupal.org. The net effect is to lighten the load on the server, not add to it.

In the other link you provided, the key point you missed was that the hosting company (Godaddy free hosting) was adding Javascript to every pageview. By adding Javascript to Drupal's self-test page, it broke the test. It might be argued that Drupal's self-test process should be more robust, but the fault was clearly with Godaddy.