- **status**: unassigned --> duplicate
---
** [tickets:#1618] AMF: SI removal gets stuck when component termination
failed**
**Status:** duplicate
**Milestone:** 4.7.2
**Created:** Fri Dec 04, 2015 06:22 AM UTC by Quyen Dao
**Last Updated:** Mon May 30, 2016 06:58 AM UTC
**Owner:** nobody
**Attachments:**
-
[AppConfig-2N-3comp-1si-3csi.xml](https://sourceforge.net/p/opensaf/tickets/1618/attachment/AppConfig-2N-3comp-1si-3csi.xml)
(16.6 kB; text/xml)
-
[amf_demo_delay_terminate_callback.patch](https://sourceforge.net/p/opensaf/tickets/1618/attachment/amf_demo_delay_terminate_callback.patch)
(472 Bytes; application/octet-stream)
-
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/1618/attachment/osafamfnd)
(439.4 kB; application/octet-stream)
-
[syslog.PL-4](https://sourceforge.net/p/opensaf/tickets/1618/attachment/syslog.PL-4)
(13.4 kB; application/octet-stream)
**Description**
SI removal gets stuck and SG becomes unstable when component termination failed
**Steps to reproduce**
1. Change amf_demo CLI-CLI CLEANUP command always return 1 (to trigger
termination failed)
2. Change amf_demo to delay the terminate_callback for 2 seconds (attached is
the patch)
3. Load the attached model
4. Kill 1 amf_demo to trigger the component instantiation failed. This also
leads to component failover
**Result**
- Failed component is cleaned up
- Other components in the SU are terminated.
- SI assigned to failed SU gets stuck at "Removing
'safSi=AmfDemo1,safApp=AmfDemo1' from 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'"
- SG become unstable and failed SU can't be "repaired"
**Syslog**
2015-12-03 17:59:05 PL-4 amf_demo[618]: exiting (caught term signal)
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' component restart probation timer
started (timeout: 40000000000 ns)
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Restarting a component of
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' (comp restart count: 1)
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO
'safComp=C-AmfDemo1,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' faulted due to
'avaDown' : Recovery is 'componentRestart'
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Cleanup of
'safComp=C-AmfDemo1,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' failed
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Reason:'Exec of script success, but
script exits with non-zero status'
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Exit code: 1
2015-12-03 17:59:05 PL-4 osafamfnd[419]: WA
'safComp=C-AmfDemo1,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State
RESTARTING => TERMINATION_FAILED
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Component Failover trigerred for
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1': Failed component:
'safComp=C-AmfDemo1,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED =>
TERMINATION_FAILED
2015-12-03 17:59:05 PL-4 amf_demo[625]: Terminating
2015-12-03 17:59:05 PL-4 amf_demo[632]: Terminating
2015-12-03 17:59:05 PL-4 osafamfnd[419]: NO Removing
'safSi=AmfDemo1,safApp=AmfDemo1' from 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
2015-12-03 17:59:07 PL-4 amf_demo[632]: Terminated
2015-12-03 17:59:07 PL-4 amf_demo[625]: Terminated
2015-12-03 17:59:45 PL-4 osafamfnd[419]: NO
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' SU restart probation timer expired
**Command log**
root@PL-4:/srv/shared/osaf_amf_demo# date
Thu Dec 3 18:02:55 ICT 2015
root@PL-4:/srv/shared/osaf_amf_demo# immadm -o 9 --disable-tryagain
safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_TRY_AGAIN
(6)
error-string: SG state is not stable
root@PL-4:/srv/shared/osaf_amf_demo#
Model, trace, syslog, amf_demo_patch are attached.
---
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.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
