<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Everyone,</p>
<p><br>
</p>
<blockquote
cite="mid:09ba05de-cec0-d649-32b1-64ad4221adf0@itsts.net"
type="cite">So my question is - why Corosync didn't work correctly
if it start under Pacemaker? <br>
</blockquote>
<p>Finally I found the answer.</p>
<p>In short - it was caused by the wrong settings of local name
resolver.</p>
<p>/etc/cluster/cluster.conf contain the similar settings for each
node:</p>
<p><clusternode name="NODE17.local" nodeid="17"><br>
<fence><br>
<method name="pcmk-redirect"><br>
<device name="pcmk" port="NODE17"/><br>
</method><br>
</fence><br>
<altname name="NODE17.pub"/><br>
</clusternode></p>
where <br>
NODE17.local point to private IP address<br>
NODE17.pub point to public IP address<br>
<br>
Due to configuration error on the latest NODE17 the internal name
NODE17.local <span class="gt-baf-word-clickable">improperly </span>resolved
to the public IP (NODE17.pub).<br>
In such case command 'corosync-cfgtool -s' on the latest added node
NODE17 printed status looks like:<br>
Local node ID 17<br>
RING ID 0<br>
id = 111.11.11.1<br>
Marking ringid 0 interface 111.11.11.1 FAULTY<br>
RING ID 1<br>
id = 111.11.11.1<br>
status = ring 1 active with no faults<br>
<br>
As well as RING ID 0 was marked as FAULTY on all 17 nodes.<br>
After name resolution has fixed - both rings are operating as
expected .<br>
<br>
I think the error would be resolved much quickly if I will used
newest pacemaker/corosync versions,<br>
since both of them has many improvements/fixes applied to logging
subsystems.<br>
<br>
Thanks everyone who found ability to help me, and be <span
id="result_box" class="short_text" lang="en"><span>be careful to
DNS names when you're using similar configuration :)<br>
<br>
</span></span>--
<pre class="moz-signature" cols="72">Regards Denis Gribkov</pre>
</body>
</html>