what i meant was, how are you conducting the test?


On 4/23/07, Maverik <[EMAIL PROTECTED]> wrote:

I have 1 director and two real servers:

eth0(172.31.24.146) --director -- eth1(192.16.1.1) --> real1 (192.168.1.2
)/real2(192.168.1.3 )

outbound route from the real servers to the gateway is okay. but routing
by the director doesn't work and no indication of errors on the
/var/log/messages (I even generated another log without any misconfigured
indication).

thanks.


On 4/21/07, Ariz Jacinto <[EMAIL PROTECTED]> wrote:
>
> hi,
>
> how are you testing it? by a single connection only?
>
>
>
>
>  On 4/19/07, Maverik < [EMAIL PROTECTED] > wrote:
>
> >  Hi!
> >
> > I installed Ultra Monkey for load-balancing purposes (on a RHEL4). I
> > followed the instruction on the UM site. I did the following already:
> >
> > 1. installed UM on the director; modified the sysctl file and updated
> > the ldirectord.cf (1 director and 2 nodes)
> > 2. based on the ipvsadm -L -n, it shows both the nodes' IP addresses
> > and the virtual's as well.
> > 3. also, the polling of the nodes are okay based on the tcpdump result
> > (nodes would return 200 status to the requests of the director)
> > 4. i turned on the apache on all of the nodes and the director;
> > however, for the director, i configured the httpd.conf to listen to
> > the loopback only (for the fallback parameter of the ldirectord.cf).
> > 5. connectivity to the outside network of the nodes are okay (iptables
> > have been configured to allow nodes to connect to the external network)
> >
> > After several tests, the director doesn't route requests coming from
> > the virtual IP to the nodes. tcpdump is not taking any packets from the
> > virtual address on port 80. the director doesn't reroute traffic to the
> > loopback address when connection to the nodes fails (as per fallback
> > parameter would instruct).
> >
> > According to a debian site, I need to modify the sysctl of the nodes,
> > which I did. Nothing happened.
> >
> > I checked several sites already, and there's nothing much to do in the
> > director or the ldirectord.cf file, unless the implementation is
> > load-balancing and high-availability (which isn't the case here).
> >
> > Any help is appreciated. Thanks.
> >
> > _________________________________________________
> > Philippine Linux Users' Group (PLUG) Mailing List
> > [email protected] (#PLUG @ irc.free.net.ph)
> > Read the Guidelines: http://linux.org.ph/lists
> > Searchable Archives: http://archives.free.net.ph
> >
>
>
> _________________________________________________
> Philippine Linux Users' Group (PLUG) Mailing List
> [email protected] (#PLUG @ irc.free.net.ph)
> Read the Guidelines: http://linux.org.ph/lists
> Searchable Archives: http://archives.free.net.ph
>



--
Regards,
Maenard

---------------------
"Ability is what you're capable of doing... Motivation determines what you
do... Attitude determines how well you do it."
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to