Hi Andreas,
just a comment while I guess what your misunderstanding may come from. When services are clustered you often see a filesystem resource which is moved between the cluster nodes and on top of that filesystem resource is a service (call it S) which is also handled by the cluster. (colocation, groups, etc.) BUT: You have to be aware of one fact. The resource agents mostly rely on some service (S) related binaries to do there job. So if the binaries are not on every node the monitor action of the resource agent fails and the behaviour of the cluster is not what you like. So, most of the time you have to design your stack of resources in a way that the binaries of the service S is on every node in any case and is exactly the same on any node. I once wrote a resource agent which was clever enough to do a multiphase monitor action, checking first if there are expected binaries found. And if not assuming that the service can't be run. In this special case we were able to move the whole service S's binaries with the filesystem resource. But this is uncommon and mostly you don't like it. Best regards Andreas Mock Von: andreas graeper [mailto:agrae...@googlemail.com] Gesendet: Donnerstag, 6. Juni 2013 16:26 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] failed actions after resource creation hi and thanks. (better sentences: i will give my best) on inactive node there is actually only /etc/init.d/nfs and neither nfs-common nor nfs-kernel-server. is monitor not only looking for the running service on active node, but for the situation on inactive node, too ? so i would have expected, that the missing nfs-kernel-server was reported, too. i guess, this can be handled only with a init-script 'nfs' (same name on both nodes) that is starting/killing nfs-commo/nfs-kernel-server ? or is there another solution ? what is monitor in case of resource managed by lsb-script doing ? is it calling `service xxx status` ? what does the monitor expect on node where service is running / not running ? thanks in advance andreas 2013/6/6 Florian Crouzat <gen...@floriancrouzat.net> Le 06/06/2013 15:49, andreas graeper a écrit : p_nfscommon_monitor_0 (node=linag, call=189, rc=5, status=complete): not installed Sounds obvious: "not installed". Node "linag" is missing some daemons/scripts , probably nfs-related. Check your nfs packages and configuration on both nodes, node1 should be missing something. what can i do ? Better sentences. -- Cheers, Florian Crouzat _______________________________________________ Pacemaker mailing list: Pacemaker@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
_______________________________________________ Pacemaker mailing list: Pacemaker@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
