Hi All, I am using opennms 1.8.7 the test case is as follows.
1. Node down event occured and alarmd created a alarm 2. Node up event occured and alarmd created a alarm clearing the nodedown alarm 3. Before vaccumd cleared the nodedown alarm using the deletePastClearedAlarms automation(which is 5 minutes) if there is another nodedown event occurs on the same node, alarmd verifies and updates the nodedown alarm which is present. Before alarmd updates the alarms table vaccuumd cleared the record of that alarm, which is causing the inconsistency. Since vaccummd cleared the alarm record the alarmd was not able to successfully update the alarm record leading to no alarm for nodedown of that node. How could this problem be resolved ?? -- View this message in context: http://opennms.530661.n2.nabble.com/Race-condition-between-alarmd-and-vaccumd-tp7584646.html Sent from the OpenNMS - devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
