In case of cleanup, Amf exports NCS_ENV_COMPONENT_ERROR_SRC with the value of
AVND_ERR_SRC. Component can use the value of
AVND_ERR_SRC_CBK_CSI_SET_TIMEOUT(10) to create core dump of their component as
below :
if [ $NCS_ENV_COMPONENT_ERROR_SRC -eq 10 ]; then
kill -5 3341
logger -st $name "Generated the core dump.."
fi
We will document the above statement in AMF PR doc.
Creating core dump in application during any failure should be left on
Application to handle.
---
** [tickets:#429] amf: amfnd should generate core file if the director / agent
failed with csi set callback timeout or other failures**
**Status:** review
**Created:** Fri May 31, 2013 06:39 AM UTC by Praveen
**Last Updated:** Mon Sep 09, 2013 11:58 AM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2139.
If the traces are not enabled for any director / node director and if amfnd is
rebooting the node because of the csiSetCallbackTimeout or any other timeouts
,amf should generate core file while rebooting the node.
Root cause will not be entirely known by the core, but it helps in debugging
the issue further.
It would be good even if the core generating process is extended for amf agents
in the case of failures.
Currently I think core will be generated for amfnd / amfd only.
In the case of following scenario, there would be no clue why plmd has got
csiSetCallbackTimeout with out enabling traces.
Sep 28 19:00:04 SLES11-SLOT-2 osafimmnd[4251]: Implementer connected: 80
(safPlmService) <893, 2020f>
Sep 28 19:00:04 SLES11-SLOT-2 osafimmnd[4251]: Implementer connected: 81
(safSmfService) <405, 2020f>
Sep 28 19:00:05 SLES11-SLOT-2 osafamfnd[4343]:
'safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?' Presence State INSTANTIATED =>
TERMINATING
Sep 28 19:00:05 SLES11-SLOT-2 osafamfnd[4343]:
'safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?' Presence State TERMINATING =>
UNINSTANTIATED
Sep 28 19:00:13 SLES11-SLOT-2 osafamfnd[4343]:
'safComp=PLMS,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to
'csiSetcallbackTimeout(10)' : Recovery is 'nodeFailfast(6)'
Sep 28 19:00:13 SLES11-SLOT-2 osafamfnd[4343]:
safComp=PLMS,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due
to:csiSetcallbackTimeout(10) Recovery is:nodeFailfast(6)
Sep 28 19:00:13 SLES11-SLOT-2 osafamfnd[4343]: Rebooting OpenSAF NodeId? =
131599 EE Name = , Reason: Component faulted: recovery is node failfast
Changed 20 months ago by hafe ΒΆ
Core file for what process, the one causing the csiSetCallbackTimeout I assume?
---
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.
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
