I was not; but now I am setting the final score on successful start. I am calculating the score by using the monitor actions. For each portion of monitoring which returns successful, I am adding 10 to the score. The final score set should be 40. However, it is still not working. Any other suggestions?
On Mon, Aug 27, 2012 at 7:49 AM, Lars Marowsky-Bree <l...@suse.com> wrote: > On 2012-08-26T11:44:52, Eliot Gable <egable+pacema...@gmail.com> wrote: > > > Looking back through my E-mails, it looks like this was originally > deployed > > on 1.1.2. My guess is that someone did a sweeping software update on the > > system but never restarted/reloaded pacemaker + corosync until that > reboot > > occurred last week. Did something change between 1.1.2 and 1.1.6 which > > might have broken how the system behaves in the scenario I outlined? > > Does your script call crm_master somewhere to set a non-zero promotion > score? > > > Regards, > Lars > > -- > Architect Storage/HA > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix > Imendörffer, HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org >
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
