On 11/10/2016 09:47 AM, Toni Tschampke wrote:
>> Did your upgrade documentation describe how to update the corosync
>> configuration, and did that go well? crmd may be unable to function due
>> to lack of quorum information.
>
> Thanks for this tip, corosync quorum configuration was the cause.
>
>
Did your upgrade documentation describe how to update the corosync
configuration, and did that go well? crmd may be unable to function due
to lack of quorum information.
Thanks for this tip, corosync quorum configuration was the cause.
As we changed validate-with as well as the feature set
On 11/07/2016 09:08 AM, Toni Tschampke wrote:
> We managed to change the validate-with option via workaround (cibadmin
> export & replace) as setting the value with cibadmin --modify doesn't
> write the changes to disk.
>
> After experimenting with various schemes (xml is correctly interpreted
>
> I'm guessing this change should be instantly written into the xml file?
> If this is the case something is wrong, greping for validate gives the
> old string back.
We found some strange behavior when setting "validate-with" via
cibadmin, corosync.log shows the successful transaction, issuing
> I'm going to guess you were using the experimental 1.1 schema as the
> "validate-with" at the top of /var/lib/pacemaker/cib/cib.xml. Try
> changing the validate-with to pacemaker-next or pacemaker-1.2 and see if
> you get better results. Don't edit the file directly though; use the
> cibadmin
> You'll want to switch your validate-with schema to a newer schema,
and most
> likely there will be one or two things that don't validate
> anymore. There is the "crm configure upgrade" command, but if crmsh is
> having problems you can call cibadmin directly:
>
> cibadmin --upgrade
Hi,
we just upgraded our nodes from wheezy 7.11 (pacemaker 1.1.7) to jessie
(pacemaker 1.1.15, corosync 2.3.6).
During the upgrade pacemaker was removed (rc) and reinstalled after from
jessie-backports, same for crmsh.
Now we are encountering multiple problems:
First I checked the
