keepalived loses MASTER state if reloaded multiple times

Greetings!

I'm new here and I'd like to ask for your help to solve a possible issue I'm having when running 2 instances of keepalived, configured to use VRRP.

If I issue a reload (SIGHUP) to keepalived when it's still reloading from a previous SIGHUP, all VIPs get unregistered from the interface.
I'm guessing this is related to VRRP, but preempt_delay didn't help. Is there a way to fix that or at least find out easily when it's safe to reload keepalived (ie, when a previous reload is not happening)?


I'm doing these operations (and below are their generated logs):

$ service keepalived reload
Sep 24 12:04:10 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_B) Entering BACKUP STATE
Sep 24 12:04:13 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_A) Transition to MASTER STATE

(Above you can see I reload keepalived and waited for it to transition to MASTER. Everything went as expected.)

Now below I reload it again when it didn't have time to transition to MASTER:


$ service keepalived reload
Sep 24 12:04:23 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_B) Entering BACKUP STATE

$ service keepalived reload
Sep 24 12:04:24 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_A) Entering BACKUP STATE
Sep 24 12:04:24 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_B) Entering BACKUP STATE
Sep 24 12:04:27 vdirector1 Keepalived_vrrp[19948]: VRRP_Instance(LB_A) Transition to MASTER STATE

Thanks,
-- Luís Fernando


________________________________

AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/.

NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information.
If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/.

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel