- **status**: review --> fixed
- **Milestone**: 4.6.FC --> 4.4.2
- **Comment**:

changeset:   6132:9e2d3ef76abf
branch:      opensaf-4.4.x
parent:      6129:492918cdca13
user:        [email protected]
date:        Wed Nov 12 12:42:07 2014 +0530
summary:     ntfimcn : change LOG_ERR to LOG_NO during shutdown [#1196]

changeset:   6133:3e88f6c28f27
branch:      opensaf-4.5.x
parent:      6130:3707ef0d6d49
user:        [email protected]
date:        Wed Nov 12 12:42:29 2014 +0530
summary:     ntfimcn : change LOG_ERR to LOG_NO during shutdown [#1196]

changeset:   6134:4393feb1b55a
tag:         tip
parent:      6131:8a9ece4f5cf4
user:        [email protected]
date:        Wed Nov 12 12:42:43 2014 +0530
summary:     ntfimcn : change LOG_ERR to LOG_NO during shutdown [#1196]


[staging:9e2d3e]
[staging:3e88f6]
[staging:4393fe]




---

** [tickets:#1196] ntf: change error log to notification when saImmOiDispatch() 
returns with SA_AIS_ERR_BAD_HANDLE**

**Status:** fixed
**Milestone:** 4.4.2
**Created:** Wed Oct 29, 2014 07:56 AM UTC by Robert Apanowicz
**Last Updated:** Fri Oct 31, 2014 06:05 AM UTC
**Owner:** Praveen

Log printout have to be changed to notification since in some cases 
"saImmOiDispatch() Fail SA_AIS_ERR_BAD_HANDLE (9)" is not an error.

When node shutting down and NTF executes "saImmOiDispatch" and receives reply 
"SA_AIS_ERR_BAD_HANDLE":

Oct 28 14:16:43 localhost osafrded[239]: exiting for shutdown
Oct 28 14:16:43 localhost osafclmna[304]: exiting for shutdown
Oct 28 14:16:43 localhost osafckptnd[349]: exiting for shutdown
Oct 28 14:16:43 localhost osafsmfd[417]: exiting for shutdown
Oct 28 14:16:43 localhost osafimmnd[263]: NO Implementer locally disconnected. 
Marking it as doomed 14 <244, 2020f> (safSmfService)
Oct 28 14:16:43 localhost osafimmnd[263]: NO Implementer disconnected 14 <244, 
2020f> (safSmfService)
Oct 28 14:16:43 localhost osafimmd[255]: exiting for shutdown
Oct 28 14:16:43 localhost osafimmnd[263]: exiting for shutdown
Oct 28 14:16:43 localhost osafntfimcnd[838]: ER saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)

In the above case IMM went down when dispatch called and the agent replied with 
"SA_AIS_ERR_BAD_HANDLE". That case a notification needed to be logged instead 
of an error.



---

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.
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to