<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#0050d0">
<br>
<br>
Sent: Wed Dec 15 2010 09:10:12 GMT-0700 (Mountain Standard Time)<br>
From: Dejan Muhamedagic <a class="moz-txt-link-rfc2396E" href="mailto:dejanmm@fastmail.fm"><dejanmm@fastmail.fm></a><br>
To: The Pacemaker cluster resource manager
<a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@oss.clusterlabs.org"><pacemaker@oss.clusterlabs.org></a> <br>
Subject: Re: [Pacemaker] colocation issues (isnt it always)
<blockquote cite="mid:20101215161011.GC2549@rondo.homenet" type="cite">
<pre wrap="">Hi,
On Mon, Dec 13, 2010 at 07:08:52PM -0700, Patrick H. wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Sent: Mon Dec 13 2010 15:19:48 GMT-0700 (Mountain Standard Time)
From: Pavlos Parissis <a class="moz-txt-link-rfc2396E" href="mailto:pavlos.parissis@gmail.com"><pavlos.parissis@gmail.com></a>
To: The Pacemaker cluster resource manager <a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@oss.clusterlabs.org"><pacemaker@oss.clusterlabs.org></a>
Subject: Re: [Pacemaker] colocation issues (isnt it always)
</pre>
<blockquote type="cite">
<pre wrap="">If you put all of them in a group and have the nfs_sdb1 as last
resource you will manage to have what you want with a very simple
configuration
BTW, I used your conf and in my case all resources started on the same node
</pre>
</blockquote>
<pre wrap="">I futzed around with it some more and the problem was the nfsserver
resource. It wasnt properly detecting that it wasnt running on the
'nas02' node. When I first added the resource it wasnt in the
colocation rule, so it started up on 'nas02' (or it thought it did),
and then I added the colocation rule. Well the monitor action was
reporting that the service was running when it really wasnt. So
every time it went to shut it down and move it to another node, it
failed cause it thought it was still running. I ended up writing my
own script with a working monitor function and it moved over just
fine.
</pre>
</blockquote>
<pre wrap=""><!---->
nfsserver actually uses your distribution init script:
nfs_init_script (string, [/etc/init.d/nfsserver]): Init script for nfsserver
The default init script shipped with the Linux distro.
The nfsserver resource agent offloads the start/stop/monitor
work to the init script because the procedure to start/stop/monitor nfsserver
varies on different Linux distro.
It looks like you need to report a bug to your vendor for the
NFS server init script.
</pre>
</blockquote>
No, the problem wasnt the nfs server init script, that worked
perfectly, and in the script I'm using that I wrote to replace
nfsserver i'm using the system's init script as well. The problem was
with the nfsserver script improperly thinking that nfs was active, even
when it wasnt. The path that nfs stores its state data (/var/lib/nfs)
didnt even exist and it still said it was running. That was the problem.<br>
<blockquote cite="mid:20101215161011.GC2549@rondo.homenet" type="cite">
<pre wrap="">Thanks,
Dejan
_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
</pre>
</blockquote>
</body>
</html>