I've upgraded to version 2.2.3 in two datacenters. This were 2.1.2 running on centos5 virtual machines. The upgrade was done via rpm. One upgrade went smoothly, the other is getting hundreds of blue alerts related to oid issues. Perf snmp keep getting bad oids. When I disable templates that are bound to devises that generate these errors, awknowlege the events and move to history, when zenoss is restarted, the blue errors come back, even though the templates are no longer bound to the devises. This make little logical sense, that the errors would return. I've copied my virtual machine so I have the original running 2.1.2 and have a cloned, upgraded and re-ip'd vm running as 2.2.3. I'm trying to clean up the 2.2.3 version while keeping the older working version running. The while reason for the upgrade is to fix the problem with schedueling, where time schedules built into alerting rules on a group level (lists of users belonging to a group) do not work. The upgrade directions are very terse, just stating to run an rpm -Uvh and all is well, but this not the case. Is there a better, detailed set up upgrade instructions for an rpm upgrade? Or, how do I at least prevent old blue errors that show up even when the oid's aren't being probed anymore, because the template's aren't even active.
-------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=24162#24162 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
