Le 06/06/2013 16:25, andreas graeper a écrit :
hi and thanks. (better sentences: i will give my best)
Okay
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 ?
Well, the main goal of a cluster is the ability to move resources between members in case of failures of the hosting node so yes, of course pacemaker checks the capacity of all cluster nodes to host the resources ..
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 ?
If you want to clusterize nfs, than have all your node nfs-ready, otherwise, I really don't see what is your inactive node good for ?
what is monitor in case of resource managed by lsb-script doing ? is it calling `service xxx status` ?
Yes.
what does the monitor expect on node where service is running / not running ?
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/ap-lsb.html
thanks in advance andreas
You are welcome.
2013/6/6 Florian Crouzat <gen...@floriancrouzat.net <mailto: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
-- 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
