|
So i've got a better handle on the HTTP error now. Firstly the set up
is two dual core AMD Athlon 64 servers are serving as the director
boxes. I'm running ultramonkey 3 on each of these. All of the
servers are at a data center and are running directly on the WAN.
What seems to be happening is that when i start heartbeat and
ldirector on one of the directors it makes an HTTP request to the
Apache real servers. Though when i do a tcpdump on the apache real
servers it only seems to make a request the first time ipvsadm is run
on the director box. After this however it makes no HTTP requests to
the machine at all, and though the box appears to be clustered when i
do an ipvsadm -L -n, the connection is refused. I have no firewalls
running right now, so that is not the issue. Here is the section of
the ldirectord.cf file pertaining to the HTTP services:
virtual=64.34.209.34:80
fallback=127.0.0.1:80
real=64.34.174.215:80 gate
real=64.34.180.165:80 gate
service=http
request="/update/index.html"
receive="Test Page"
scheduler=rr
#persistent=600
protocol=tcp
checktype=negotiate
As you can see both of the webservers are on different subnets than
each other, and also on a different subnet than both of the
ultramonkey directors, though the director boxes are on the same
subnet (170) and share a common default gateway.
the ha.cf file sets up a ucast between the two servers, and the names
are properly configured using the uname -n output as the names of the
two hosts.
The haresources file looks like this:
Server06.example.com \
ldirectord::ldirectord.cf \
LVSSyncDaemonSwap::master \
IPaddr2::64.34.209.34/24/eth0/64.34.209.255 \
IPaddr2::64.34.183.97/24/eth0/64.34.209.255 \
IPaddr2::64.34.209.50/24/eth0/64.34.209.255
Any ideas as to why it is behaving in this weird way?
--
regards,
matt
|
