Adding mds.log
Not only IMMD but also AMFD had this MBC problem
<pre>
Nov 21 11:06:16.926819 osafimmd[4183] ERR |MDS_SND_RCV:No Route Found from
svc_id = MBCSV(19), to svc_id = MBCSV(19) on Adest = <nodeid[2]:osafimmd[4183]>
Nov 21 11:06:16.926920 osafimmd[4183] ERR |MDS_SND_RCV: RED send Message sent
Failed from svc_id = MBCSV(19), to svc_id = MBCSV(19)
Nov 21 11:06:16.926944 osafimmd[4183] ERR |MDS_SND_RCV: Adest=<0x00000000,13>
Nov 21 11:06:16.926967 osafimmd[4183] ERR |MDS_SND_RCV:
Anchor=<0x0002010f,2993899434>
Nov 21 11:06:16.927088 osafimmd[4183] ERR |MDS_SND_RCV:No Route Found from
svc_id = MBCSV(19), to svc_id = MBCSV(19) on Adest = <nodeid[2]:osafimmd[4183]>
Nov 21 11:06:16.927110 osafimmd[4183] ERR |MDS_SND_RCV: RED send Message sent
Failed from svc_id = MBCSV(19), to svc_id = MBCSV(19)
Nov 21 11:06:16.927132 osafimmd[4183] ERR |MDS_SND_RCV: Adest=<0x00000000,13>
Nov 21 11:06:16.927153 osafimmd[4183] ERR |MDS_SND_RCV:
Anchor=<0x0002010f,2993899434>
</pre>
<pre>
Nov 21 11:05:17.792951 osafamfd[4276] ERR |MDS_SND_RCV:No Route Found from
svc_id = MBCSV(19), to svc_id = MBCSV(19) on Adest = <nodeid[2]:osafamfd[4276]>
Nov 21 11:05:17.792977 osafamfd[4276] ERR |MDS_SND_RCV: RED send Message sent
Failed from svc_id = MBCSV(19), to svc_id = MBCSV(19)
Nov 21 11:05:17.793000 osafamfd[4276] ERR |MDS_SND_RCV: Adest=<0x00000000,1>
Nov 21 11:05:17.793053 osafamfd[4276] ERR |MDS_SND_RCV:
Anchor=<0x0002010f,3751409323>
...
Nov 21 11:05:17.860424 osafamfd[4276] ERR |MDS_SND_RCV:No Route Found from
svc_id = MBCSV(19), to svc_id = MBCSV(19) on Adest = <nodeid[2]:osafamfd[4276]>
Nov 21 11:05:17.860483 osafamfd[4276] ERR |MDS_SND_RCV: RED sndrsp message
SEND Failed from svc_id = MBCSV(19), to svc_id = MBCSV(19)
Nov 21 11:05:17.860507 osafamfd[4276] ERR |MDS_SND_RCV: Adest=<0x00000000,1>
Nov 21 11:05:17.860529 osafamfd[4276] ERR |MDS_SND_RCV:
Anchor=<0x0002010f,3751409323>
</pre>
Attachments:
-
[1606_log.7z](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/b899e4dc/c6c1/attachment/1606_log.7z)
(2.2 MB; application/octet-stream)
---
** [tickets:#1606] mbc: No error handling when sending peer-discovery messages**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Fri Nov 20, 2015 07:14 AM UTC by Hung Nguyen
**Last Updated:** Fri Nov 20, 2015 07:14 AM UTC
**Owner:** nobody
**Attachments:**
-
[mbcsv.7z](https://sourceforge.net/p/opensaf/tickets/1606/attachment/mbcsv.7z)
(3.1 MB; application/octet-stream)
When a standby peer is up, it will:
1. send PEER_UP_MSG to active peer
2. receive PEER_INFO_MSG from active peer
3. send PEER_INFO_RSP_MSG to active peer
But if the active peer fails to send PEER_INFO_MSG, the standby peer will also
never send PEER_INFO_RSP_MSG to the active peer.
<pre>--- trace on active peer ---
osafimmd [4477:mbcsv_peer.c:0897] >> mbcsv_send_peer_disc_msg
osafimmd [4477:mbcsv_peer.c:0908] TR peer info msg
osafimmd [4477:mbcsv_mds.c:0185] >> mbcsv_mds_send_msg: sending to vdest:d
osafimmd [4477:mbcsv_mds.c:0201] TR send type MDS_SENDTYPE_RED
osafimmd [4477:mbcsv_mds.c:0247] << mbcsv_mds_send_msg: failure
osafimmd [4477:mbcsv_peer.c:0942] << mbcsv_send_peer_disc_msg
</pre>
That resulted in the active peer kept the standby peer in
'NCS_MBCSV_ACT_STATE_IDLE' state.
The state would have been changed to
'NCS_MBCSV_ACT_STATE_WAIT_FOR_COLD_WARM_SYNC' if the standby had been able to
send the PEER_INFO_RSP_MSG to the active peer.
And that made the active peer failed to dispatch on
NCSMBCSV_EVENT_COLD_SYNC_REQ.
<pre>--- trace on standby peer ---
osafimmd [4645:mbcsv_act.c:0293] TR sending cold sync req. myrole: 2, svc_id:
42, pwe_hdl: 65549
...
osafimmd [4645:mbcsv_tmr.c:0250] TR Timer expired. my role:2, svc_id:42,
pwe_hdl:65549, peer_anchor:565213722578604, tmr
type:NCS_MBCSV_TMR_SEND_COLD_SYNC
</pre>
<pre>--- trace on active peer ---
osafimmd [4477:mbcsv_pr_evts.c:0068] >> mbcsv_process_events: mbcsv hdl:
4293918753
osafimmd [4477:mbcsv_pr_evts.c:0160] TR Internal event
osafimmd [4477:mbcsv_act.c:0079] TR Illegal dispatch event. role:1, svc_id: 42,
pwe_hdl:65549
osafimmd [4477:mbcsv_pr_evts.c:0222] << mbcsv_process_events
</pre>
MBC should somehow retry mbcsv_mds_send_msg when it fails.
---
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.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
