I had real similar issue and i'll tell you how i got around it. in case it matters i'm running mine on Fedora Core 8. I realize this is a hard option but desperate times call for desperate measures.
I created a completely stock install of fedora core 8 on a different box. then installed the stack install of zenoss core 2.2. so I've got at this point a working version of 2.2 with no data. make sure to move the zeo.conf, and cope.conf config files. i forgot this step and it messed up big time. So here are the rewritten steps i used and it worked for me twice (used the wrong restore file the first time) before starting make sure that you issue the "zenoss stop" command and stop mysql with the "/usr/local/zenoss/mysql/scripts/ctl.sh stop" command run as root. 1) cd /usr/local/zenoss/zenoss/etc cp zeo.conf zope.conf /temp 2) copy old zenpack folders from old zenoss box into new folders on the new zenoss box. 3) start mysql, by becoming root "su root" and then using the command "/usr/local/zenoss/mysql/scripts/ctl.sh start " then type exit to become zenoss user again 4) run zenrestore to restore your backup. I've never been able to get this to work with the commands they supply so this is the one I use. "zenrestore -v --dbpass=XXX --file=XXX" and skip the variables and the additional parameters. otherwise it always errors out for me. 5) copy the configuration files back cp /tmp/zope.conf /usr/local/zenoss/zenoss/etc cp /tmp/zeo.conf /usr/local/zenoss/zenoss/etc 6) start zeo with the "zeoctl start" command 7) run zenmigrate with no extra parameters 8) re-register the portlets. this was an important one that i messed up a couple of times because the instructions included are wrong for some reason as zenoss run zendmd when you get the >>> issue the following three commands verbatim from Products.ZenWidgets.ZenossPortlets.ZenossPortlets import register_default_portlets register_default_portlets(zport.ZenPortletManager) commit() and they are case sensitive. after all that i was able to start zenoss, and then stop it and stop mysql and then reboot the computer. upon startup i changed the loading screen so i could see what it was doing and you can actually see zenoss starting up in the OS initialization. if you get no errors, log in and make sure everything is there and you're done. Hope that helps a little, i've been trying to figure out the 2.1.3 to 2.2.0 upgrade since it came out and i've failed at least ten times. Oh yeah did I mention you should use G4L(ghost for linux) to backup your production zenoss box before doing this... -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21665#21665 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
