LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: ipvs repartition problem

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: ipvs repartition problem
From: Todd Lyons <tlyons@xxxxxxxxxx>
Date: Tue, 22 Mar 2005 11:25:21 -0800
Stéphane Klein wanted us to know:

>[Mon Mar 21 17:52:23 2005|www] Quiescent real server: 
>from 10.1.1.26:80 ( x VIP:80) (Weight set to 0)
>[Mon Mar 21 17:52:23 2005|www] Restored real server: 
>VIP:80) (Weight set to 1)

Normal for startup.  It brings the service up in quiescent state, then
"restores" it to active state.  So no problems yet.


>[Mon Mar 21 17:56:32 2005|www] Quiescent real server:
>[Mon Mar 21 17:56:43 2005|www] Restored real server:
>[Mon Mar 21 17:56:56 2005|www] Quiescent real server:
>[Mon Mar 21 17:57:08 2005|www] Restored real server:
>[Mon Mar 21 17:59:41 2005|www] Quiescent real server:
>[Mon Mar 21 17:59:53 2005|www] Restored real server:
>[Mon Mar 21 18:00:31 2005|www] Quiescent real server: 
>[Mon Mar 21 18:00:50 2005|www] Restored real server: 
>[Mon Mar 21 18:29:18 2005|www] Quiescent real server:
>[Mon Mar 21 18:29:29 2005|www] Restored real server: 
>[Tue Mar 22 09:17:00 2005|www] Quiescent real server:
>[Tue Mar 22 09:17:12 2005|www] Restored real server:
>[Tue Mar 22 09:18:35 2005|www] Quiescent real server:
>[Tue Mar 22 09:18:45 2005|www] Restored real server:

If you 'telnet 10.1.1.26 80' from the director every 5 or 10 seconds,
does it do the same thing to you?  This really looks like a network
problem since all of the reachability issues are on the same realserver
(the other one is not producing these messages according to your log
messages).

>For information, the server with ip 10.1.1.25 is stopped for the moment.

So the 10.1.1.25 realserver does it to?

>I had the same problem with a previous version. It was:

Still, it sounds even more like a network issue.  Change cables, change
cards, and change switch ports (easy stuff).  Change the switch if it's
possible.

Watch for IP collisions (look for MAC changes for that IP on the
director), though if it's doing it on multiple real-servers, it could be
an IP collision of something else out on the network with the director's
real IP address.

>Sometimes, It seams ldirectord stops redirecting requests to the real
>servers for 10 seconds.

Yes because the real server becomes unreachable.  Experiment with the
connectivity between the director and realservers and you'll find your
problem.

-- 
Regards...              Todd
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.  Please use in that order. --Ed Howdershelt
Linux kernel 2.6.8.1-12mdkenterprise   2 users,  load average: 0.10, 0.07, 0.02

<Prev in Thread] Current Thread [Next in Thread>