|
Sorry I should clarify that.
If I follow, for example, these steps:
/etc/init.d/keepalived start
/etc/init.d/keepalived stop
ipvsadm
ipvsadm hangs indefinitely. I can Ctrl-C this, then if I look at a
process listing, there is a keepalived running along with a couple of
keepalived children. Even a killall -9 keepalived will fail to kill it,
which leads me to believe this is a kernel-level ipvs problem,
presumably a deadlock.
Thanks,
Rob
On Fri, 2005-01-07 at 14:52 -0800, Rob Adams wrote:
> I've been having a bit of trouble getting ipvs working on 2.6 kernels.
> I'm using keepalived to manage a cluster of web/application servers from
> a pair of load balancers, using vrrp to handle router failover. The
> setup is a basic weight-round-robin LVS-NAT setup. I have it working
> (seemingly) fine on one load balancer running a 2.4 kernel, but on the
> other one, using 2.6.10, 2.6.9, or 2.6.8 (I've been trying it off and on
> for a while) I can start up keepalived to set up the cluster, but then
> if I run ipvsadm it hangs. The ipvsadm process then becomes an
> unkillable zombie. While this does raise interesting possibilities
> about creating unstoppable armies of zombies, in practice I have to
> reboot the server to get it usable again.
>
> Has anyone seen this ipvsadm lockup before? Any theories as to what
> might be causing it?
>
> Thanks,
> Rob
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
