We've recreated this and are looking at work-arounds and fixes for
2.2.X.
Thanks,
Matt Ray
Zenoss Community Manager
community.zenoss.com
[EMAIL PROTECTED]
On Jun 19, 2008, at 12:11 AM, thedude42 wrote:
I've tried this on Centos 4.6 after foregoing trying to get mysql5
installed. Then I installed ubuntu 8.04 and no dice. I have the
exact same issue, and have seen other forum references to other
folks with the same issue in 2.2. I'm about to try for a 2.1 install.
It seems like maybe a trigger in the database isn't firing when it's
supposed to, or something in concurrency is not configured
properly. It is easy to get this problem to happen using the
alerting rules, but I have seen it come up when you change a
zProperty for a device while an alert is up for that particular
zProperty on that device. You would think this situation would fail
safe, and not bring up a database inconsistency error.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=21600#21600
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
