Home arrow Site Administration arrow Page 3 - Configuring Load-Balanced Clusters

Testing the System continued - Administration

In this conclusion to a two-part series on load-balanced clusters, you'll learn how to configure the load balancer and test the system. This article is excerpted from chapter seven of Linux System Administration, written by Tom Adelstein and Bill Lubanovic (O'Reilly, 2007; ISBN: 0596009526). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.

TABLE OF CONTENTS:
  1. Configuring Load-Balanced Clusters
  2. Testing the System
  3. Testing the System continued
  4. Adding HA to LB
By: O'Reilly Media
Rating: starstarstarstarstar / 1
May 08, 2008

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

We’ll also check the system logs on lb:

  # tail /var/log/syslog
 
Sep 11 22:59:45 mail ldirectord[8543]: Added virtual server:
  70.253.158.44:80
  Sep 11 22:59:45 mail ldirectord[8543]: Added fallback server: 127.0.0.1:80
  ( x 70.253.158.44:80) (Weight set to 1)
  Sep 11 22:59:45 mail ldirectord[8543]: Added real server: 70.253.158.41:80
  ( x 70.253.158.44:80) (Weight set to 1)
  Sep 11 22:59:45 mail ldirectord[8543]: Deleted fallback server: 127.0.0.1:80
  ( x 70.253.158.44:80)
  Sep 11 22:59:46 mail ldirectord[8543]: Added real server: 70.253.158.45:80
  ( x 70.253.158.44:80) (Weight set to 1)

Back on web1 and web2, check the Apache access logs. The director should demand director.html everycheckintervalseconds:

  70.253.158.44 - - [11/Sep/2006:22:49:37 -0500] "GET /director.html HTTP/1.1"
  200 11 "-" "libwww-perl/5.803"
  70.253.158.44 - - [11/Sep/2006:22:49:39 -0500] "GET /director.html HTTP/1.1"
  200 11 "-" "libwww-perl/5.803"

In your browser, go to the virtual site URL http://70.253.158.42/which.html, and you should see either:

  I'm web1

or:

  I'm web2

If the load balancer is broken or one of the web servers is down, you might always get a response from the same web server.

Now, stop Apache on web1:

  # /etc/init.d/apache stop

Reload/refresh your browser page to access http://70.253.158.42/which.html again. You should always get the response:

  I'm web2



 
 
>>> More Site Administration Articles          >>> More By O'Reilly Media
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

SITE ADMINISTRATION ARTICLES

- Coding: Not Just for Developers
- To Support or Not Support IE?
- Administration: Networking OSX and Win 7
- DotNetNuke Gets Social
- Integrating MailChimp with Joomla: Creating ...
- Integrating MailChimp with Joomla: List Mana...
- Integrating MailChimp with Joomla: Building ...
- Integrating MailChimp with Joomla
- More Top WordPress Plugins for Social Media
- Optimizing Security: SSH Public Key Authenti...
- Patches and Rejects in Software Configuratio...
- Configuring a CVS Server
- Managing Code and Teams for Cross-Platform S...
- Software Configuration Management
- Back Up a Joomla Site with Akeeba Backup

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: