<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 1 Sep 2017, at 13:15, Klechomir <<a moz-do-not-send="true"
      href="mailto:klecho@gmail.com" class="">klecho@gmail.com</a>>
    wrote:
    <blockquote
      cite="mid:382BFB3C-9728-40F5-9771-0E3545FC1E9A@feldhost.cz"
      type="cite">
      <div>
        <blockquote type="cite" class=""><br
            class="Apple-interchange-newline">
          <div class="">
            <div class="">What I observe is that single monitoring
              request of different resources with different resource
              agents is timing out.<br class="">
              <br class="">
              For example LVM resource (the LVM RA) does this sometimes.<br
                class="">
              Setting ridiculously high timeouts (5 minutes and more)
              didn't solve the problem, so I think I'm  out of options
              there.<br class="">
              Same for other I/O related resources/RAs.<br class="">
              <br class="">
            </div>
          </div>
        </blockquote>
        <div><br class="">
        </div>
        <div>hmm, so probably is something bad in clvm configuration? I
          use clvm in three node cluster without issues. Which version
          of centos u use? I experience clvm problems only on pre 7.3
          version due to bug in libqb.</div>
      </div>
    </blockquote>
    <br>
    I have timeouts with and without clvm. Have it with resources
    managing (scst) iscsi targets as well.<br>
    <br>
    <blockquote
      cite="mid:382BFB3C-9728-40F5-9771-0E3545FC1E9A@feldhost.cz"
      type="cite">
      <div><br class="">
        <blockquote type="cite" class="">
          <div class="">
            <div class="">Regards,<br class="">
              Klecho<br class="">
              <br class="">
              One of the typical cases is LVM (LVM RA)monitoring.<br
                class="">
              <br class="">
              On 1.09.2017 11:07, Jehan-Guillaume de Rorthais wrote:<br
                class="">
              <blockquote type="cite" class="">On Fri, 01 Sep 2017
                09:07:16 +0200<br class="">
                "Ulrich Windl" <<a moz-do-not-send="true"
                  href="mailto:Ulrich.Windl@rz.uni-regensburg.de"
                  class="">Ulrich.Windl@rz.uni-regensburg.de</a>>
                wrote:<br class="">
                <br class="">
                <blockquote type="cite" class="">
                  <blockquote type="cite" class="">
                    <blockquote type="cite" class="">
                      <blockquote type="cite" class="">Klechomir <<a
                          moz-do-not-send="true"
                          href="mailto:klecho@gmail.com" class="">klecho@gmail.com</a>>
                        schrieb am 01.09.2017 um 08:48 in Nachricht<br
                          class="">
                      </blockquote>
                    </blockquote>
                  </blockquote>
                  <<a moz-do-not-send="true"
                    href="mailto:9f043557-233d-6c1c-b46d-63f8c2ee59c7@gmail.com"
                    class="">9f043557-233d-6c1c-b46d-63f8c2ee59c7@gmail.com</a>>:<br
                    class="">
                  <blockquote type="cite" class="">Hi Ulrich,<br
                      class="">
                    Have to disagree here.<br class="">
                    <br class="">
                    I have cases, when for an unknown reason a single
                    monitoring request<br class="">
                    never returns result.<br class="">
                    So having bigger timeouts doesn't resolve this
                    problem.<br class="">
                  </blockquote>
                  But if your monitor hangs instead of giving a result,
                  you also cannot ignore<br class="">
                  the result that isn't there! OTOH: Isn't the operation
                  timeout for monitors<br class="">
                  that hang? If the monitor is killed, it returns an
                  implicit status (it<br class="">
                  failed).<br class="">
                </blockquote>
                I agree. It seems to me the problems comes from either
                the resource agent or<br class="">
                the resource itself. Presently, this issue bothers the
                cluster stack, but soon<br class="">
                or later, it will blows something else. Track where the
                issue comes from, and<br class="">
                fix it.<br class="">
                <br class="">
              </blockquote>
              <br class="">
              <br class="">
              _______________________________________________<br
                class="">
              Users mailing list: <a moz-do-not-send="true"
                href="mailto:Users@clusterlabs.org" class="">Users@clusterlabs.org</a><br
                class="">
              <a moz-do-not-send="true"
                href="http://lists.clusterlabs.org/mailman/listinfo/users"
                class="">http://lists.clusterlabs.org/mailman/listinfo/users</a><br
                class="">
              <br class="">
              Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a><br class="">
              Getting started:
              <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br
                class="">
              Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a><br class="">
            </div>
          </div>
        </blockquote>
      </div>
      <br class="">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.clusterlabs.org/mailman/listinfo/users">http://lists.clusterlabs.org/mailman/listinfo/users</a>

Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>