Code Monkey home page Code Monkey logo

Comments (3)

jsimbola avatar jsimbola commented on May 13, 2024

Hello, here is the full procedure that I've used to show this issue :
(and Fyi, pull request #78 doesn't solve this issue)

##########################

initial situation

ip addr |grep 192
 inet 192.168.150.32/24 brd 192.168.150.255 scope global eth0
inet 192.168.150.34/24 scope global secondary eth0:vip0_0
ps aux |grep keepalived
root     16303  0.0  0.0   3892   472 ?        Ss   18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     16306  0.0  0.2   4104  1488 ?        S    18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     16307  0.1  0.2   4104  1056 ?        S    18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     16398  0.0  0.1   3832   748 pts/0    S+   18:19   0:00 grep keepalived

##########################

changing main interface mask

ifconfig eth0 192.168.150.32 netmask 255.255.255.128
ip addr | grep 192
inet 192.168.150.32/25 brd 192.168.150.127 scope global eth0
ps aux |grep keepalived
root     16303  0.0  0.0   3892   472 ?        Ss   18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     16306  0.0  0.2   4104  1488 ?        S    18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     16307  0.0  0.2   4104  1056 ?        S    18:19   0:00 /usr/sbin/keepalived --log-facility=5
root     18564  0.0  0.1   3832   748 pts/0    S+   18:21   0:00 grep keepalived

##=> the vip 192.168.150.34 has been dropped.

##########################

trying to restart keepalived in order to get vip back on

/etc/init.d/keepalived stop
Stopping keepalived: keepalived.
ps aux |grep keepalived
root     19550  0.0  0.1   3832   752 pts/0    S+   18:23   0:00 grep keepalived
ip addr | grep 192
inet 192.168.150.32/25 brd 192.168.150.127 scope global eth0
/etc/init.d/keepalived start
Starting keepalived: keepalived.
ps aux |grep keepalived
root     19657  0.0  0.0   3892   472 ?        Ss   18:24   0:00 /usr/sbin/keepalived --log-facility=5
root     19660  0.0  0.2   4104  1484 ?        S    18:24   0:00 /usr/sbin/keepalived --log-facility=5
root     19661  0.0  0.2   4104  1052 ?        S    18:24   0:00 /usr/sbin/keepalived --log-facility=5
root     20063  0.0  0.1   3832   748 pts/0    S+   18:24   0:00 grep keepalived
ip addr | grep 192
inet 192.168.150.32/25 brd 192.168.150.127 scope global eth0
inet 192.168.150.34/24 scope global eth0:vip0_0

##########################

changing main interface mask again

ifconfig eth0 192.168.150.32 netmask 255.255.255.0
ip addr | grep 192
inet 192.168.150.34/24 scope global eth0:vip0_0
inet 192.168.150.32/24 brd 192.168.150.255 scope global secondary eth0
ifconfig eth0 192.168.150.32 netmask 255.255.255.128
ip addr | grep 192
inet 192.168.150.34/24 scope global eth0:vip0_0
inet 192.168.150.32/25 brd 192.168.150.127 scope global eth0
ifconfig eth0 192.168.150.32 netmask 255.255.255.0
ip addr | grep 192
inet 192.168.150.34/24 scope global eth0:vip0_0
inet 192.168.150.32/24 brd 192.168.150.255 scope global secondary eth0

##=> that's fine, however, if I try to restart keepalived :

/etc/init.d/keepalived stop
Stopping keepalived: keepalived.
ip addr | grep 192

##=> the main IP (192.168.0.32) disapeared...

ps aux |grep keepalived
root     23256  0.0  0.1   3832   752 pts/0    S+   18:28   0:00 grep keepalived
/etc/init.d/keepalived start
ip addr | grep 192
inet 192.168.150.34/24 scope global secondary eth0:vip0_0
ps aux |grep keepalived
root     23603  0.0  0.0   3892   472 ?        Ss   18:29   0:00 /usr/sbin/keepalived --log-facility=5
root     23606  0.0  0.2   4104  1488 ?        S    18:29   0:00 /usr/sbin/keepalived --log-facility=5
root     23607  0.0  0.2   4104  1032 ?        S    18:29   0:00 /usr/sbin/keepalived --log-facility=5
root     23637  0.0  0.1   3832   748 pts/0    S+   18:29   0:00 grep keepalived

from keepalived.

jsimbola avatar jsimbola commented on May 13, 2024

Hello
I think that I've found out what is going wrong about that behavior : If I delete the vip, keepalived just won't detect it... Is it normal ?

Also note that if I kill the keepalived processes (but I keep the vip up), then the backup box will mount the vip event if it's still up on the master box.

I think that I can solve that with a vrrp_strict, however, I'm wondering if it's a bug...

best regards.
Julien

from keepalived.

acassen avatar acassen commented on May 13, 2024

Hi Julien,

Keepalived is managing VIPs configured in conf file. If you are deleting VRRP VIP by hand, then VRRP stack will no longer be sync with operation. There is no kind of synchronization mecanism through netlink to set VRRP VIP back to system if someone else than Keepalived delete it.

regs,
Alexandre

from keepalived.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.