[Pacemaker] Current DC: NONE

Andrew Beekhof beekhof at gmail.com
Mon Feb 16 10:05:40 UTC 2009


On Mon, Feb 9, 2009 at 17:19, Raoul Bhatia [IPAX] <r.bhatia at ipax.at> wrote:
> Raoul Bhatia [IPAX] wrote:
>>> ============
>>> Last updated: Fri Dec  5 19:53:33 2008
>>> Current DC: NONE
>>> 2 Nodes configured.
>>> 9 Resources configured.
>>> ============
>>>
>>> Node: wc02 (f36760d8-d84a-46b2-b452-4c8cac8b3396): online
>>> Node: wc01 (31de4ab3-2d05-476e-8f9a-627ad6cd94ca): online
>>
>> same hb_report at [1].
>>
>
>> [1] http://ip52.ipax.at/~raoul/cluster/stonith_error_long_no_dc.tar.bz2
>
> i encountered the "DC: NONE" problem again: cibamin -Ql showed
> dc-uuid="0". should this periodically be (re-)checked?

not really, its not used for anything except reporting in crm_mon.
the DC sets it when it gets elected and no other process (or
administrator) has any business modifying it.

how did it get into this state?




More information about the Pacemaker mailing list