I’m fine with this proposed change. We could check with other active users too!
Cheers, Mathi. From: Nagendra Kumar [mailto:nagendr...@users.sf.net] Sent: Tuesday, September 10, 2013 1:18 PM To: [opensaf:tickets] Subject: [opensaf:tickets] #429 amf: amfnd should generate core file if the director / agent failed with csi set callback timeout or other failures May be changing the name is not backward compatible if somebody is using it. We can change it if every body agrees. _____ HYPERLINK "http://sourceforge.net/p/opensaf/tickets/429/"[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: Tue Sep 10, 2013 07:45 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 you indicated interest in https://sourceforge.net/p/opensaf/tickets/429/ To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ ------------------------------------------------------------------------------ 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-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
