[Pacemaker] pacemaker 1.1.5/ corosync 1.2.1 on cent os
    Igor Khomyakov 
    ikh at iri.columbia.edu
       
    Tue Apr  3 00:34:29 EDT 2012
    
    
  
Resolved this issue by upgrading pacemaker to 1.1.6 and by adding the following to  corosync.conf:
	aisexec {
       		user: root
        	group: root
	}
	service {
        	name: pacemaker
        	ver: 0
        	use_mgmtd: yes
	}
I am curious what was causing the original issue...
In service.d/pcmkservice we still have : 
	{
        	# Load the Pacemaker Cluster Resource Manager
        	name: pacemaker
        	ver: 1
	}
Thanks,
Igor
On Apr 2, 2012, at 3:57 PM, Igor Khomyakov wrote:
> Hello, 
> 
> I am probably missing something very simple... I am trying to set up a 2-node cluster using pacemaker 1.1.5/ corosync 1.2.1 on cent os . 
> 
> corosync and pamaker start without complaints, however "crm status" reports :
> 
> 
> # crm status 
> ============
> Last updated: Mon Apr  2 15:56:08 2012
> Last change: Mon Apr  2 15:22:03 2012
> Current DC: NONE
> 0 Nodes configured, unknown expected votes
> 0 Resources configured.
> ============
> 
> 
> Pacemaker doesn't want to pick up the nodes for soem reason. Could you help? 
> 
> Thank you,
> 
> Igor 
> 
    
    
More information about the Pacemaker
mailing list