<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi,
<div><br>
</div>
<div>Initially I had the following resource setup.</div>
<div><br>
</div>
<div>
<div>1. Clone -> Group -> Primitives (ocf:pacemaker:controld, ocf:ocfs2:o2cb)</div>
</div>
<div>2. Clone -> Primitives (ocf:heartbeat:Filesystem)</div>
<div>3. Group -> Primitives (ocf:heartbeat:IPaddr2, ocf:heartbeat:mysql)</div>
<div><br>
</div>
<div>I had a resource colocation where 3, 2 and 1 would all need to run on the same node.</div>
<div>I had a resource location preference for 3 on node 1.</div>
<div>I had an order constraint of 1 -> 2 -> 3</div>
<div><br>
</div>
<div>In the above scenario, I had issues of resource getting restarted when any of the nodes in the cluster rebooted. I added the Time-based rule later and noticed the same again, so the resource restarting is probably not because of the Time-based rule as
you mentioned.</div>
<div><br>
</div>
<div>I have changed my config since to below:</div>
<div><br>
</div>
<div>1. Clone -> group -> primitives (1 - ocf:pacemaker:controld, 2 - ocf:ocfs2:o2cb, 3 - ocf:heartbeat:Filesystem)</div>
<div>2. Group -> Primitives (ocf:heartbeat:IPaddr2, ocf:heartbeat:mysql)</div>
<div><br>
</div>
<div>I have a resource colocation where 2 would run where primitive 3 of Clone above is running.</div>
<div>I have a resource location preference for 2 on node 1.</div>
<div>I have an order constraint of primitive 3 of Clone -> 2</div>
<div><br>
</div>
<div>Now, I am unable to start the MySQL resource 2 on node 1 at all because of some kind of locking.</div>
<div><br>
</div>
<div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>InnoDB: Unable to lock ./ibdata1, error: 38</div>
<div>120626 15:01:48 InnoDB: Unable to open the first data file</div>
<div>InnoDB: Error in opening ./ibdata1</div>
<div>120626 15:01:48 InnoDB: Operating system error number 38 in a file operation.</div>
<div>InnoDB: Error number 38 means 'Function not implemented'.</div>
<div>InnoDB: Some operating system error numbers are described at</div>
<div>InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html">
http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html</a></div>
<div>120626 15:01:48 InnoDB: Could not open or create data files.</div>
<div>120626 15:01:48 InnoDB: If you tried to add new data files, and it failed here,</div>
<div>120626 15:01:48 InnoDB: you should now edit innodb_data_file_path in my.cnf back</div>
<div>120626 15:01:48 InnoDB: to what it was, and remove the new ibdata files InnoDB created</div>
<div>120626 15:01:48 InnoDB: in this failed attempt. InnoDB only wrote those files full of</div>
<div>120626 15:01:48 InnoDB: zeros, but did not yet use them in any way. But be careful: do not</div>
<div>120626 15:01:48 InnoDB: remove old data files which contain your precious data!</div>
<div>120626 15:01:48 [ERROR] Plugin 'InnoDB' init function returned error.</div>
<div>120626 15:01:48 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.</div>
<div>120626 15:01:48 [ERROR] Unknown/unsupported storage engine: InnoDB</div>
<div>120626 15:01:48 [ERROR] Aborting</div>
<div><br>
</div>
<div>Any idea? Can a resource order constraint be specified depending on a primitive that is part of a clone resource? Is that even supported?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Prakash</div>
<div><br>
</div>
<div>
<div>On Jun 26, 2012, at 1:48 PM, Phil Frost wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/26/2012 12:59 PM, Velayutham, Prakash wrote:<br>
</div>
<blockquote cite="mid:CFD613AA-9636-4A56-81FE-7EB9E9DE6E9A@cchmc.org" type="cite">
Hi,<br>
<br>
I have a Corosync (1.3.0-5.6.1) / Pacemaker (1.1.5-5.5.5) cluster where I am using a Time-based rule for resource stickiness (<a moz-do-not-send="true" href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-rules-cluster-options.html">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-rules-cluster-options.html</a>).<br>
<br>
Everything works as expected, except that the resources get stopped and restarted on the same node during the core-hours if any other node in the cluster gets rebooted. The stickiness works, but I would prefer that the resources do not get affected this way.
Would anyone know what I have configured wrong?<br>
</blockquote>
<br>
If you delete your time-based rules, do you still have these undesired restarts? Maybe the restarts are due to something else entirely, like maybe an order constraint on a clone. There was a bug some time ago regarding this, but I've found configurations where
it's still a problem. More here:<br>
<br>
<a class="moz-txt-link-freetext" href="https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2153">https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2153</a><br>
</div>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: http://www.clusterlabs.org<br>
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>
Bugs: http://bugs.clusterlabs.org<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>