[Pacemaker] getting started

[Frank DiMeo]

Sorry, the permissions were the problem I think.  It looks like the hacluster user actually is the writer of these files.

 

Thanks for you help hj

 

-Frank

 

________________________________

From: Frank DiMeo [mailto:Frank.DiMeo at bigbandnet.com] 
Sent: Wednesday, November 18, 2009 5:17 PM
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] getting started

 

Well, set the permissions to 755 but still nothing is stored in /var/lib/heartbeat/crm in a running node

 

-Frank

 

________________________________

From: Frank DiMeo [mailto:Frank.DiMeo at bigbandnet.com] 
Sent: Wednesday, November 18, 2009 5:09 PM
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] getting started

 

Sorry, I just noticed that the directories under /var/lib/heartbeat/ have permissions of 750...not good.  This probably explains the persistence problem.

 

-Frank

 

________________________________

From: Frank DiMeo [mailto:Frank.DiMeo at bigbandnet.com] 
Sent: Wednesday, November 18, 2009 5:04 PM
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] getting started

 

Maybe the permissions and ownership of /var/lib/heartbeat/XXX directories are wrong on my system?  On my nodes, the owner of all directories under /var/lib/heartbeat is root/root and the permissions are 755

 

-Frank

 

________________________________

From: hj lee [mailto:kerdosa at gmail.com] 
Sent: Wednesday, November 18, 2009 4:57 PM
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] getting started

 

 

On Wed, Nov 18, 2009 at 2:27 PM, Frank DiMeo <Frank.DiMeo at bigbandnet.com> wrote:

Thanks for you response,  some comments:

 

1)       So, if we cannot load a persistent configuration after a restart of the all nodes in the cluster, how does one automatically configure an (rebooted) unattended cluster with a known set of resources?  Is it expected that a person will reconfigure a cluster if it were to all nodes in the cluster were to reboot?

You don't have to reload it. The cluster configuration is saved in /var/lib/heartbeat/crm/crm-xx.raw and it survives across reboot. 

	2)       If I'm trying to reduce the DC election time during a complete cluster reboot, so how can I load the dc-deadtime before a DC is elected?

When you configure a cluster initially, just set the dc-deadtime, it will be persistent. 

	 

	3)       Thanks, that's was the problem

	 

	4)       I'm sure your method will work, but the syntax that I used is right out of the documentation for pacemaker (example 6.16 of Pacemaker 1.0, Configuration explained"), so I don't see what's wrong with it.  Regardless, I'll use your method.

Oh, well. That's why we are here to catch a bug!

Thanks

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091118/48bd6299/attachment-0002.htm>