<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <div class="moz-cite-prefix">0.20 doesn't crash the server upon
      failure of (first) agent to access rndc due to default-key being
      incorrect.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Other testing in progress.<br>
    </div>
    <div class="moz-cite-prefix">-Erik</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 9/8/21 9:06 AM, Victoria Risk wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0B388268-3C59-4BC7-BDF2-184C29E792C0@isc.org">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Hi Erik-
      <div class=""><br class="">
      </div>
      <div class="">I think this issue *may* be addressed in a fix in
        the version we are about to post. It is being sanity checked and
        signed now, so it should be up later today.</div>
      <div class=""><br class="">
      </div>
      <div class=""><strong class="">Agent re-registration fix</strong><span
          style="font-family: -webkit-standard; font-size: medium;"
          class="">. Earlier Stork versions suffered from a problem when
          a previously authenticated agent restarted, the server
          couldn't recognize it and forced a new registration, requiring
          the administrator to re-authenticate the machine. This problem
          has been fixed.[</span><a
          href="/isc-projects/stork/-/issues/528" data-original="#528"
          data-link="false" data-link-reference="false"
          data-project="87" data-issue="5991"
          data-reference-type="issue" data-container="body"
          data-placement="top" title="Restarting agent service triggers
          re-registration (sanity checks)" class="gfm gfm-issue
          has-tooltip" moz-do-not-send="true">#528 (closed)</a><span
          style="font-family: -webkit-standard; font-size: medium;"
          class="">,</span><a href="/isc-projects/stork/-/issues/558"
          data-original="#558" data-link="false"
          data-link-reference="false" data-project="87"
          data-issue="6341" data-reference-type="issue"
          data-container="body" data-placement="top" title="Stork Agent
          registers with different token on each service/server restart"
          class="gfm gfm-issue has-tooltip" moz-do-not-send="true">#558
          (closed)</a><span style="font-family: -webkit-standard;
          font-size: medium;" class="">]. </span></div>
      <div class=""><font class="" size="3" face="-webkit-standard"><br
            class="">
        </font></div>
      <div class=""><font class="" size="3" face="-webkit-standard">Vicky<br
            class="">
        </font>
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Sep 7, 2021, at 5:14 PM, Erik Edwards <<a
                href="mailto:fluteze@gmail.com" class=""
                moz-do-not-send="true">fluteze@gmail.com</a>> wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div class="">Hello list,<br class="">
                <br class="">
                I've been testing the 0.19 version of the stork system
                and encountered a consistent error after a new (first)
                machine is registered, either manually with the server's
                ID copy/paste or via the unauthorized tab.<br class="">
                <br class="">
                After some investigation, I found a line in the remote
                dhcp server's /etc/rndc.conf file referencing the
                default key as "sample-key" in the options section.
                After changing this to the correct key name (which is
                loaded via an include statement from /etc/rndc.key) the
                server was able to complete the registration and seems
                to be functional.<br class="">
                <br class="">
                The log on the isc-stork-server had a panic message
                referencing an invalid index [0] of [0]. In the test
                network this was the first machine being added.<br
                  class="">
                <br class="">
                -Erik<br class="">
                <br class="">
                <br class="">
                -- <br class="">
                Stork-users mailing list<br class="">
                <a href="mailto:Stork-users@lists.isc.org" class=""
                  moz-do-not-send="true">Stork-users@lists.isc.org</a><br
                  class="">
                <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/stork-users">https://lists.isc.org/mailman/listinfo/stork-users</a><br
                  class="">
              </div>
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>