Hi Neel, Thanks for the analysis. It seems that multiple components in this case tripped on the race condition, I assume from your description that the fix was only applied to CLM? Also in this case the node didn’t recover despite multiple restarts - does that fit with the scenario in ticket 528?
Is this reproducible? - not sure yet, this is the first time I’ve seen this particular crash, but we recently started testing on bigger systems and that could be a factor. We really need a fix for this - should I open a ticket? thanks — tony On Feb 21, 2014, at 5:36 AM, Neelakanta Reddy <[email protected]> wrote: > Hi, > > The same problem is observed in CLM, and is fixed in > sourceforge.net/p/opensaf/tickets/528 . > It is fixed in 4622, changeset for opensaf-4.3.x . > > For other services, the problem is not yet fixed. > > Can you, please confirm it is re-producible always. > > /Neel. > > > On Friday 21 February 2014 05:30 AM, Tony Hart wrote: >> 4.3.0 >> >> BTW is there a way to tell at runtime what version is installed? >> >> >> On Feb 20, 2014, at 4:03 AM, Neelakanta Reddy <[email protected]> >> wrote: >> >>> Hi, >>> >>> which version of OpenSAF is used. It looks to be an older release. >>> >>> /Neel. >>> >>> On Wednesday 19 February 2014 08:42 PM, Tony Hart wrote: >>>> Hi Neel, >>>> Thanks for the reply, I’ve attached a fuller log (just the osaf message) >>>> from SCM2, unfortunately the logs from SCM1 are not available. >>>> >>>> — >>>> tony >>>> > ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
