Hi,

On Wed, Jun 09, 2010 at 10:09:33PM -0400, Miles Fidelman wrote:
> Hi Folks,
> 
> I'm not sure if this belongs on the linux-ha or pacemaker list, so....
> 
> I just upgraded a Debian Lenny cluster from hearbeat2 to 
> heartbeat3+pacemaker - per the directions at
> http://www.linux-ha.org/doc/s-upgrade-crm-install-software.html (thank 
> you to Florian and Michael for you advice)
> 
> ---- note to anyone who follows -----
> At the upgrade step, I borrowed from the directions at 
> http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo and added
> 
> debhttp://people.debian.org/~madkiss/ha  
> <http://people.debian.org/%7Emadkiss/ha>  lenny main
> 
> to /etc/apt/sources.list
> and then did
> apt-get dist-upgrade heartbeat pacemaker
> and everything installed and upgraded automagically.
> ---------------------------------------------
> 
> All seems to have gone well, and pretty painlessly - everything is up 
> and running, with one remaining issue:
> 
> As I understand it, after running "cibadmin --upgrade --force" the CIB 
> should be accessible through crm-shell (crm > configure).
> 
> However, when I do this, I get the error message:
> INFO: object crm_config.id2244404 cannot be represented in the CLI notation

What a strange id. Do you have such id? Can you show the config?
In particular this element should've been shown as xml.

Thanks,

Dejan

> So... clearly something didn't convert from the old format to the new 
> format.  Any suggestions on how to get past this?
> 
> Thank you very much,
> 
> Miles Fidelman
> 
> -- 
> In theory, there is no difference between theory and practice.
> In<fnord>  practice, there is.   .... Yogi Berra
> 
> 
> _______________________________________________
> 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

Reply via email to