- **status**: unassigned --> fixed
- **assigned_to**: Mathi Naickan
---
** [tickets:#564] CLM: CLMD ignores ERR_LIBRARY from saImmOIRtObjectUpdate**
**Status:** fixed
**Created:** Wed Sep 11, 2013 10:55 AM UTC by Anders Bjornerstedt
**Last Updated:** Wed Sep 11, 2013 10:55 AM UTC
**Owner:** Mathi Naickan
While testing SC failover in conjunction with restart of several payloads
I see this:
------------------------------------------------------------
Sep 11 10:53:44 SC-1 local0.notice osafamfd[443]: NO Node 'SC-2' left the
cluster
Sep 11 10:53:44 SC-1 local0.notice osafamfd[443]: NO FAILOVER StandBy -->
Active DONE!
Sep 11 10:53:44 SC-1 local0.notice osafamfnd[453]: NO Assigning
'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF'
Sep 11 10:53:44 SC-1 user.notice kernel: TIPC: Resetting link
<1.1.1:eth0-1.1.4:eth0>, requested by peer while probing
Sep 11 10:53:44 SC-1 user.notice kernel: TIPC: Lost link
<1.1.1:eth0-1.1.4:eth0> on network plane A
Sep 11 10:53:44 SC-1 user.notice kernel: TIPC: Lost contact with <1.1.4>
Sep 11 10:53:44 SC-1 user.notice kernel: TIPC: Established link
<1.1.1:eth0-1.1.2:eth0> on network plane A
Sep 11 10:53:44 SC-1 local0.notice osafamfd[443]: NO Node 'PL-3' left the
cluster
Sep 11 10:53:44 SC-1 local0.notice osafamfd[443]: NO Node 'PL-4' left the
cluster
Sep 11 10:53:44 SC-1 local0.notice osafamfd[443]: NO Node 'PL-5' left the
cluster
Sep 11 10:53:44 SC-1 local0.err osafclmd[424]: ER saImmOiRtObjectUpdate FAILED
2, 'safNode=SC-2,safCluster=myClmCluster'
Sep 11 10:53:44 SC-1 local0.err osafclmd[424]: ER saImmOiRtObjectUpdate FAILED
2, 'safCluster=myClmCluster'
Sep 11 10:53:44 SC-1 local0.err osafclmd[424]: ER saImmOiRtObjectUpdate FAILED
2, 'safNode=PL-3,safCluster=myClmCluster'
Sep 11 10:53:44 SC-1 local0.err osafclmd[424]: ER saImmOiRtObjectUpdate FAILED
2, 'safCluster=myClmCluster'
-------------------------------------------------------------------
Note the LOG_ER messages from CLMD due to getting ERR_LIBRARY from
saImmOIRtObjectUpddate, and then just ignoring it.
There are several problems here.
(1) ERR_LIBRARY is a serious error and should not be ignored.
The most probable cause is that CLMD uses the OI handle concurrently from
several threads. This is incorrect usage. Other possible casues are
library locking failure, but that in turn indicates something much more
serious such as a heap overwrite.
(2) In the particular case above, an update of a cached runtime attribute is
dropped. While not necessarily a serious problem in general, it seems to me that
a CLM service that just drops its updates to the runtime state of the
ClmCluster and safNode objects could be seen as it failing in one of its
main purposes, that of reflecting an accurate picture of the cluster state.
Cached runtime data can not be guaranteed to be 100% realtime updated.
But here the CLM service drops the task a bit too frivolously.
3) CLMD uses severity ERR for practically all its syslog messages.
It should only use that severity for problems that indicate CLMD internal
inconsistency (and fail-fast process termination) or at least problems
serious enough to merit trouble reporting by testers (such as me in this case).
(4) CLM user errors should use LOG_NOtice or possibly not log at all since it
can cause spamming of the syslogs.
---
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.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
