Any estimate on the backport ?
--
Keepalived haven't LVS support
https://bugs.launchpad.net/bugs/496932
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in ubuntu.
--
Ubuntu-server-bugs mailing list
I works just fine in my test environment. Please rush the backport, i
dont like devel repositories in my production enviroment ;)
--
Keepalived haven't LVS support
https://bugs.launchpad.net/bugs/496932
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Sorry forgot configuration
ips has been changed, but should be consistent
For the LVS NAT to work you should not add any rules for the VIP in the
PRE og POSTROUTING chains, ipvs does this on its own transparently. The
rules add in the test setup is for management of the nodes behind the
LVS. The
Note:
i have 2 interfaces with static address, front (eth0) and back (eth1) of the
lvs. I use VIPS (VIP and BVIP) in example config on both sides. This ensures
that i with multiple loadbalancers can move different instances to different
lvs machines thus not having fixed master/slave but i use
Does your backend/real servers use the 10.10.10.1 as gateway? also you should
either use lb_algo wrr or drop the weigths on the realservers. keepalived/ipvs
had problems with such configurations earlier - i just dropped functionallity
without any warning.
1 backend node missing
Look in your
Any estimate on the backport ?
--
Keepalived haven't LVS support
https://bugs.launchpad.net/bugs/496932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I works just fine in my test environment. Please rush the backport, i
dont like devel repositories in my production enviroment ;)
--
Keepalived haven't LVS support
https://bugs.launchpad.net/bugs/496932
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry forgot configuration
ips has been changed, but should be consistent
For the LVS NAT to work you should not add any rules for the VIP in the
PRE og POSTROUTING chains, ipvs does this on its own transparently. The
rules add in the test setup is for management of the nodes behind the
LVS. The
Note:
i have 2 interfaces with static address, front (eth0) and back (eth1) of the
lvs. I use VIPS (VIP and BVIP) in example config on both sides. This ensures
that i with multiple loadbalancers can move different instances to different
lvs machines thus not having fixed master/slave but i use
Does your backend/real servers use the 10.10.10.1 as gateway? also you should
either use lb_algo wrr or drop the weigths on the realservers. keepalived/ipvs
had problems with such configurations earlier - i just dropped functionallity
without any warning.
1 backend node missing
Look in your
10 matches
Mail list logo
