[Pacemaker] Cannot Create Primitive in CRM Shell

[Andrew Martin]

Hi Florian, 


Thanks for the quick response. This is a fresh install of pacemaker/heartbeat on two VMs so it should not have any previous/corrupted configuration (Ubuntu 10.04 amd64). I had previously deployed pacemaker on alternative copies of these VM images, but both of those have since been deleted. I am using the versions of these packages from the Ubuntu HA PPA because the Lucid version does not appear to contain ocf:heartbeat:exportfs. 


Here's the output of "crm_mon -1", which appears normal: 

# crm_mon -1 
============ 
Last updated: Mon Jan 9 07:56:23 2012 
Last change: Fri Jan 6 12:20:20 2012 via cibadmin on host1 
Stack: Heartbeat 
Current DC: host1 (e7dd6b7b-83ee-45bd-9768-bf576260ff15) - partition with quorum 
Version: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c 
2 Nodes configured, unknown expected votes 
0 Resources configured. 
============ 


Online: [ host1 host2 ] 


I issued "crm configure erase" and then performed the following operations after running "crm configure": 

property stonith-enabled="false" 
property no-quorum-policy="ignore" 
rsc_defaults resource-stickiness="200" 
commit 

primitive p_exportfs_drive \ 
ocf:heartbeat:exportfs \ 
params fsid=1 \ 
directory="/tmp" \ 
options="rw,mountpoint" \ 
clientspec="10.10.0.0/255.255.0.0" \ 
wait_for_leasetime_on_stop=true \ 
op monitor interval="30s" 


I have attached the syslog from these operations as well as a copy of the configuration as exported via "cibadmin --query > /tmp/pacemaker_config.xml". I am also including a copy of the portion of the strace from when I entered 'op monitor interval="30s"' at the end of the exportfs primitive and then hit the Enter key (and the crm shell remains frozen). 


Any ideas of what else I can try to fix the crm shell on these nodes? 


Thanks, 


Andrew 




----- Original Message -----

From: "Florian Haas" < florian at hastexo.com > 
To: "The Pacemaker cluster resource manager" < pacemaker at oss.clusterlabs.org > 
Sent: Monday, January 9, 2012 5:44:55 AM 
Subject: Re: [Pacemaker] Cannot Create Primitive in CRM Shell 

On Mon, Jan 9, 2012 at 11:42 AM, Dan Frincu < df.cluster at gmail.com > wrote: 
> Hi, 
> 
> On Fri, Jan 6, 2012 at 11:24 PM, Andrew Martin < amartin at xes-inc.com > wrote: 
>> Hello, 
>> 
>> I am working with DRBD + Heartbeat + Pacemaker to create a 2-node 
>> highly-available cluster. I have been following this official guide on 
>> DRBD's website for configuring all of the components: 
>> http://www.linbit.com/fileadmin/tech-guides/ha-nfs.pdf 
>> 
>> However, once I go to configure the primitives in pacemaker's CRM shell 
>> (section 4.1 in the PDF above) I am unable to create the primitive. For 
>> example, I enter the following configuration for a DRBD device called 
>> "drive": 
>> primitive p_drbd_drive \ 
>> 
>> ocf:linbit:drbd \ 
>> 
>> params drbd_resource="drive" \ 
>> 
>> op monitor interval="15" role="Master" \ 
>> 
>> op monitor interval="30" role="Slave" 
>> 
>> After entering all of these lines I hit enter and nothing is returned - it 
>> appears frozen and I am never returned to the "crm(live)configure# " shell. 
>> An strace of the process does not reveal any obvious blocks. I have also 
>> tried entering the entire configuration on a single line with the same 
>> result. 
> 
> I would recommend going through this guide first 
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/ 

That's a bit of a knee-jerk response if I may say so, and when I wrote 
those guides[1] the intention was specifically that people could 
peruse them _without_ first having to check the documentation that 
covers the configuration internals. 

At any rate, Andrew, if your crm shell is freezing up when you're 
simply trying to add a primitive, something must be seriously awry in 
your setup -- it's something that I've not run into personally, unless 
the cluster was already responding to an error state on one of the 
nodes. Are you sure your cluster is behaving OK otherwise? Are you 
getting meaningful output from "crm_mon -1"? Does your cluster report 
it has successfully elected a DC? 

Cheers, 
Florian 

[1] Which I did while employed by Linbit, which is no longer the case, 
as they have asked I point out. http://wp.me/p4XzQ-bN 

-- 
Need help with High Availability? 
http://www.hastexo.com/now 

_______________________________________________ 
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 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120109/4bd90718/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pacemaker_config.xml
Type: application/xml
Size: 2591 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120109/4bd90718/attachment-0003.wsdl>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog
Type: application/octet-stream
Size: 12194 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120109/4bd90718/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: strace
Type: application/octet-stream
Size: 3399 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120109/4bd90718/attachment-0007.obj>