|
After taking Xen out of the picture on the LVS node, and a failing attempt
to use the "configure" script, setting up via piranha following the Redhat
instructions sort of worked. I get connections to one realserver or the
other, and other connections hang.
I remember reading about problems with realservers using Redhat init
scripts (as I have in Centos 5.2 for example) interfering with each other
when more than one start up, due to doing ARPs on startup. The problem
was, I thought, referred to as being in ifup, but there's no occurrence of
the string 'arp' in ifup. It's in ifup-eth0 in my install.
One of the suggested fixes was to remove it. That doesn't look practical,
there's too much obscure code scattered through the script (and I don't
understand the internals of network startup or the Redhat scripts for it).
There are three calls to a utility called 'arping', plus various checks
and variable references that are arp-related.
Also, the routing tables look different on the two servers, and I can't
find the difference in network init scripts, which I take as another
reason to consider that I'm hitting an init scripts problem.
None of the realservers can ping out. Is this normal? I'm using the NAT
setup, partly because I thought it would allow the realservers to connect
out (normal NAT setups that I'm familiar with support outward
connections!). Once I get past basic testing, the applications on the
realservers will have to connect to databases and things which aren't of
course on the private network. Also the realservers currently have an
interface directly connected to the outside network; shouldn't *that*
provide outside connectivity? Or is it the source of my problems? Do the
realservers *have to* be totally isolated behind the LVS nodes?
--
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info
|
