<html><head><meta http-equiv="Content-Type" content="text/html charset=UTF-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 8. nov. 2015, at 10.26, <a href="mailto:user.clusterlabs.org@siimnet.dk" class="">user.clusterlabs.org@siimnet.dk</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Setting up my first pacemaker cluster, I’m trying to grasp howto make ocf:heartbeat:nginx monitor with check levels &gt; 0.<div class=""><br class=""></div><div class="">Got this so far:</div><div class=""><br class=""></div><div class=""><div class="">[root@afnA ~]# pcs resource</div><div class="">&nbsp;Resource Group: afnGroup</div><div class="">&nbsp; &nbsp; &nbsp;afnVIP &nbsp; &nbsp; (ocf::heartbeat:IPaddr2): &nbsp; &nbsp; &nbsp; Started afnA&nbsp;</div><div class="">&nbsp; &nbsp; &nbsp;afnNGinx &nbsp; (ocf::heartbeat:nginx): Started afnA&nbsp;</div><div class=""><br class=""></div><div class="">[root@afnA ~]# pcs resource show afnNGinx</div><div class="">&nbsp;Resource: afnNGinx (class=ocf provider=heartbeat type=nginx)</div><div class="">&nbsp; Attributes: configfile=/opt/imail/nginx/conf/nginx.conf port=8080 httpd=/opt/imail/nginx/sbin/nginx options="-p /opt/imail/nginx" status10url=/ping status10regex=".+ is alive\."&nbsp;</div><div class="">&nbsp; Operations: start interval=0s timeout=60s (afnNGinx-start-interval-0s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; stop interval=0s timeout=60s (afnNGinx-stop-interval-0s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; monitor interval=10s timeout=20s (afnNGinx-monitor-interval-10s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; monitor interval=60s timeout=20s (afnNGinx-monitor-interval-60s)</div><div class="">[root@afnA ~]#&nbsp;</div></div><div class=""><br class=""></div><div class="">but I cant verify that pacemaker RA ever calls <a href="http://localhost:8080/ping" class="">http://localhost:8080/ping</a>, why not?</div><div class=""><br class=""></div><div class="">Any pointers to info source(s) for better understanding RA configuration and maybe specially check levels?</div></div></div></blockquote></div><div class="">Found this:&nbsp;<a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-operation-monitor-multiple.html" class="">http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-operation-monitor-multiple.html</a></div><div class=""><br class=""></div>This seemed to work much better:<div class=""><br class=""></div><div class=""><div class="">[root@afnA ~]# pcs resource show afnNGinx</div><div class="">&nbsp;Resource: afnNGinx (class=ocf provider=heartbeat type=nginx)</div><div class="">&nbsp; Attributes: configfile=/opt/imail/nginx/conf/nginx.conf port=8080 httpd=/opt/imail/nginx/sbin/nginx options="-p /opt/imail/nginx" status10url=<a href="http://localhost:8080/ping" class="">http://localhost:8080/ping</a> status10regex="mss[0-9] is alive\."&nbsp;</div><div class="">&nbsp; Meta Attrs: target-role=Started&nbsp;</div><div class="">&nbsp; Operations: start interval=0s timeout=60s (afnNGinx-start-interval-0s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; stop interval=0s timeout=60s (afnNGinx-stop-interval-0s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; monitor interval=10s timeout=10s (afnNGinx-monitor-interval-10s)</div><div class="">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; monitor interval=120s timeout=30s OCF_CHECK_LEVEL=10 (afnNGinx-monitor-interval-120s)</div></div><div class=""><br class=""></div><div class="">=&gt;</div><div class=""><br class=""></div><div class=""><div class="">127.0.0.1 - - [08/Nov/2015:11:34:25 +0100] "GET /ping HTTP/1.1" 200 16 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"</div><div class="">127.0.0.1 - - [08/Nov/2015:11:36:25 +0100] "GET /ping HTTP/1.1" 200 16 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"</div><div class="">127.0.0.1 - - [08/Nov/2015:11:38:25 +0100] "GET /ping HTTP/1.1" 200 16 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"</div><div class="">127.0.0.1 - - [08/Nov/2015:11:40:25 +0100] "GET /ping HTTP/1.1" 200 16 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">[root@afnA]# pcs --version</div><div class="">0.9.139</div></div><div class=""><br class=""></div><div class=""><a href="https://www.mankier.com/8/pcs" class="">https://www.mankier.com/8/pcs</a>&nbsp;seems to indicate a debug-monitor command only my pcs version doesn’t seem to support this, might it only be in a later version, also I can seem to find ocf-tester from CentOS 6 repository, where might I find ocf-tester rpm?</div><div class=""><br class=""></div><div class="">/Steffen</div></body></html>