<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 5/22/2017 1:55 AM, Sven Schuster
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:trinity-cfff806b-bfb7-4c11-8f44-376234278f4e-1495443305079@3capp-gmx-bs30">
      <div style="font-family: Verdana;font-size: 12.0px;">
        <div style="font-family: Verdana;font-size: 12.0px;">
          <div>
            <div>Sorry, I should have been a bit more precise in this
              regard:</div>
            <div>- test disabled are disabled via enable/disable from
              the Administration menu for some period of time, e.g. 2
              hours, without "until OK" checked. It doesn't matter if
              you're blueing out a green (e.g. planned downtime) or red
              test. The problem remains the same.</div>
            <div>- the restart is done to make changes visible
              immediately for checking the change after applying it</div>
            <div>- dropped tests are of checks (or hosts) which don't
              exist anymore, so there won't be any checks coming in for
              the checks/hosts dropped</div>
            <div> </div>
            <div>Yes when waiting for some time before restarting after
              disabling or dropping a check, that change will "survive"
              the restart. As pointed out in Jeremy Laidman's post, this
              indeed seems to be due to the checkpoint interval which is
              600 seconds in the local configuration.</div>
            <div> </div>
            <div><br>
              Kind regards,</div>
            <div>Sven</div>
            <div> 
              <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding:
                10.0px 0 10.0px 10.0px;border-left: 2.0px solid
                rgb(195,217,229);">
                <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag,
                  19. Mai 2017 um 16:02 Uhr<br>
                  <b>Von:</b> "Root, Paul T"
                  <a class="moz-txt-link-rfc2396E" href="mailto:Paul.Root@CenturyLink.com"><Paul.Root@CenturyLink.com></a><br>
                  <b>An:</b> "'Sven Schuster'"
                  <a class="moz-txt-link-rfc2396E" href="mailto:Schuster.Sven@gmx.de"><Schuster.Sven@gmx.de></a>, <a class="moz-txt-link-rfc2396E" href="mailto:xymon@xymon.com">"xymon@xymon.com"</a>
                  <a class="moz-txt-link-rfc2396E" href="mailto:xymon@xymon.com"><xymon@xymon.com></a><br>
                  <b>Betreff:</b> RE: [Xymon] dropping/making blue
                  checks not persistent when restarting</div>
                <div>
                  <div>
                    <div class="WordSection1">
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);">So,
                            there’s a couple things here.</span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);"> </span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);">First,
                            how are you disabling (bluing out) a test
                            (you call check)? Are you checking the
                            “until OK” or are you providing a time limit
                            for the disable? Also, if the test is green
                            why would you want it disabled?</span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);"> </span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);">Second,
                            why are you restarting xymon after a config
                            change? All configuration files are re-read
                            (except local-client.cfg) every 5 minutes.</span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);"> </span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);">Next, you
                            say dropped tests reappear. Well of course.
                            If the client is providing the test to the
                            server, the server is going to display it.
                            If you don’t want a test in xymon, it has to
                            be disabled at the source.</span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);"> </span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);">I don’t
                            understand your second paragraph. You you
                            are saying that you disable a test and then
                            wait 5-10 minutes and the disabled test will
                            remain blue after restarting xymon?</span></font></p>
                      <p class="MsoNormal"><font size="2" face="Calibri"
                          color="#1f497d"><span style="font-size:
                            11.0pt;font-family: Calibri ,
                            sans-serif;color: rgb(31,73,125);"> </span></font></p>
                      <div>
                        <div style="border: none;border-top: solid
                          rgb(181,196,223) 1.0pt;padding: 3.0pt 0.0in
                          0.0in 0.0in;">
                          <p class="MsoNormal"><b><font size="2"
                                face="Tahoma"><span style="font-size:
                                  10.0pt;font-family: Tahoma ,
                                  sans-serif;font-weight: bold;">From:</span></font></b><font
                              size="2" face="Tahoma"><span
                                style="font-size: 10.0pt;font-family:
                                Tahoma , sans-serif;"> Xymon
                                [<a class="moz-txt-link-freetext" href="mailto:xymon-bounces@xymon.com">mailto:xymon-bounces@xymon.com</a>] <b><span
                                    style="font-weight: bold;">On Behalf
                                    Of </span> </b>Sven Schuster<br>
                                <b><span style="font-weight: bold;">Sent:</span></b>
                                Friday, May 19, 2017 7:55 AM<br>
                                <b><span style="font-weight: bold;">To:</span></b>
                                <a class="moz-txt-link-abbreviated" href="mailto:xymon@xymon.com">xymon@xymon.com</a><br>
                                <b><span style="font-weight: bold;">Subject:</span></b>
                                [Xymon] dropping/making blue checks not
                                persistent when restarting</span></font></p>
                        </div>
                      </div>
                      <p class="MsoNormal"><font size="3" face="Times
                          New Roman"><span style="font-size: 12.0pt;"> </span></font></p>
                      <div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">Hello everybody,</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;"> </span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">recently I've been seeing a
                                strange issue on xymon server. When I
                                make a check blue and shortly after
                                xymon gets restarted due to
                                configuration updates, that blue check
                                will be green again afterwards. The same
                                thing happens when a check is dropped
                                and xymon gets restarted directly after
                                that: the dropped check reappears.</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">If you wait some amount of
                                time before restarting, say 5-10
                                minutes, the problem won't appear and
                                everything will be fine. I also sync'ed
                                on the server directly after making a
                                check blue and before restarting (to
                                avoid data not being written to disk for
                                some strange reason), which
                                unfortunately did not help.</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">Environment is xymon 4.3.27
                                on Debian jessie. Xymon has been updated
                                to 4.3.28 because of this problem
                                lately, with the problem appearing in
                                4.3.28, too. This server has just been
                                upgraded from Debian wheezy to Jessie a
                                few weeks ago. On wheezy xymon 4.3.27
                                was in use but didn't show this
                                behaviour.</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;"> </span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">Did anybody notice such an
                                odd behaviour or maybe have any thoughts
                                regarding possible causes?</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;"> </span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">Thanks in advance,</span></font></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><font size="1"
                              face="Verdana"><span style="font-size:
                                9.0pt;font-family: Verdana ,
                                sans-serif;">Sven</span></font></p>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <p>Hi Sven,</p>
    <p>This behavior would seem to point in the direction of the
      checkpoint file not being written out properly on shutdown,
      especially if it's working fine during the normal checkpointing
      process (eg, waiting 600 seconds before the restart) and could be
      a latent bug (or at least a missing error message).</p>
    <p>Can you set xymond to --debug mode (or send it  -USR2 signal) and
      then shutdown/restart the process after this change? If shutting
      down, you can take a quick poke at the checkpoint file to see that
      it's been updated at the moment of shutdown? Depending on the host
      in question, you can also search for the test that should "no
      longer be there" (it's just a simple text file format).</p>
    <p>The same routine is called at shutdown as is called during the
      periodic interval checkpointing, except for the fact that we wait
      synchronously for it to complete -- precisely to avoid this type
      of concern, but that doesn't mean there isn't an issue there
      still.</p>
    <p>Regards,</p>
    <p>-jc<br>
    </p>
  </body>
</html>