changeset: 4990:8d750a0d1d0b
branch: opensaf-4.2.x
parent: 4984:164ec366f3fe
user: [email protected]
date: Wed Feb 19 11:45:35 2014 +0530
summary: amfnd: handle avadown in shutting down [#778]
changeset: 4991:d9c522b51d4b
branch: opensaf-4.3.x
parent: 4985:38de9866561b
user: [email protected]
date: Wed Feb 19 11:46:42 2014 +0530
summary: amfnd: handle avadown in shutting down [#778]
changeset: 4992:97bdaca14250
branch: opensaf-4.4.x
parent: 4988:a8f4281d1863
user: [email protected]
date: Wed Feb 19 11:47:26 2014 +0530
summary: amfnd: handle avadown in shutting down [#778]
changeset: 4993:cc94ddebc7ba
tag: tip
parent: 4989:1262cda3ddf1
user: [email protected]
date: Wed Feb 19 11:48:05 2014 +0530
summary: amfnd: handle avadown in shutting down [#778]
[staging:8d750a]
[staging:d9c522]
[staging:97bdac]
[staging:cc94dd]
---
** [tickets:#778] AMF: opensaf shutdown stalled when comp crash during
shutdown**
**Status:** fixed
**Created:** Mon Feb 10, 2014 06:15 PM UTC by Hans Feldt
**Last Updated:** Mon Feb 17, 2014 11:05 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.
------------------------------------------------------------------------------
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-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
