Re: New user can't get cman to recognize other systems

Andrew Beekhof <[email protected]>
Newsgroups gmane.linux.highavailability.user
Message-ID <[email protected]>
> On 21 Oct 2014, at 7:17 am, John Scalia <[email protected]> wrote:
> 
> Thanks, but on centOS are you saying to use "pcs cluster start" rather than using "service cman start" and "service pacemaker start"? I was just going by the tutorial, which doesn't mention this.

'service pacemaker start' and 'pcs cluster start' are pretty much equivalent.
both will start cman if its not running already

> 
> On 10/20/2014 3:44 PM, Maciej Rostański wrote:
>> Hello,
>> 
>> In my experience such problems were the effect of my mistakes, such as not
>> having all hosts in /etc/hosts file. Check this, please, I know it sounds
>> simple.
>> 
>> Also, commands:
>> pcs cluster setup --name clustername node1 node2 node3
>> pcs cluster enable
>> pcs cluster start
>> 
>> are much more pleasant to run than ccs method you use, and they work on
>> Centos6.5
>> 
>> Regards,
>> Maciej
>> 
>> 
>> 
>> 2014-10-20 20:50 GMT+02:00 John Scalia <[email protected]>:
>> 
>>> Hi all,
>>> 
>>> I'm trying to build my first ever HA cluster and I'm using 3 VMs running
>>> CentOS 6.5. I followed the instructions to the letter at:
>>> 
>>> http://clusterlabs.org/quickstart-redhat.html
>>> 
>>> and everything appears to start normally, but if I run "cman_tool nodes
>>> -a", I only see:
>>> 
>>> Node     Sts    Inc          Joined Name
>>>         1      M     64         2014-10--20 14:00:00  csgha1
>>>                 Addresses: 10.10.1.128
>>>         2      X 0                                                  csgha2
>>>         3      X 0                                                  csgha3
>>> 
>>> In the other systems, the output is the same except for which system is
>>> shown as joined. Each shows just itself as belonging to the cluster. Also,
>>> "pcs status" reflects similarly with non-self systems showing offline. I've
>>> checked "netstat -an" and see each machine listening on ports 5405 and
>>> 5405. And the logs are rather involved, but I'm not seeing errors in it.
>>> 
>>> Any ideas for where to look for what's causing them to not communicate?
>>> --
>>> Jay
>>> _______________________________________________
>>> Linux-HA mailing list
>>> [email protected]
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>>> 
>> 
>> 
> 
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.