Re: Issue with priority when issuing SIGHUP

--===============2435337981765309402==
Content-Type: multipart/alternative; boundary="0000000000003214da05764d558f"

--0000000000003214da05764d558f
Content-Type: text/plain; charset="UTF-8"

Submitted, thank you.

On 20 September 2018 at 12:52, Quentin Armitage <[email protected]>
wrote:

> On Thu, 2018-09-20 at 11:46 +0100, Paul Gildea wrote:
>
> Hello,
>
> I noticed an issue with changing my VRRP config and issuing a SIGHUP
> instead of stopping and restarting the keepalived process, after each
> config change I issue a SIGHUP to update values. Usually this works fine
> but not in the case of changing priorities and decrementing using a tracked
> interface.
>
> Originally I had a priority of 50 with a tracked interface having a
> decrement value of -7. I bought down the tracked interface and then I
> proceeded to change the priority to 110 and the decrement value to -11. The
> log then indicates that the effective priority changed correctly from 100
> to 99, everything seems to be fine with the new values selected.
>
> I then brought back up the tracked interface and at this stage there is
> some internal inconsistency because the message in the log states "Changing
> effective priority from 103 to 114", remembering the old -7 decrement value
> but the new priority value, and then adds the new decrement -11 value to
> 103 instead of 99. If I bring the tracked interface down again the value
> changes from 114 to 103.
>
> In general is this method not supported or is this a bug? Should I be
> stopping/starting keepalived each time I change my config?
>
> Separate but maybe related, I have also noticed an issue sometimes that
> when I start VRRP with an interface as backup and a priority of 110, with a
> decrement set of -11, when it becomes master it actually adds the decrement
> to the priority and goes to 121, I need to look into that issue further
> though.
>
> Paul,
>
> What you describe should be supported, and it looks like a bug. What you
> be most helpful is if you could raise an issue at
> https://github.com/acassen/keepalived/issues . It is most helpful if you
> can include what version of keepalived you are using (output of keepalived
> -v), a copy of your configuration, and in this case diffs showing the
> changes in configuration for the reloads.
>
> Quentin Armitage
>

--0000000000003214da05764d558f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Submitted, thank you.</div><div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On 20 September 2018 at 12:52, Quentin Armitage =
<span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"=
_blank">[email protected]</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div bgcolor=3D"#ffffff" text=3D"#2e3436" link=3D"#2a76c6" vl=
ink=3D"#2e3436"><span class=3D""><div>On Thu, 2018-09-20 at 11:46 +0100, Pa=
ul Gildea wrote:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex;=
border-left:2px #729fcf solid;padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr"><div>Hello,</div><div><br></div><div>I noticed an issue with chang=
ing my VRRP config and issuing a SIGHUP instead of stopping and restarting =
the keepalived process, after each config change I issue a SIGHUP to update=
 values. Usually this works fine but not in the case of changing priorities=
 and decrementing using a tracked interface.</div><div><br></div><div>Origi=
nally I had a priority of 50 with a tracked interface having a decrement va=
lue of -7. I bought down the tracked interface and then I proceeded to chan=
ge the priority to 110 and the decrement value to -11. The log then indicat=
es that the effective priority changed correctly from 100 to 99, everything=
 seems to be fine with the new values selected.</div><div><br></div><div>I =
then brought back up the tracked interface and at this stage there is some =
internal inconsistency because the message in the log states &quot;Changing=
 effective priority from 103 to 114&quot;, remembering the old -7 decrement=
 value but the new priority value, and then adds the new decrement -11 valu=
e to 103 instead of 99. If I bring the tracked interface down again the val=
ue changes from 114 to 103.</div><div><br></div><div>In general is this met=
hod not supported or is this a bug? Should I be stopping/starting keepalive=
d each time I change my config?</div><div><br></div><div>Separate but maybe=
 related, I have also noticed an issue sometimes that when I start VRRP wit=
h an interface as backup and a priority of 110, with a decrement set of -11=
, when it becomes master it actually adds the decrement to the priority and=
 goes to 121, I need to look into that issue further though.</div><div><br>=
</div></div></div></blockquote></span><div>Paul,</div><div><br></div><div>W=
hat you describe should be supported, and it looks like a bug. What you be =
most helpful is if you could raise an issue at <a href=3D"https://github.co=
m/acassen/keepalived/issues" target=3D"_blank">https://github.com/acassen/<=
wbr>keepalived/issues</a> . It is most helpful if you can include what vers=
ion of keepalived you are using (output of keepalived -v), a copy of your c=
onfiguration, and in this case diffs showing the changes in configuration f=
or the reloads.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div><b=
r></div><div>Quentin Armitage</div></font></span></div></blockquote></div><=
br></div>

--0000000000003214da05764d558f--


--===============2435337981765309402==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============2435337981765309402==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2435337981765309402==--