Good! with 1.1 I have the init script. <br>Now the problem is different: pacemaker doesn't start!<br><br>this is the error:<br><br># pacemakerd -f -V<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'corosync_quorum' for option: name<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'corosync_cman' for option: name<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_clm' for option: name<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_evt' for option: name<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_ckpt' for option: name<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_msg' for option: name<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_lck' for option: name<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional service options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'openais_tmr' for option: name<br>
pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: No additional configuration supplied for: service<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: config_find_next: Processing additional quorum options...<br>pacemakerd[3389]: 2012/02/13_13:02:15 info: get_config_opt: Found 'quorum_cman' for option: provider<br>
pacemakerd[3389]: 2012/02/13_13:02:16 info: get_cluster_type: Detected an active 'cman' cluster<br>pacemakerd[3389]: 2012/02/13_13:02:16 CRIT: get_cluster_type: This installation of Pacemaker does not support the 'cman' cluster infrastructure. Terminating.<br>
<br><br><div class="gmail_quote">2012/2/13 Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Feb 13, 2012 at 8:01 AM, diego fanesi <<a href="mailto:diego.fanesi@gmail.com">diego.fanesi@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I'm trying to install corosync with pacemaker using drbd + gfs2 with cman<br>
> support.<br>
><br>
> I installed corosync + pacemaker and all worked fine. Then I tried to add<br>
> cman but to use it I have to start corosync from cman. cman doesn't consider<br>
> corosync.conf (and services.d/*) and if you want to modify default settings<br>
> of corosync defined by cman, you have to add these informations in your<br>
> cluster.conf.<br>
><br>
> In this file are not allowed all possible configurations of corosync.conf<br>
> and there aren't any way to add services that corosync will run at startup.<br>
><br>
> In debian there are no init scripts for pacemaker and I need to start it<br>
> from corosync.conf using the section "service".<br>
<br>
</div>It sounds like you're using 1.0.x?<br>
Have you tried 1.1.x from backports?<br>
<br>
To use pacemaker+cman, you /must/ use the pacemaker init script.<br>
<div class="im"><br>
><br>
> My problem is that: I need to start pacemaker from corosync.conf (or<br>
> services.d/pmkr) but if this file is not considered by cman I haven't other<br>
> ways to start pacemaker with corosync + cman.<br>
><br>
> Can someone help me?<br>
><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" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
<br>
_______________________________________________<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" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote></div><br>