Re: lvs configuration problem...

"Mustafa A. Hashmi" <[email protected]>
Newsgroups gmane.linux.highavailability.ultramonkey
Message-ID <[email protected]>
On 6/2/06, Jiang <[email protected]> wrote:
> Hi,
>
> I am trying to set up a LVS system through ultramonkey recently, I am
> following "Streamline High Availability and Load Balancing"
> [url=http://www.ultramonkey.org/3/topologies/sl-ha-lb-eg.html] step by
> step, and the service I am testing on is HTTP, but eventually I still
> can't get it work. The system i am working on is Linux EL AS3 with
> information show by "uname -a": Linux ctestsrv1 2.4.21-40.ELsmp #1 SMP
> Thu Feb 2 22:22:39 EST 2006 i686 i686 i386 GNU/Linux

Please also have a look at:
http://www.debianhelp.co.uk/ultramonkey.htm. It may shed some more
light on your issue.

> ipvsadm -L -n shows:
> IP Virtual Server version 1.0.8 (size=65536)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  10.226.193.191:22 rr
>   -> 10.226.193.190:22            Route   1      0          0
>   -> 10.226.193.189:22            Local   1      0          0
> TCP  10.226.193.191:80 rr
>   -> 10.226.193.190:80            Route   0      0          0
>   -> 10.226.193.189:80            Local   1      0          0
>
> the other LD/real server also shows the similar things...
>

Can you post your ldirector.cf file? With route set to 0 for the
target server, the HB service is not receiving the desired result for
it's request. Are you sure the receive= line from ldirector is getting
what it's requesting? See the web server logs if a request comes in
from the HA service.

Regards,
--
Mustafa A. Hashmi
[email protected]
[email protected]


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.