<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks Kristoffer for answering<br>
<blockquote type="cite">
<pre wrap="">The corosync and pacemaker services are just regular services, and are
configured to start at boot just like any other service in sysvinit. That said, if
you have a two node cluster, starting the services at boot might not be
what you want since you can easily end up with a deathmatch
configuration.</pre>
</blockquote>
I noticed that corosync and pacemaker are regular services, in fact
if I start them from shell <i>/etc/init.d/corosync start</i> <i>/etc/init.d/pacemaker
start</i> they both seem to work.<br>
<br>
You say that having them at boot is not a good configuration
(possible deathmatch), but how can I ensure the cluster stays always
up if I don't have that? What is the best practice?<br>
<br>
In my previous cluster configuration I used the Debian Wheezy
apt-get binaries (corosync v1.4.2 and pacemaker v1.1.7) and all I
had to do was setting a START variale to yes in
/etc/default/corosync on both nodes.<br>
(as described here
<a class="moz-txt-link-freetext" href="http://zeldor.biz/2010/12/activepassive-cluster-with-pacemaker-corosync/">http://zeldor.biz/2010/12/activepassive-cluster-with-pacemaker-corosync/</a>)<br>
<br>
<blockquote type="cite">
<pre wrap="">If adding them to runlevels doesn't work, there's a bug of some sort.</pre>
</blockquote>
I thought there was a bug in the init.d scripts, but I cannot find
any so far.<br>
I was looking for someone who had done this on Debian, because I am
starting to think maybe I am picking the wrong runlevels, should I
change defaults to specific runlevels?<br>
<pre>update-rc.d corosync defaults
update-rc.d pacemaker defaults
</pre>
<blockquote type="cite">
<pre wrap="">There's a basic guide here: <a class="moz-txt-link-freetext" href="http://crmsh.github.io/start-guide/">http://crmsh.github.io/start-guide/</a></pre>
</blockquote>
While googling I also found the guide you mentioned, but all I could
find are commands to configure corosync, configure pacemaker start
and stop the cluster. <br>
No way to make crmsh a daemon that starts the cluster at boot (if
this is the right thing to do to obtain a cluster on even after a
temporary node failure like an AC power failure)<br>
<blockquote type="cite">
<pre wrap="">I'm working on a crmsh version of the official documentation, but it's
not online yet unfortunately.</pre>
</blockquote>
<br>
That would be great! Do you think you'll be able to share the crmsh
version of documentation soon? <br>
<blockquote type="cite">
<pre wrap="">The crmsh commands simply call
"service corosync start; service pacemaker start"
and
"service pacemaker stop; service corosync stop"
</pre>
</blockquote>
That is what I thought and what I found evince of while I was
googling online, corosync and pacemaker must be started in an order
and stopped in the opposite one, I was planning to do that on Debian
by renaming the symlinks in rc.d but I haven't got to that point
because update-rc.d doesn't create any symlinks for corosync and
pacemaker when I issue the two commands I wrote before. That's why I
am wondering about specifying different runlevels.<br>
<br>
<blockquote type="cite">
<pre wrap="">
To be honest this has only been tested on SUSE distros by me. I'd be
happy for patches to make this work properly on Debian. :)
</pre>
</blockquote>
Anyway I could help, I'd be glad to make the latest stable cluster
stack (corosync + pacemaker) work on Debian with compiled sources. <br>
I thought mine was a common problem because there was this compiling
guide on the official website
(<a class="moz-txt-link-freetext" href="http://clusterlabs.org/wiki/Compiling_on_Debian">http://clusterlabs.org/wiki/Compiling_on_Debian</a>) so I thought more
people used this OS for clustering, and some already encountered my
problem.<br>
<br>
Thanks again<br>
Danilo<br>
<br>
<div class="moz-signature">
<hr align="left" color="#000080" size="1" width="282">
<pre wrap="">
</pre>
</div>
</body>
</html>