|
> > On Fri, Dec 29, 2000 at 11:47:50AM -0800, Suresh Rajagopalan wrote:
> > > I upgraded my box from 2.2.14/0.9.12 to the latest versions --
> > > 2.2.18/1.0.2.
> > >
> > > I found typing in a rule with a -p option clears/messes up the ipvsadm
> > > table.
> > >
> > > For example:
> > >
> > > ipvsadm -A -t 1.2.3.4:443 -p 900 -s wlc
> > >
> > > would then screw up the ipvsadm table. A ipvsadm -S (or ipvsadm
> > > -L) dumps "unexpected input data".
> > >
> > > This only occurs when -p is included.
Thanks for the heads up on this. There is a minor bug in ipvsadm that
causes it to fail when _reading_ information on services with the
persistant flag set. Note that setting the services should work fine,
as will the LVS setup itself. You just can't read the entries using
ipvsadm -L.
Attached are two patches. The first is a patch to ipvsadm that fixes the
probelem. The second is a cosmetic patch to the LVS kernel code.
You should be fine if you just patch ipvsadm, recompile (and install it).
As an aside I am also looking in to an issue with compiling the ipvsadm
RPM with the supplied .spec file on Redhat 6.2 systems.
--
Horms
ipvsadm-1.3.persistant.patch
Description: Text document
ipvs-1.0.2-2.2.18-persistant.patch
Description: Text document
| 