- **Milestone**: 4.2.4 --> future
---
** [tickets:#129] CLM: CLMD gets BAD_HANDLE on classImplementeSet causes node
reboot.**
**Status:** unassigned
**Created:** Mon May 13, 2013 09:40 AM UTC by Anders Bjornerstedt
**Last Updated:** Fri May 24, 2013 08:29 AM UTC
**Owner:** nobody
See ticket [#37].
Killing the IMMND coord durign a switchover will cause CLMD to crash
at new active. The CLMD needs to cope with getting ERR_BAD_HANDLE when
it tries implementerSet and/or classImplementerSet to become active.
It needs to re-initialize the oi-handle for this case.
May 7 15:43:18 OEL-64BIT-SLOT1 osaflogd[13604]: ER saImmOiClassImplementerSet
(safLogService) failed: 9
May 7 15:43:18 OEL-64BIT-SLOT1 osafclmd[13638]: ER saImmOiClassImplementerSet
failed for class SaClmNode rc:9, exiting
May 7 15:43:18 OEL-64BIT-SLOT1 osafamfnd[13686]: ER
safComp=CLM,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery
is:nodeFailfast
May 7 15:43:18 OEL-64BIT-SLOT1 osafamfnd[13686]: Rebooting OpenSAF NodeId =
131343 EE Name = , Reason: Component faulted: recovery is node failfast
May 7 15:43:18 OEL-64BIT-SLOT1 opensaf_reboot: Rebooting local node
---
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.
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
