|
On Tue, 9 May 2000, Joseph Mack wrote:
> This doesn't fix the problem. Here's the output for 0.9.8-2.2.14
>
> IP Virtual Server version 0.9.8 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP lvs.mack.net:telnet rr
> -> 255.255.255.255:49320 Masq 4194304 0 0
> TCP lvs.mack.net:netpipe rr
> -> 255.255.255.255:49320 Masq 4194304 0 0
>
> Note the realservers were 192.168.1.x and not 255^4,
> the weights are wrong and I'm using DR not NAT. The
> LVS doesn't work either.
>
> In case I have put some new files somewhere,
> there are no new files in /sbin, /bin, /usr/bin/, /usr/sbin,
> /usr/local/bin, /lib , /usr/lib, /usr/local/lib and looking
> with find doesn't find anything obvious
>
> Any ideas anyone?
>
Joe, I guess that your ipvsadm version and ipvs patch version doesn't
match, it lead to this problem. In the ipvs 0.9.12, we have fwmark-based
service feature, we add a member fwmark of struct ip_vs_user. In the ipvs
0.9.8, there is no such member fwmark. So, if you use ipvsadm compiled
based on ipvs 0.9.12 to talk to the kernel with ipvs 0.9.8, you are
talking different things (different ip_vs_user), the kernel cannot
understand.
So, after you switch back to ipvs 0.9.8, you need to recompiled your
ipvsadm program.
Thanks,
Wensong
|
