<!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="#000000">
Hi Andrew, <br>
<br>
thanks for the pointer. It turns out that running the
Filesystem-monitor operation on the nfs server killed it since it too
had a /data filesystem mounted, which then (mistakenly) was being
unmounted causing the crash... Changing the mountpoint on the
apachefs-resource fixed this. However, now I see the apachefs-service
being tried to run TWICE on each apa-node! From my log:<br>
<br>
lrmd[3101]: 2009/05/19_13:09:25 debug: on_msg_perform_op: add an
operation operation start[11] on ocf::Filesystem::apachefs:0 for client
3104, its parameters: directory=[/var/www] fstype=[nfs]
device=[192.168.202.47:/data/export] CRM_meta_timeout=[20000]
CRM_meta_clone_max=[2] crm_feature_set=[3.0.1]
CRM_meta_globally_unique=[false] CRM_meta_clone=[0]
CRM_meta_clone_node_max=[1] to the operation list.<br>
lrmd[3101]: 2009/05/19_13:09:25 info: rsc:apachefs:0: start<br>
stonithd[3102]: 2009/05/19_13:09:25 debug: external_set_config: called.<br>
stonithd[3102]: 2009/05/19_13:09:25 debug: external_get_confignames:
called.<br>
lrmd[3101]: 2009/05/19_13:09:25 debug: on_msg_add_rsc:client [3104]
adds resource apachefs:1<br>
crmd[3104]: 2009/05/19_13:09:25 info: do_lrm_rsc_op: Performing
key=55:14:0:e38d2516-b13e-4c2f-b44d-86e574c7dcb7 op=apachefs:1_start_0 )<br>
lrmd[3101]: 2009/05/19_13:09:25 debug: on_msg_perform_op:2356: copying
parameters for rsc apachefs:1<br>
lrmd[3101]: 2009/05/19_13:09:25 debug: on_msg_perform_op: add an
operation operation start[12] on ocf::Filesystem::apachefs:1 for client
3104, its parameters: directory=[/var/www] fstype=[nfs]
device=[192.168.202.47:/data/export] CRM_meta_timeout=[20000]
CRM_meta_clone_max=[2] crm_feature_set=[3.0.1]
CRM_meta_globally_unique=[false] CRM_meta_clone=[1]
CRM_meta_clone_node_max=[1] to the operation list.<br>
lrmd[3101]: 2009/05/19_13:09:25 info: rsc:apachefs:1: start<br>
<br>
It tried modifying the apache clone line to 'clone apache apacheservice
meta clone-max="2" clone-node-max="1"' (which shouldn't be necessary)
but that didn;'t help either...<br>
<br>
Should I maybe NOT use a clone for this and write out two seperate
apache-configs for both nodes?<br>
<br>
Andrew Beekhof wrote:
<blockquote
cite="mid:b80f82d20905190157q3a0c2b4aic7fa81b61ec7ad7e@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, May 19, 2009 at 10:24 AM, Mark Schenk <a class="moz-txt-link-rfc2396E" href="mailto:M.M.A.Schenk@tudelft.nl"><M.M.A.Schenk@tudelft.nl></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I am trying to run cloned resources on part of my cluster, however I must
be mistaken on how to use the location-directive. This is the relevant part
of my config:
node $id="8ce10d28-174c-4fc3-bac4-b2bf21ef6a38" apa1
node $id="09c41339-21db-4250-83b9-bac11a6c25de" apa2
node $id="ea3da999-829d-4042-a5d5-9ee0ad27f989" mysql1
node $id="23f84b10-ad8c-43a9-ab23-344d06254948" mysql2
node $id="47c29bf2-ac4a-4873-9b91-f05b8e41af2d" nfs1
node $id="e588fc86-92d8-4658-a394-3e031171bcd0" nfs2
primitive apachefs ocf:heartbeat:Filesystem \
params device="192.168.202.47:/data/export" directory="/data"
fstype="nfs"
primitive apacheserver ocf:heartbeat:Dummy
group apacheservice apachefs apacheserver
clone apache apacheservice \
meta clone-max="2"
location apaapa1 apache 100: apa1
location apaapa2 apache 100: apa2
property $id="cib-bootstrap-options" \
dc-version="1.0.3-b133b3f19797c00f9189f4b66b513963f9d25db9" \
symmetric-cluster="false" \
last-lrm-refresh="1242719884"
What I thought this would do was: start (cloned) resources apachefs and
apacheserver only on nodes apa1 and apa2 (since symmetric-cluster=false and
having the two location directives). What I can see happening is that the
apachefs resource is tried on other nodes as well, most importantly also on
nfs1 and nfs2, which causes these to crash :-(. Could someone point out how
I can get this working the way I want?
</pre>
</blockquote>
<pre wrap=""><!---->
It shouldn't be starting apache anywhere except apa1 & 2, but we do
check _every_ node to see if its running (so that we can satisfy the
constraints by stopping apache if we find it running somewhere it
shouldn't be).
_______________________________________________
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>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
_____________________________________________________________________
Mark Schenk
Project Manager
Shared Service Centre ICT - 3xO
Technische Universiteit Delft
<a class="moz-txt-link-abbreviated" href="mailto:M.M.A.Schenk@tudelft.nl">M.M.A.Schenk@tudelft.nl</a>
Room 3B-41
Postbus 354
2600 AJ Delft
Landbergstraat 15
2628 CE DELFT ___________________________________________
+31 (0)15 27 85448 | Reality is that which, when you
<a class="moz-txt-link-abbreviated" href="http://www.tudelft.nl">www.tudelft.nl</a> | stop believing in it, doesn't go away.
_____________________________________________________________________
</pre>
</body>
</html>