 |  |
At 10:36 AM +0100 3/15/01, Lieven Gekiere wrote:
Re: load balancing problems
From: Men & Mice Support
Date: Thursday, March 15, 2001
Time: 4:34:18 am
>Hi,
>
>I'm trying to set up a load balancing system via Webstar 4.3 and QDNS 2.2.1,
>but I have some problems.
>
>My Setup :
>2 x WebSTAR 4.3 (www.piens.be & nauru.piens.be)
>1 x QuickDNS 2.2.1 (dns.piens.be)
>
>Is the load balancing plugin really needed in Webstar? I've did some tests
>by adding the LB-hosts in QuickDNS and I got requests on both hosts,
>however, the plugin was not installed on both Web*'s
When the WebSTAR plug-in isn't installed, it's exactly like having
multiple A records for the name. You don't get fault tolerance that
way, and you're limited to symmetric load balancing.
>I've installed the plugin in 1 Webstar Host and activated it via the Webstar
>Admin page. The log window now shows the following message every 30 seconds
>: 'Sending LPM Packet for HTTP to dns.piens.be at 10:11:39'
>
>The QuickDNS logfile tells me every 30 secons this message :
>'Rejecting LPM packet for nauru.piens.be, domain is not load shared'.
>'Rejecting LPM packet for www.boercharel.com, domain is not load shared'.
First off, you have both a load balance record and an A record named
nauru.piens.be. Remove one or the other, as they will conflict. You
appear to have the same problem for www.boercharel.com.
Secondly, WebSTAR is actually sending one LPM packet for each entry
in its Virtual Hosts table. That's why you're likely to see rejected
LPM packets in the QuickDNS Log. You can safely ignore these
messages, unless they involve a name for which you do actually have a
load balance record.
>I've added a load balancing record via QuickDNS Admin to the boercharel.com
>dns data file:
>
>------------------------------
>Name : www.boercharel.com
>ACC : a password
>TTL : 300
>Name server : dns.piens.be
>Load Balancing hosts:
> 195.207.143.100
> 195.207.143.99
>------------------------------
>
>If I make a browser request for www.boercharel.com only the second WebSTAR
>takes requests.
That's probably because you only installed the plug-in in that
WebSTAR server. This makes QuickDNS Pro think that (a) that server is
up, but (b) the other server is still not communicating, so it must
be down. This is the fault tolerance mechanism in action.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page