LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Bug in LVS-0.6

To: "Shi, Eddie E" <eshi@xxxxxxxxxxxxxxxxx>
Subject: Re: Bug in LVS-0.6
Cc: <linux-virtualserver@xxxxxxxxxxxx>
From: "Ted Pavlic" <tpavlic@xxxxxxxxxxx>
Date: Wed, 7 Jul 1999 19:33:36 -0400
Sorta makes mon useless, doesn't it? :p

The funny thing is... I *HAVE* been able to delete before. It's odd... I
always can find someway to replicate this error -- just sometimes there are
more ways than one.

Thanks for the confirmation. I tried to trace exactly what was happening
when someone issued a delete command... but everything I can tell -- jumping
from file to file and routine to routine... it just looks like nothing vital
happens. A few if statements here... a little output there... but nothing
that should cause the system to halt. :(

Oh well.

Just a side note: in ip_vs_pcc.c, "Initializing" is spelled wrong and the
spacing is a little off. It's in the section that is executed at system
boot -- as the dmesg is built. Easy fix.

All the best --
Ted

----- Original Message -----
From: Shi, Eddie E <eshi@xxxxxxxxxxxxxxxxx>
To: 'Ted Pavlic' <tpavlic_list@xxxxxxxxxxx>; Linux Virtual Server Mailing
List <linux-virtualserver@xxxxxxxxxxxx>
Cc: <wensong@xxxxxxxxxxxx>
Sent: Wednesday, July 07, 1999 6:31 PM
Subject: RE: Bug in LVS-0.6


> Yes, I can confirm this. It also happened to my machine.
> Here is what I did.
>
>    . insmod ip_vs_pcc.o
>    . ipvsadm -A -t 192.168.10.100:80 -s pcc
>    . ipvsadm -a -t 192.168.10.100:80 -R 192.168.11.10
>    . ipvsadm -L
>       it listed correctly.
>    . ipvsadm -d -t 192.168.10.100:80
>       ### this cause the system locked up.
>
>    I have not spent time investigate this yet. For now I just try to avoid
> deleting.
>    Regards!
>
> Eddie
> -----Original Message-----
> From: Ted Pavlic [mailto:tpavlic_list@xxxxxxxxxxx]
> Sent: Tuesday, July 06, 1999 9:25 AM
> To: Linux Virtual Server Mailing List
> Cc: wensong@xxxxxxxxxxxx
> Subject: Bug in LVS-0.6
>
>
> I think I found a bug in LVS-0.6 for 2.2.10. It looks like when someone
> deletes a real server from the hash, the actual entry that says "hey, I'm
an
> existing real server" isn't deleted. (I haven't had time to look at the
> code, but I'm guessing this is the case)
>
> Try this: (SYNC first! And be sure you don't have processes in the
> background. This may cause you to need to reset your computer.) (Feel free
> to change the IP addresses)
>
> sync
> ipvsadm -C
> ipvsadm -A -t 10.200.0.15:80 -s rr
> ipvsadm -a -t 10.200.0.15:80 -r 216.69.192.196 -g
> ipvsadm -d -t 10.200.0.15:80 -r 216.69.192.196
> ipvsadm -d -t 10.200.0.15:80 -r 216.69.192.196
>
> At that point, if things work correctly, I should get this:
>
> setosckopt failed: No such file or directory
> No such destination
>
> Which is fine. That's what I get if I delete any real server that never
> existed in the first place. However, what I *ACTUALLY* get is this:
>
> IP_VS: ip_vs_del_dest(): destination not found!
> setosckopt failed: No such file or directory
> No such destination
>
> And then the machine locks up. It looks like init still is functioning, as
a
> CNTRL+ALT+DELETE does kick it into runlevel 6, however... it doesn't get
> very far into runlevel 6 until it completely locks up.
>
> Let me know if anyone else can confirm these results.
>
> Try:
>
> adding a virtual server
> adding a real node
> deleting that real node
> deleting it again
>
> If there isn't a bug, then it'll just act as if you tried to delete a
server
> that never existed... but if there is a bug... then your machine will
> lockup.
>
> All the best --
> Ted Pavlic
> tpavlic@xxxxxxxxxxx
>
>
>
>


<Prev in Thread] Current Thread [Next in Thread>