Hi! Let me add: I'm not completely sure, but a side-effect of this messages seems to be that resources (being cleaned up) that are running (e.g. Xen VMs) are considered "stopped". If the CRM tried to start the VM elsewhere, data corruption or other bad effects are likely...
So I wonder: I thought that cleaning up a resource just resets the failed-count for the nodes where the resource couldn't start before. Does it (should it?) really clean the "running" status? Regards, Ulrich >>> "Ulrich Windl" <[email protected]> schrieb am 05.02.2013 um 11:10 in Nachricht <[email protected]>: > Hi! > > I found out that "crm_resource -C -r ..." causes syslog messages like this: > crmd: [12372]: WARN: decode_transition_key: Bad UUID (crm-resource-22905) in > sscanf result (3) for 0:0:crm-resource-22905 > crmd: [12372]: WARN: decode_transition_key: Bad UUID (crm-resource-22993) in > sscanf result (3) for 0:0:crm-resource-22993 > crmd: [12372]: WARN: decode_transition_key: Bad UUID (crm-resource-23033) in > sscanf result (3) for 0:0:crm-resource-23033 > [...] > > It seems crm_resource created some bad or unexpected UUID. Seen in SLES11 > SP2 with current updates. > > # rpm -qf /usr/lib64/pacemaker/crmd > pacemaker-1.1.7-0.9.1 > > Regards, > Ulrich > > > _______________________________________________ > 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
