With helps from Hung, I have seen 2 concurrent IMM reinit threads by adding
delay in immpbe, log/trace is attached.
Below is snippet
2016-11-18 23:13:24 SC-1 osafamfd[488]: NO Re-initializing with IMM
2016-11-18 23:13:24 SC-1 osafimmnd[432]: WA IMMND - Client Node Get Failed for
cli_hdl 115964248335
2016-11-18 23:13:24 SC-1 osafimmnd[432]: NO Implementer connected: 12
(safAmfService) <389, 2010f>
2016-11-18 23:13:24 SC-1 osafamfd[488]: NO Re-initializing with IMM
2016-11-18 23:13:24 SC-1 osafamfd[488]: NO Finished re-initializing with IMM
2016-11-18 23:13:24 SC-1 osafimmnd[432]: NO Implementer locally disconnected.
Marking it as doomed 12 <389, 2010f> (safAmfService)
2016-11-18 23:13:24 SC-1 osafamfd[488]: ER exec: update FAILED 2
2016-11-18 23:13:24 SC-1 osafamfd[488]: WA saImmOiRtObjectUpdate of
'safSg=AmfDemoTwon,safApp=AmfDemoTwon' osafAmfSGSuOperationList failed with 2
2016-11-18 23:13:24 SC-1 osafamfd[488]: WA saImmOiRtObjectUpdate of
'safSg=AmfDemoTwon,safApp=AmfDemoTwon' osafAmfSGFsmState failed with 2
2016-11-18 23:13:24 SC-1 osafimmnd[432]: NO Implementer disconnected 12 <389,
2010f> (safAmfService)
2016-11-18 23:13:24 SC-1 osafimmnd[432]: NO Implementer connected: 13
(safAmfService) <390, 2010f>
2016-11-18 23:13:24 SC-1 osafamfd[488]: ER ERR_BAD_OPERATION: The
SaImmOiHandleT is not associated with any implementer name
2016-11-18 23:13:24 SC-1 osafamfd[488]: WA saImmOiRtObjectUpdate of
'safSg=AmfDemoTwon,safApp=AmfDemoTwon' osafAmfSGSuOperationList failed with 20
2016-11-18 23:13:24 SC-1 osafamfd[488]: ER ERR_BAD_OPERATION: The
SaImmOiHandleT is not associated with any implementer name
2016-11-18 23:13:24 SC-1 osafamfd[488]: WA saImmOiRtObjectUpdate of
'safSg=AmfDemoTwon,safApp=AmfDemoTwon' osafAmfSGFsmState failed with 20
2016-11-18 23:13:24 SC-1 osafamfd[488]: ER exec: update FAILED 2
2016-11-18 23:13:24 SC-1 osafimmnd[432]: WA Timeout on syncronous admin
operation 1
2016-11-18 23:13:24 SC-1 osafamfd[488]: NO Finished re-initializing with IMM
In another run, I have seen "saImmOiImplementerSet failed 14", but logs were
rotated
Below is log left from console
2016-11-18 22:37:27 SC-1 osafamfd[487]: NO Re-initializing with IMM
2016-11-18 22:37:27 SC-1 osafimmnd[431]: WA IMMND - Client Node Get Failed for
cli_hdl 115964248335
2016-11-18 22:37:27 SC-1 osafimmnd[431]: NO Implementer connected: 12
(safAmfService) <471, 2010f>
2016-11-18 22:37:27 SC-1 osafamfd[487]: NO Re-initializing with IMM
2016-11-18 22:37:27 SC-1 osafamfd[487]: NO Finished re-initializing with IMM
2016-11-18 22:37:27 SC-1 osafamfd[487]: ER exec: update FAILED 2
2016-11-18 22:37:27 SC-1 osafimmnd[431]: NO Implementer locally disconnected.
Marking it as doomed 12 <471, 2010f> (safAmfService)
2016-11-18 22:37:27 SC-1 osafamfd[487]: NO Re-initializing with IMM
2016-11-18 22:37:27 SC-1 osafimmnd[431]: NO Implementer disconnected 12 <471,
2010f> (safAmfService)
2016-11-18 22:37:27 SC-1 osafimmnd[431]: NO Implementer connected: 13
(safAmfService) <472, 2010f>
2016-11-18 22:37:27 SC-1 osafimmnd[431]: WA Timeout on syncronous admin
operation 1
2016-11-18 22:37:27 SC-1 osafamfd[487]: NO Finished re-initializing with IMM
2016-11-18 22:37:27 SC-1 osafamfd[487]: ER saImmOiImplementerSet failed 14
2016-11-18 22:37:27 SC-1 osafamfd[487]: ER exiting since avd_imm_impl_set failed
2016-11-18 22:37:27 SC-1 osafamfnd[500]: WA AMF director unexpectedly crashed
2016-11-18 22:37:27 SC-1 osafamfnd[500]: Rebooting OpenSAF NodeId = 131343 EE
Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received,
OwnNodeId = 131343, SupervisionTime = 60
Attachments:
-
[2188.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/b176386d/8157/attachment/2188.tgz)
(652.0 kB; application/x-compressed)
---
** [tickets:#2188] amfd: avd_imm_impl_set fails causing node reboot**
**Status:** unassigned
**Milestone:** 5.1.1
**Created:** Tue Nov 15, 2016 06:39 AM UTC by Gary Lee
**Last Updated:** Fri Nov 18, 2016 05:31 AM UTC
**Owner:** nobody
**Attachments:**
-
[amfd-core.txt](https://sourceforge.net/p/opensaf/tickets/2188/attachment/amfd-core.txt)
(9.9 kB; text/plain)
avd_imm_impl_set fails causing node reboot
It seems there may have been simultaneous IMM reinit threads running.
Nov 14 02:24:26 SC-2-2 osafamfd[4174]: NO Re-initializing with IMM
Nov 14 02:24:26 SC-2-2 osafamfd[4174]: NO Re-initializing with IMM
Nov 14 02:24:26 SC-2-2 osafimmnd[16412]: NO Implementer connected: 44
(safAmfService) <526, 2020f>
Nov 14 02:24:26 SC-2-2 osafamfd[4174]: NO Finished re-initializing with IMM
Nov 14 02:24:26 SC-2-2 osafamfd[4174]: ER saImmOiImplementerSet failed 14
Nov 14 02:24:26 SC-2-2 osafamfd[4174]: ER exiting since avd_imm_impl_set failed
Nov 14 02:24:26 SC-2-2 osafimmnd[16412]: NO Implementer locally disconnected.
Marking it as doomed 44 <526, 2020f> (safAmfService)
Nov 14 02:24:26 SC-2-2 osafamfnd[4192]: WA AMF director unexpectedly crashed
Nov 14 02:24:26 SC-2-2 osafamfnd[4192]: Rebooting OpenSAF NodeId = 131599 EE
Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received,
OwnNodeId = 131599, SupervisionTime = 60
Nov 14 02:24:26 SC-2-2 osafimmnd[16412]: NO Implementer disconnected 44 <526,
2020f> (safAmfService)
---
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
