[Pacemaker] crm command line tool problem

Joe Armstrong jarmstrong at postpath.com
Fri May 22 11:51:45 EDT 2009


Hi All,

I am playing around with the crm command line tool to create an HA config for pacemaker and am bumping into a problem.

If I have a configuration running already, 3-node with ip & httpd (pretty simple) and I want to create a new configuration according to the "CRM CLI" document I should:

	crm configure erase

and then create my new configuration.  But the "erase" directive also blows away my cluster node definitions.  If I manually put them back again:

	crm configure node vm1
        crm configure node vm2
        crm configure node vm4

I get this:

	============
	Last updated: Fri May 22 08:32:16 2009
	Current DC: NONE
	3 Nodes configured, unknown expected votes
	0 Resources configured.
	============

	Node vm1: UNCLEAN (offline)
	Node vm2: UNCLEAN (offline)
	Node vm4: UNCLEAN (offline)

Now, now matter what I seem to do I can't get the nodes back to the online state.  And worse, if I try to shutdown heartbeat all nodes try to kill all other nodes and crmd won't shutdown (if I kill crmd "Bad Things"(TM) happen).

Is there a way I can either:
	- remove all resources/constraints but leave the node definitions (I did this by manually removing each resource and it works fine, but this seems like a pain in a large config)
	- get the cluster nodes to see each other again
	- do something before the "erase" so the nodes don't go to the UNCLEAN state

Thanks.

Joe




More information about the Pacemaker mailing list