I am able to reproduce again, with the changeset 4837.  The assert occurred at 
at the time "Jan 24 03:09".

some reason the syslog is not available at exact time, the problem is 
reproducible, the similar syslog is available.


Jan 23 03:20:56 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 2096 
<0, 2030f> (MsgQueueService131855)
Jan 23 03:20:56 SLES-SLOT-1 osafimmnd[4006]: NO Implementer connected: 2098 
(MsgQueueService131855) <0, 2030f>
Jan 23 03:21:22 SLES-SLOT-1 osafmsgd[4126]: ER mqd_asapi.c:684: ERR_NOT_EXIST: 
Database Operation (UPD) Failed
Jan 23 03:21:22 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 2098 
<0, 2030f> (MsgQueueService131855)
Jan 23 03:21:22 SLES-SLOT-1 osafimmnd[4006]: NO Implementer connected: 2099 
(MsgQueueService131855) <0, 2030f>
Jan 23 03:21:23 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 2099 
<0, 2030f> (MsgQueueService131855)
Jan 23 03:21:24 SLES-SLOT-1 osafimmnd[4006]: NO Implementer connected: 2100 
(MsgQueueService131855) <0, 2030f>
Jan 23 03:21:25 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 2100 
<0, 2030f> (MsgQueueService131855)
Jan 23 03:21:25 SLES-SLOT-1 osafimmnd[4006]: NO Implementer connected: 2101 
(MsgQueueService131855) <0, 2030f>
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:22:06 SLES-SLOT-1 osafmsgd[4126]: ER ERR_NOT_EXIST: Track list 
associated with the object not found
Jan 23 03:24:11 SLES-SLOT-1 osafamfd[4065]: NO safSi=SC-2N,safApp=OpenSAF Swap 
initiated
Jan 23 03:24:11 SLES-SLOT-1 osafamfnd[4075]: NO Assigning 
'safSi=SC-2N,safApp=OpenSAF' QUIESCED to 'safSu=SC-1,safSg=2N,safApp=OpenSAF'
Jan 23 03:24:11 SLES-SLOT-1 osaflogd[4019]: lgs_stream.c:889: 
log_stream_file_close: Assertion 'stream->numOpeners > 0' failed.
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 5 
<313, 2010f> (safMsgGrpService)
Jan 23 03:24:11 SLES-SLOT-1 osafamfnd[4075]: NO 
'safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'
Jan 23 03:24:11 SLES-SLOT-1 osafamfnd[4075]: ER 
safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast
Jan 23 03:24:11 SLES-SLOT-1 osafamfnd[4075]: Rebooting OpenSAF NodeId = 131343 
EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 
131343, SupervisionTime = 60
Jan 23 03:24:11 SLES-SLOT-1 opensaf_reboot: Rebooting local node; timeout=60
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO Implementer locally 
disconnected. Marking it as doomed 1 <4, 2010f> (safLogService)
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO implementer for class 
'SaSmfCampaign' is released => class extent is UNSAFE
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 8 
<329, 2010f> (safEvtService)
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 1 <4, 
2010f> (safLogService)
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO implementer for class 
'OpenSafSmfConfig' is released => class extent is UNSAFE
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO implementer for class 
'SaSmfSwBundle' is released => class extent is UNSAFE
Jan 23 03:24:11 SLES-SLOT-1 osafimmnd[4006]: NO Implementer disconnected 9 
<307, 2010f> (safSmfService)




---

** [tickets:#714] LGS: logd is asserting, when a switchover is initiated**

**Status:** unassigned
**Created:** Fri Jan 10, 2014 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Mon Jan 13, 2014 07:01 AM UTC
**Owner:** nobody

Nodes: SC1, SC2, PL-3,PL-4
changeset:4804
when switchover is run, the logd is asserting, and controller is going for 
reboot.


SC-1 syslog:
--------------

Jan 10 14:29:21 SLES-SLOT-1 osafimmnd[3340]: NO implementer for class 
'SaSmfCampaign' is released => class extent is UNSAFE
Jan 10 14:29:21 SLES-SLOT-1 osafimmnd[3340]: NO implementer for class 
'OpenSafSmfConfig' is released => class extent is UNSAFE
Jan 10 14:29:21 SLES-SLOT-1 osaflogd[3349]: lgs_stream.c:889: 
log_stream_file_close: Assertion 'stream->numOpeners > 0' failed.
Jan 10 14:29:21 SLES-SLOT-1 osafimmnd[3340]: NO implementer for class 
'SaSmfSwBundle' is released => class extent is UNSAFE
Jan 10 14:29:21 SLES-SLOT-1 osafamfnd[3401]: NO 
'safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'
Jan 10 14:29:21 SLES-SLOT-1 osafamfnd[3401]: ER 
safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast



The syslog of SC-1, and SC-2 is attached along with the logd trace of SC-1, 
when the logd got asserted.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to