[Pacemaker] Disconnected from CIB?

[Andrew Beekhof]

On 02/07/2013, at 12:12 AM, Lars Marowsky-Bree <lmb at suse.com> wrote:

> On 2013-07-01T14:15:01, Lars Marowsky-Bree <lmb at suse.com> wrote:
> 
>> Reproducible on the non-DC node during full start-up of a cluster, yes.
> 
> And it turns out to be a CIB problem afterall. Or I'm doing something
> else wrong:
> 
> I'm doing, basically straight from crm_mon.c:
> 
>        xmlNode *cib_copy = copy_xml(current_cib);
> [...]
>        if (cli_config_update(&cib_copy, NULL, FALSE) == FALSE) {

Also, change FALSE -> TRUE here so that you see the validation errors.

>                if (cib) {
>                        cib->cmds->signoff(cib);
>                }
> 
> (See the two functions following
> https://github.com/l-mb/sbd/blob/master/src/sbd-pacemaker.c#L446)
> 
> write(2, "Your current configuration could only be upgraded to <null>... the minimum requirement is pacemaker-1.0.\n", 105) = 105
> 
> I have seen crm_mon exit with this error message in the past too, but
> not been able to reproduce it reliably enough to file a bug. So, I
> guess, this is progress. ;-)
> 
> What could cause cli_config_update() to fail in this way?

Beats me. Can you log the xml before the connection gets dropped?

> Is that
> expected?

No.