- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -20,7 +20,24 @@
-----------------------------------------------------------
-The problem has so far not been possible to reproduce and the previous
-analysis turned out to be incorrect.
+The problem has been reproduced.
+It is simply the case of an idempotent *applier* object-implementer-set
+attempted during sync.
-We need to obtain the exact code version used when the problem was observed.
+To reproducde:
+1) Create an applier on a test object. For example using
+immapplier .a @MyApplier <test-object>
+
+2) Stop the applier.
+
+3) Trigger a sync by rebooting one node or killing one immnd.
+
+4) While the sync is on-going (you may need to poulate with objects so
+that the sync is not too fast) start the same applier on the same object
+again.
+
+The IMMND on the processor where the applier is trying to re-attach will crash.
+
+Raising priority to critical since the originaly reported case happened
+during failover and resulted in IMMND restart at new active SC resulting
+in cluster restart.
~~~~
- **status**: needinfo --> accepted
- **Priority**: major --> critical
---
** [tickets:#1202] IMM: Local immnd crashes on assert in executing
saImmOiObjectImplementerSet**
**Status:** accepted
**Milestone:** 4.4.2
**Created:** Wed Nov 05, 2014 09:47 AM UTC by Anders Bjornerstedt
**Last Updated:** Wed Nov 05, 2014 04:13 PM UTC
**Owner:** Anders Bjornerstedt
>From syslog:
2014-10-28 15:16:27 SystemEvent osafimmnd SC-2-1 err osafimmnd[8813]:
immnd_evt.c:3178: immnd_fevs_local_checks: Assertion 'error != SA_AIS_OK'
failed.
This assertion is in immnd_evt.c in function immnd_fevs_local_checks at:
-----------------------------------
case IMMND_EVT_A2ND_OI_OBJ_IMPL_SET:
if(fevsReq->sender_count != 0x1) {
LOG_WA("ERR_LIBRARY: IMMND_EVT_A2ND_OI_OBJ_IMPL_SET
fevsReq->sender_count != 0x1");
error = SA_AIS_ERR_LIBRARY;
} else if(immModel_immNotWritable(cb)) {// sync is on-going
SaUint32T ccbId=0;
error = immModel_objectImplementerSet(cb,
&(frwrd_evt.info.immnd.info.implSet), conn,
nodeId, &ccbId);
osafassert(error != SA_AIS_OK); <======
/* OK is impossible since we are not writable */
-----------------------------------------------------------
The problem has been reproduced.
It is simply the case of an idempotent *applier* object-implementer-set
attempted during sync.
To reproducde:
1) Create an applier on a test object. For example using
immapplier .a @MyApplier <test-object>
2) Stop the applier.
3) Trigger a sync by rebooting one node or killing one immnd.
4) While the sync is on-going (you may need to poulate with objects so
that the sync is not too fast) start the same applier on the same object
again.
The IMMND on the processor where the applier is trying to re-attach will crash.
Raising priority to critical since the originaly reported case happened
during failover and resulted in IMMND restart at new active SC resulting
in cluster restart.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
