<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Sync Cluster Configuration and Verify Failover Setup in Nodes &#8211; Part 4	</title>
	<atom:link href="https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Sun, 11 Oct 2020 09:47:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Shibin		</title>
		<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-1372299</link>

		<dc:creator><![CDATA[Shibin]]></dc:creator>
		<pubDate>Sun, 11 Oct 2020 09:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=16263#comment-1372299</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-914296&quot;&gt;Vaibhav&lt;/a&gt;.

Make sure you stopped iptables on both nodes.  If you need that to be run, then add the necessary rules.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-914296">Vaibhav</a>.</p>
<p>Make sure you stopped iptables on both nodes.  If you need that to be run, then add the necessary rules.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Arun Ghanta		</title>
		<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-1047467</link>

		<dc:creator><![CDATA[Arun Ghanta]]></dc:creator>
		<pubDate>Sat, 13 Oct 2018 00:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=16263#comment-1047467</guid>

					<description><![CDATA[There are many things that don&#039;t make sense. 

The LVM that&#039;s added, is that a shared storage between all nodes or is it local to cluster server?

If that is a local storage, what happens when the cluster server goes down. The data that&#039;s on LVM which local to cluster server gets replicated across all nodes. If so to which location on member nodes?
&lt;ul&gt;
&lt;li&gt;There must be some packages that coordinate with LVM with cluster services. I am sure we can&#039;t straight up add an LVM to cluster resources.&lt;/li&gt;
&lt;li&gt;On top of all these.. The other nodes in the cluster just have ricci started and wait for the configuration come from cluster server to join and sync.&lt;/li&gt;
&lt;li&gt;No offense but the article is half-baked. Tecmint should retire this page. Misleading and ending up half-way is what we don&#039;t expect from tech articles.&lt;/li&gt;
&lt;/ul&gt;]]></description>
			<content:encoded><![CDATA[<p>There are many things that don&#8217;t make sense. </p>
<p>The LVM that&#8217;s added, is that a shared storage between all nodes or is it local to cluster server?</p>
<p>If that is a local storage, what happens when the cluster server goes down. The data that&#8217;s on LVM which local to cluster server gets replicated across all nodes. If so to which location on member nodes?</p>
<ul>
<li>There must be some packages that coordinate with LVM with cluster services. I am sure we can&#8217;t straight up add an LVM to cluster resources.</li>
<li>On top of all these.. The other nodes in the cluster just have ricci started and wait for the configuration come from cluster server to join and sync.</li>
<li>No offense but the article is half-baked. Tecmint should retire this page. Misleading and ending up half-way is what we don&#8217;t expect from tech articles.</li>
</ul>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Parthiban		</title>
		<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-996637</link>

		<dc:creator><![CDATA[Parthiban]]></dc:creator>
		<pubDate>Fri, 25 May 2018 14:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=16263#comment-996637</guid>

					<description><![CDATA[Dear Brother,
 
Interesting lesson, I got a validation error in &quot;&lt;strong&gt;ccs -h 172.16.1.250 --addresource fs name=my_fs device=/dev/mapper/tecminttest_lv_vol01 mountpoint=/x01 fstype=ext3&lt;/strong&gt;&quot; this part below commend I have tried &quot;&lt;strong&gt;ccs -h 192.168.1.87 --addresource fs name=my_fs device=/dev/sda4 mountpoint=/test fstype=ext4&lt;/strong&gt;&quot; kindly need a advice the session.

Thanks 
Parthiban]]></description>
			<content:encoded><![CDATA[<p>Dear Brother,</p>
<p>Interesting lesson, I got a validation error in &#8220;<strong>ccs -h 172.16.1.250 &#8211;addresource fs name=my_fs device=/dev/mapper/tecminttest_lv_vol01 mountpoint=/x01 fstype=ext3</strong>&#8221; this part below commend I have tried &#8220;<strong>ccs -h 192.168.1.87 &#8211;addresource fs name=my_fs device=/dev/sda4 mountpoint=/test fstype=ext4</strong>&#8221; kindly need a advice the session.</p>
<p>Thanks<br />
Parthiban</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pila		</title>
		<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-983598</link>

		<dc:creator><![CDATA[pila]]></dc:creator>
		<pubDate>Tue, 17 Apr 2018 17:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=16263#comment-983598</guid>

					<description><![CDATA[Hello interesting documentation friend I&#039;m lost in this part.

ccs -h 172.16.1.250 --addresource fs name = my_fs device = / dev / mapper / tecminttest_lv_vol01 mountpoint = / x01 fstype = ext3

my question is the following one, is to know if you already have created this file system &lt;strong&gt;/dev/mapper/tecminttest_lv_vol01&lt;/strong&gt; and create it and then mount it.]]></description>
			<content:encoded><![CDATA[<p>Hello interesting documentation friend I&#8217;m lost in this part.</p>
<p>ccs -h 172.16.1.250 &#8211;addresource fs name = my_fs device = / dev / mapper / tecminttest_lv_vol01 mountpoint = / x01 fstype = ext3</p>
<p>my question is the following one, is to know if you already have created this file system <strong>/dev/mapper/tecminttest_lv_vol01</strong> and create it and then mount it.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nike Leung		</title>
		<link>https://www.tecmint.com/sync-cluster-configuration-and-verify-failover-setup-in-nodes/comment-page-1/#comment-967775</link>

		<dc:creator><![CDATA[Nike Leung]]></dc:creator>
		<pubDate>Thu, 08 Feb 2018 20:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=16263#comment-967775</guid>

					<description><![CDATA[Following the step 3 and ran &quot;&lt;strong&gt;ccs -h 172.16.1.250 --sync --activate&lt;/strong&gt;&quot; but showing the error with &quot;&lt;strong&gt;unable to connect to 172.16.1.222&lt;/strong&gt;, make sure the ricci server is started&quot;.

Then, I ran &quot;&lt;strong&gt;service ricci status&lt;/strong&gt;&quot; for all three servers that showing &quot;&lt;strong&gt;ricci (pid 1863) is running&lt;/strong&gt;&quot;....no idea what to do next. Please advice.]]></description>
			<content:encoded><![CDATA[<p>Following the step 3 and ran &#8220;<strong>ccs -h 172.16.1.250 &#8211;sync &#8211;activate</strong>&#8221; but showing the error with &#8220;<strong>unable to connect to 172.16.1.222</strong>, make sure the ricci server is started&#8221;.</p>
<p>Then, I ran &#8220;<strong>service ricci status</strong>&#8221; for all three servers that showing &#8220;<strong>ricci (pid 1863) is running</strong>&#8220;&#8230;.no idea what to do next. Please advice.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
