Kelly, The 2.1.x -> 2.3.x upgrade instructions were vetted from a system starting out at 2.1.3. I'm wondering if you could migrate 2.1.2 -> 2.1.3 first, you may have a better outcome.
Something along these lines... Code: Verify you can see the 2.1.3 trove on the repository... # conary rq [EMAIL PROTECTED]:core/2.1.3 --full-versions group-zenoss=/[EMAIL PROTECTED]:devel//core/2.1.3-0.1-1[~!VMwareTools-kernel.debug,~!VMwareTools-kernel.numa,~!VMwareTools-kernel.pae,~!VMwareTools-kernel.smp,~!kernel.pae,sasl,~!unionfs.debug,~!unionfs.numa,~!unionfs.smp is: x86(~!mmx,~!sse2)] Migrate to 2.1.3 # service zenoss stop # ps ax | grep zenoss # rm /home/zenoss/var/*.zec # find /home/zenoss/perf -name *.pickle -delete # su - zenoss -c "/home/zenoss/bin/zeoctl start" # conary migrate [EMAIL PROTECTED]:core/2.1.3 --interactive If that goes well, continue instructions as published. I'll see if I can replicate your problem. I just did a migrate from 2.1.2 to 2.1.3 with the recipe above. Regards, Glenn Configuration Management Zenoss, Inc. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=27820#27820 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
