|
Hello,
On Wed, 11 Sep 2002, Matthias Krauss wrote:
> thanks for this info, ip_vs doesnt want to get unloaded / device busy, also
> something
> strange happens to the expire time which i think is the reason for "device
> busy" ,
In theory, it can be unloaded after ipvsadm -C
> yesterday evening i left the lvs with a 2 hours persistant timeout for the
> night, i
> made a conx request and closed it afterwards.
>
> IPVS connection entries
> pro expire state source virtual destination
>
> TCP 115:58.78 NONE venus.intern:0 lbs.intern:65535
> hh-fra-in01.intern:65535
>
> today for my surprise i see:
>
> IPVS connection entries
> pro expire state source virtual destination
>
> TCP 357913:56.47 NONE venus.intern:0 lbs.intern:65535
> hh-fra-in01.intern:65535
>
> there was no request during this time, the time difference between this to
> lists is
> around 14 hours.
Why 14 hours? 357913 are minutes. What is the IPVS version
and what is the ipvsadm version? It seems you are using old ipvsadm
utility. Or may be old IPVS too? The recent ipvsadm does not print
".47" from "357913:56.47".
> Regards
> Matthias
Regards
--
Julian Anastasov <ja@xxxxxx>
|
