with the patch and an exit in the first CSI remove I get this:

Feb 14 09:57:04 PL-3 osafamfnd[409]: NO Shutdown initiated
Feb 14 09:57:04 PL-3 osafamfnd[409]: NO Removing assignments from AMF components
Feb 14 09:57:04 PL-3 osafamfnd[409]: IN Removing 
'safCsi=C,safSi=ABC,safApp=osaftest' from 
'safComp=C,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:04 PL-3 C[596]: csiRemoveCallback: 
'safCsi=C,safSi=ABC,safApp=osaftest', invocation 4261412878
Feb 14 09:57:04 PL-3 C[596]: csiRemoveCallback: '0'
Feb 14 09:57:05 PL-3 C[596]: terminate: 99
Feb 14 09:57:05 PL-3 C[596]: Exiting
Feb 14 09:57:05 PL-3 osafamfnd[409]: NO 
'safComp=C,safSu=1,safSg=1,safApp=osaftest' faulted due to 'avaDown'
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN 
'safComp=C,safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATED => 
TERMINATING
Feb 14 09:57:05 PL-3 amfclccli[622]: CLEANUP request 
'safComp=C,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 amfclccli[622]: CLEANUP response 'kill(pid=596)'
Feb 14 09:57:05 PL-3 amfclccli[622]: CLEANUP kill result: [Errno 3] No such 
process 
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN 
'safComp=C,safSu=1,safSg=1,safApp=osaftest' Presence State TERMINATING => 
UNINSTANTIATED
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN Removed 
'safCsi=C,safSi=ABC,safApp=osaftest' from 
'safComp=C,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN Removing 
'safCsi=B,safSi=ABC,safApp=osaftest' from 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 B[589]: csiRemoveCallback: 
'safCsi=B,safSi=ABC,safApp=osaftest', invocation 4269801480
Feb 14 09:57:05 PL-3 B[589]: csiRemoveCallback: '0'
Feb 14 09:57:05 PL-3 B[589]: saAmfResponse(inv=4269801480, error=1)
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN Removed 
'safCsi=B,safSi=ABC,safApp=osaftest' from 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN Removing 
'safCsi=A,safSi=ABC,safApp=osaftest' from 
'safComp=A,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 A[582]: csiRemoveCallback: 
'safCsi=A,safSi=ABC,safApp=osaftest', invocation 4269801481
Feb 14 09:57:05 PL-3 A[582]: csiRemoveCallback: '0'
Feb 14 09:57:05 PL-3 A[582]: saAmfResponse(inv=4269801481, error=1)
Feb 14 09:57:05 PL-3 osafamfnd[409]: IN Removed 
'safCsi=A,safSi=ABC,safApp=osaftest' from 
'safComp=A,safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 osafamfnd[409]: NO Removed 'safSi=ABC,safApp=osaftest' 
from 'safSu=1,safSg=1,safApp=osaftest'
Feb 14 09:57:05 PL-3 osafamfnd[409]: NO Removed assignments from AMF components
Feb 14 09:57:05 PL-3 osafamfnd[409]: NO Terminating all AMF components

no delay in shutdown!


---

** [tickets:#778] AMF: opensaf shutdown stalled when comp crash during 
shutdown**

**Status:** review
**Created:** Mon Feb 10, 2014 06:15 PM UTC by Hans Feldt
**Last Updated:** Thu Feb 13, 2014 08:37 AM UTC
**Owner:** Hans Feldt

If a component crash/exit during opensaf shutdown, amfnd relies on the CSI 
remove timeout to sort out the situation which can be seen in the logs below.

The reason is that the "avadown" event is discarded in the "shutting down" 
state in function avnd_evt_mds_ava_dn_evh(). If that filter is removed the 
event is used and the shutdown proceeds without waiting for the CSI remove 
timeout.

There is anyway special handling in the error handler (avnd_err_process) for 
the shutdown state. The important thing is that when CLEANUP is performed the 
component presence state changes to TERMINATING which then later effects the 
CSI remove handling.

Feb 10 07:46:40 PL-3 opensafd: Stopping OpenSAF Services
Feb 10 07:46:40 PL-3 osafamfnd[409]: NO Shutdown initiated
Feb 10 07:46:40 PL-3 osafamfnd[409]: NO Removing assignments from AMF components
Feb 10 07:46:40 PL-3 osafamfnd[409]: IN Removing 
'safCsi=C,safSi=ABC,safApp=osaftest' from 
'safComp=C,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:40 PL-3 C[602]: csiRemoveCallback: 
'safCsi=C,safSi=ABC,safApp=osaftest', invocation 4269801485
Feb 10 07:46:40 PL-3 C[602]: csiRemoveCallback: '0'
Feb 10 07:46:40 PL-3 B[595]: terminate: 99
Feb 10 07:46:40 PL-3 B[595]: Exiting
Feb 10 07:46:40 PL-3 C[602]: saAmfResponse(inv=4269801485, error=1)
Feb 10 07:46:40 PL-3 osafamfnd[409]: IN Removed 
'safCsi=C,safSi=ABC,safApp=osaftest' from 
'safComp=C,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:40 PL-3 osafamfnd[409]: IN Removing 
'safCsi=B,safSi=ABC,safApp=osaftest' from 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:50 PL-3 osafamfnd[409]: NO 
'safComp=B,safSu=1,safSg=1,safApp=osaftest' faulted due to 
'csiRemovecallbackTimeout'
Feb 10 07:46:50 PL-3 osafamfnd[409]: IN 
'safComp=B,safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATED => 
TERMINATING
Feb 10 07:46:51 PL-3 amfclccli[637]: CLEANUP request 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 amfclccli[637]: CLEANUP response 'kill(pid=595)'
Feb 10 07:46:51 PL-3 amfclccli[637]: CLEANUP kill result: [Errno 3] No such 
process 
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN 
'safComp=B,safSu=1,safSg=1,safApp=osaftest' Presence State TERMINATING => 
UNINSTANTIATED
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN Removed 
'safCsi=B,safSi=ABC,safApp=osaftest' from 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN Removing 
'safCsi=A,safSi=ABC,safApp=osaftest' from 
'safComp=A,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN Removed 
'safCsi=B,safSi=ABC,safApp=osaftest' from 
'safComp=B,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN Removing 
'safCsi=A,safSi=ABC,safApp=osaftest' from 
'safComp=A,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: IN Removed 
'safCsi=A,safSi=ABC,safApp=osaftest' from 
'safComp=A,safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: NO Removed 'safSi=ABC,safApp=osaftest' 
from 'safSu=1,safSg=1,safApp=osaftest'
Feb 10 07:46:51 PL-3 osafamfnd[409]: NO Removed assignments from AMF components



---

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.
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to