Ok so I was getting errors similar to those. They actually just "went away" - sorry I don't have a better solution than that. Anyhow, those configs are the *.pickle files you deleted earlier - from what I understand they are just some kind of caching file (the caching deal was taking from the upgrade notes in the install guide).
Anyhow each device gets one of these files, check the path: $ZENHOME/Perf/devices/<deviceName>/localhost-config.pickle In my case, every single devices has one of these files. I'm not sure how/when they are created/recreated but I just ran zenperfsnmp a few times and all the errors regarding configs just took care of themselves. If you wanted to see the contents of the file and are comfortable with hackery, you can load them up in python using the cPickle (or pickle) module and then check them out. You'll want to do that at the Zenoss user and make sure that your environment is set right such that you can import zenoss libs (or you could use the zmd). In my opinion though you don't need to go that far. The template is good out of box unless you've got a funky MIB on your system. I would go as far as verifying the OIDs using snmpwalk. If that's good, just try running that zenperfsnmp a few times, see if those go away (as they did for me). I'm fairly confident that there's a mechanism to recreate these configs its just a question of when/how/where that happens and if there's a way to force it. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=26797#26797 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
