Posted by emcee0 on November 11, 2009 at 12:10am
Hello everyone, I'm a long time lurker and first time poster. I've run into a small issue with my first drupal load balanced setup. Currently I have a ServerIron XL performing load balancing using a virtual IP. Behind the virtual IP are 2 web servers with drupal installations. What I've noticed is that when loading my Drupal instance into this environment, the status page will alert that the HTTP Request Status failed. Initially I thought it was a configuration issue with Drupal or with my Apache settings but I loaded the DB and files on to my staging server which has an identical configuration and it's not giving me any alerts. Anybody have any ideas?
Comments
I just saw this error last
I just saw this error last week.
On the status page the HTTP Request ability is tested by seeing if Drupal can download it's own front page. Depending on your configuration the head servers may not be able to query it's own domain (not sure about the exact cause). You can confirm this by running wget from the command line on one of the heads:
wget http://mydomain.com
You should also see on the status page that Drupal was able to successfully connect to drupal.org to get module update information. If that is not the case then you do in fact have something that prevents you from connecting to the outside world. It's only then that you need to investigate further.
--
Dave Hansen-Lange
Director of Technical Strategy, Advomatic.com
Pronouns: he/him/his
Ok here's what I tried so
Ok here's what I tried so far.
From both individual web front end server when I do a wget on http://mydomain.com it will not download the index file.
From both individual web front end server when I do a wget on http://google.com it will download the index file.
From a seperate server not hosting the website, when I do a wget on http://mydomain.com it will download the index file.
I'm thinking this is some sort of routing issue.
Hosts
Try adding your domain pointed to localhost in /etc/hosts.
Ken Winters