garp_group breaks after reload/SIGHUP

Sven Hartge <[email protected]> Thu, 16 Mar 2017 21:09:26 +0100 (CET)
Newsgroups gmane.linux.keepalived.devel
Message-ID <[email protected]>
Hi!

Because of a picky switch I am forced to use a garp_group to limit the
amount of Gratuitous ARPs to about 0.5/s.

This works as intented:

garp_group {
     garp_interval 0.5
     gna_interval 0.5
     interfaces {
        bond0.130
        bond0.136
        bond0.140
        bond0.200
        bond0.1869
        bond0.1905
        bond1.137
        bond1.600
        bond1.1862
        bond1.1863
        bond1.1865
        bond1.1866
        bond1.3333
      }   
}


But: After doing a reload of keepalived via either "systemctl reload
keepalived.service" or just sending a plain SIGHUP to the main PID, only
the very first interface in the list gets GARPs, all other interfaces do
no longer receive any. 

I have to do a hard restart of the daemon to get it working again, but
this is inconveniently causing a failover to the backup system which I
would like to avoid.

This behavior is also present with multple garp_groups. Only the first
interface in every group gets GARPs, the rest end up empty.

Using --dump-conf I can see that the configuration file is parsed
correctly and every interface is placed on the correct garp_group.

I first noticed this with 1.2.23, but 1.3.2 (latest version available in
Debian Sid right now) also shows this problem.

Grüße,
Sven.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot