Hello Neighbor! I believe this occurs when you've issued a 'crm node standby' followed by a 'crm node online' on a particular node. In my experience, this sets the 'standby: off' attribute.
Eric Schoeller Information Technology Services University of Colorado, Boulder On 09/24/10 15:08, Greg Woods wrote: > On Fri, 2010-09-24 at 11:34 -0600, Greg Woods wrote: > > >> # crm node show >> vmserve2.scd.ucar.edu(16fde08d-b4b6-4550-adfb-b3aab83f706f): normal >> standby: off >> vmserve.scd.ucar.edu(6f5ced83-a790-4519-8449-3d4cf43275b0): normal >> standby: off >> >> On the second cluster: >> >> # crm node show >> vmx1.ucar.edu(62cf0a44-5d0f-475e-a0ac-689537f98f58): normal >> vmx2.ucar.edu(8ad9076e-c571-499b-91e9-4d513fd5be61): normal >> > This difference can be corrected by running: > > # crm node attribute vmx1.ucar.edu set standby off > # crm node attribute vmx2.ucar.edu set standby off > > But I don't recall having to do this before, so this does not explain > why the difference occurred in the first place. I also don't know if > this change will last across a reboot, but since it's part of the CIB, > hopefully it will. > > --Greg > > > _______________________________________________ > 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
