[Pacemaker] crm_simulate a resource failure
Jake Smith
jsmith at argotec.com
Tue Oct 23 18:35:23 EDT 2012
Ubuntu 12.04
pacemaker 1.1.6-2ubuntu3
If I run crm_simulate -L I get this:
root at Vulture:~# crm_simulate -L
*** glibc detected *** crm_simulate: double free or corruption (out): 0x0000000001fc2e00 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7e626)[0x7f35df08e626]
/usr/lib/libcib.so.1(+0xc259)[0x7f35df96b259]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x373d3)[0x7f35ded523d3]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_hash_table_remove_all+0x1d)[0x7f35ded5324d]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_hash_table_destroy+0xe)[0x7f35ded532de]
/usr/lib/libcib.so.1(cib_new_variant+0x155)[0x7f35df96b9fb]
/usr/lib/libcib.so.1(cib_file_new+0x28)[0x7f35df971aad]
/usr/lib/libcib.so.1(cib_new+0x62)[0x7f35df96b70c]
crm_simulate[0x40614f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f35df03176d]
crm_simulate[0x402279]
======= Memory map: ========
00400000-00409000 r-xp 00000000 fb:05 541771 /usr/sbin/crm_simulate
00608000-00609000 r--p 00008000 fb:05 541771 /usr/sbin/crm_simulate
00609000-0060a000 rw-p 00009000 fb:05 541771 /usr/sbin/crm_simulate
01fbb000-02259000 rw-p 00000000 00:00 0 [heap]
7f35dbba6000-7f35dbbbb000 r-xp 00000000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f35dbbbb000-7f35dbdba000 ---p 00015000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f35dbdba000-7f35dbdbb000 r--p 00014000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f35dbdbb000-7f35dbdbc000 rw-p 00015000 fb:05 393311 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f35dbdbc000-7f35dbdbf000 r-xp 00000000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7f35dbdbf000-7f35dbfbe000 ---p 00003000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7f35dbfbe000-7f35dbfbf000 r--p 00002000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7f35dbfbf000-7f35dbfc0000 rw-p 00003000 fb:05 393398 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7f35dbfc0000-7f35dbfc8000 r-xp 00000000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0
7f35dbfc8000-7f35dc1c8000 ---p 00008000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0
7f35dc1c8000-7f35dc1c9000 r--p 00008000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0
7f35dc1c9000-7f35dc1ca000 rw-p 00009000 fb:05 525256 /usr/lib/x86_64-linux-gnu/libltdl.so.7.3.0
7f35dc1ca000-7f35dc1db000 r-xp 00000000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7f35dc1db000-7f35dc3da000 ---p 00011000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7f35dc3da000-7f35dc3db000 r--p 00010000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7f35dc3db000-7f35dc3dc000 rw-p 00011000 fb:05 525504 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7f35dc3dc000-7f35dc456000 r-xp 00000000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0
7f35dc456000-7f35dc656000 ---p 0007a000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0
7f35dc656000-7f35dc657000 r--p 0007a000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0
7f35dc657000-7f35dc65a000 rw-p 0007b000 fb:05 393527 /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0
7f35dc65a000-7f35dc66a000 r-xp 00000000 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7f35dc66a000-7f35dc869000 ---p 00010000 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7f35dc869000-7f35dc86a000 r--p 0000f000 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7f35dc86a000-7f35dc86b000 rw-p 00010000 fb:05 525508 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7f35dc86b000-7f35dc872000 r-xp 00000000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so
7f35dc872000-7f35dca71000 ---p 00007000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so
7f35dca71000-7f35dca72000 r--p 00006000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so
7f35dca72000-7f35dca73000 rw-p 00007000 fb:05 403340 /lib/x86_64-linux-gnu/librt-2.15.so
7f35dca73000-7f35dca8b000 r-xp 00000000 fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so
7f35dca8b000-7f35dcc8a000 ---p 00018000 fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so
7f35dcc8a000-7f35dcc8b000 r--p 00017000 fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so
7f35dcc8b000-7f35dcc8c000 rw-p 00018000 fb:05 403404 /lib/x86_64-linux-gnu/libpthread-2.15.so
7f35dcc8c000-7f35dcc90000 rw-p 00000000 00:00 0
7f35dcc90000-7f35dcccc000 r-xp 00000000 fb:05 393325 /lib/x86_64-linux-gnu/libpcre.so.3.12.1
7f35dcccc000-7f35dcecb000 ---p 0003c000 fb:05 393325 /lib/x86_64-linux-gnu/libpcre.so.3.12.1
7f35dcecb000-7f35dcecc000 r--p 0003b000 fb:05 393325 /lib/x86_64-linux-gnu/libpcre.so.3.12.1
7f35dcecc000-7f35dcecd000 rw-p 0003c000 fb:05 393325 /lib/x86_64-linux-gnu/libpcre.so.3.12.1
7f35dcecd000-7f35dcfc6000 r-xp 00000000 fb:05 393285 /lib/x86_64-linux-gnu/libm-2.15.so
7f35dcfc6000-7f35dd1c5000 ---p 000f9000 fb:05 393285 /lib/x86_64-linux-gnu/libm-2.15.so
7f35dd1c5000-7f35dd1c6000 r--p 000f8000 fb:05 393285 /lib/x86_64-linux-gnu/libm-2.15.so
7f35dd1c6000-7f35dd1c7000 rw-p 000f9000 fb:05 393285 /lib/x86_64-linux-gnu/libm-2.15.so
7f35dd1c7000-7f35dd1dd000 r-xp 00000000 fb:05 396605 /lib/x86_64-linux-gnu/libz.so.1.2.3.4
7f35dd1dd000-7f35dd3dc000 ---p 00016000 fb:05 396605 /lib/x86_64-linux-gnu/libz.so.1.2.3.4
7f35dd3dc000-7f35dd3dd000 r--p 00015000 fb:05 396605 /lib/x86_64-linux-gnu/libz.so.1.2.3.4
7f35dd3dd000-7f35dd3de000 rw-p 00016000 fb:05 396605 /lib/x86_64-linux-gnu/libz.so.1.2.3.4
7f35dd3de000-7f35dd3e2000 r-xp 00000000 fb:05 393218 /lib/x86_64-linux-gnu/libuuid.so.1.3.0
7f35dd3e2000-7f35dd5e1000 ---p 00004000 fb:05 393218 /lib/x86_64-linux-gnu/libuuid.so.1.3.0
7f35dd5e1000-7f35dd5e2000 r--p 00003000 fb:05 393218 /lib/x86_64-linux-gnu/libuuid.so.1.3.0
7f35dd5e2000-7f35dd5e3000 rw-p 00004000 fb:05 393218 /lib/x86_64-linux-gnu/libuuid.so.1.3.0
7f35dd5e3000-7f35dd5ec000 r-xp 00000000 fb:05 526760 /usr/lib/libpils.so.2.0.0
7f35dd5ec000-7f35dd7eb000 ---p 00009000 fb:05 526760 /usr/lib/libpils.so.2.0.0
7f35dd7eb000-7f35dd7ec000 r--p 00008000 fb:05 526760 /usr/lib/libAborted (core dumped)
Maybe just cause I'm not giving it enough parameters??
Jake
----- Original Message -----
From: "Andrew Beekhof" <andrew at beekhof.net>
To: "Jake Smith" <jsmith at argotec.com>, "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
Cc: "Cal Heldenbrand" <cal at fbsdata.com>
Sent: Tuesday, October 23, 2012 6:24:51 PM
Subject: Re: [Pacemaker] crm_simulate a resource failure
On Wed, Oct 24, 2012 at 5:40 AM, Jake Smith <jsmith at argotec.com> wrote:
> Maybe try with verbose flag. Maybe try with error for the exit code? Or
> try $stop and $error to see if it will show anything - I would expect
> something like a node fence from that.
>
> crm_simulate with -LS for me causes seg fault so I can't test :-(
Really? What version?
>
> Jake
>
>
> ________________________________
> From: "Cal Heldenbrand" <cal at fbsdata.com>
> To: "Jake Smith" <jsmith at argotec.com>, "The Pacemaker cluster resource
> manager" <pacemaker at oss.clusterlabs.org>
> Sent: Tuesday, October 23, 2012 2:01:59 PM
> Subject: Re: [Pacemaker] crm_simulate a resource failure
>
>
> Thanks Jake, that at gives a little better description of the parameters,
> but I still just can't seem to get anything to trigger with the various
> syntaxes I'm trying. See below, I'm using single quotes so the $ symbol
> isn't parsed by bash. I've tried using my clone name, different return
> values, different task names, without the $ symbols... nothing seems to
> trigger anything in the Transition stuff. And I don't get any error
> messages at all.
>
> Any other ideas for me?
>
> Thanks!
>
> ---------------------------------------------------------------------------------
> [root at m3 /]# crm_simulate -LS
> --op-fail='$memcached:0_$monitor_$1@$m1.fbsdata.com=$not_running'
>
> Current cluster status:
> Online: [ m1.fbsdata.com m2.fbsdata.com m3.fbsdata.com ]
>
> Clone Set: memcached_clone [memcached]
> Started: [ m1.fbsdata.com m2.fbsdata.com m3.fbsdata.com ]
> cluster-ip-m1 (ocf::heartbeat:IPaddr2): Started m1.fbsdata.com
> cluster-ip-m2 (ocf::heartbeat:IPaddr2): Started m2.fbsdata.com
> cluster-ip-m3 (ocf::heartbeat:IPaddr2): Started m3.fbsdata.com
>
> Transition Summary:
>
> Executing cluster transition:
>
> Revised cluster status:
> Online: [ m1.fbsdata.com m2.fbsdata.com m3.fbsdata.com ]
>
> Clone Set: memcached_clone [memcached]
> Started: [ m1.fbsdata.com m2.fbsdata.com m3.fbsdata.com ]
> cluster-ip-m1 (ocf::heartbeat:IPaddr2): Started m1.fbsdata.com
> cluster-ip-m2 (ocf::heartbeat:IPaddr2): Started m2.fbsdata.com
> cluster-ip-m3 (ocf::heartbeat:IPaddr2): Started m3.fbsdata.com
> ---------------------------------------------------------------------------------
>
> On Tue, Oct 23, 2012 at 12:27 PM, Jake Smith <jsmith at argotec.com> wrote:
>>
>>
>> ----- Original Message -----
>>
>> > From: "Cal Heldenbrand" <cal at fbsdata.com>
>> > To: pacemaker at oss.clusterlabs.org
>> > Sent: Tuesday, October 23, 2012 11:50:11 AM
>> > Subject: [Pacemaker] crm_simulate a resource failure
>>
>> > Hi everyone,
>>
>> > I'm not able to find documentation or examples on this. If I have a
>> > cloned primitive set across a cluster, how can I simulate a failure
>> > of a resource on an individual node? I mainly want to see the scores
>> > on why a particular action is taken so I can adjust my configs.
>>
>> > I think the --op-fail parameter is what I need, but I just don't get
>> > the syntax of the value in the man page.
>>
>> I usually use the crm shell so I'm not positive but I think these are the
>> parts you need...
>>
>> $rsc_$task_$interval@$node=$rc
>>
>> $rsc = resource to test, in your case I believe you want to specify the
>> primitive instance of the clone i.e. p_resource:0
>> $task = monitor or migrate or stop or whatever operation you want to take
>> $interval = the interval of a monitor task
>> $node = the node
>> $rc = the exit code you want to fail with i.e. error, not_running
>>
>> So (I think) something like:
>> --op-fail=$p_of_clone_resource:0_$monitor_$10@$node1=$not_running
>>
>> You *should* be able to experiment till you get it just right since its
>> simulate.. :-)
>>
>> HTH
>>
>> Jake
>>
>> > Thank you!
>>
>> > --Cal
>>
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> > Project Home: http://www.clusterlabs.org
>> > Getting started:
>> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs: http://bugs.clusterlabs.org
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
More information about the Pacemaker
mailing list