Hi,
When specifying the node name in UPPER case and performing
crm_resource, crmd was aborted.
(The real node name is a LOWER case.)
# crm_resource -C -r p1 -N X3650H
Cleaning up p1 on X3650H
Waiting for 1 replies from the CRMdNo messages received in 60 seconds.. aborting
Mar 14 18:33:10 x3650h crmd[10718]: error: crm_abort:
do_lrm_invoke: Triggered fatal assert at lrm.c:1240 : lrm_state !=
NULL
...snip...
Mar 14 18:33:10 x3650h pacemakerd[10708]: error: child_waitpid:
Managed process 10718 (crmd) dumped core
* The state before performing crm_resource.
----
Stack: corosync
Current DC: x3650g (3232261383) - partition with quorum
Version: 1.1.10-38c5972
2 Nodes configured
3 Resources configured
Online: [ x3650g x3650h ]
Full list of resources:
f-g (stonith:external/ibmrsa-telnet): Started x3650h
f-h (stonith:external/ibmrsa-telnet): Started x3650g
p1 (ocf::pacemaker:Dummy): Stopped
Migration summary:
* Node x3650g:
* Node x3650h:
p1: migration-threshold=1 fail-count=1 last-failure='Fri Mar 14
18:32:48 2014'
Failed actions:
p1_monitor_10000 on x3650h 'not running' (7): call=16,
status=complete, last-rc-change='Fri Mar 14 18:32:48 2014',
queued=0ms, exec=0ms
----
Just for reference, similar phenomenon did not occur by crm_standby.
$ crm_standby -U X3650H -v on
Best Regards,
Kazunori INOUE
_______________________________________________
Pacemaker mailing list: Pacemaker@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
