The problem seems to be that a topology event is arriving after the data event:
<139>1 2017-06-01T00:32:21.356449+02:00 SC-1 osafimmd 207 mds.log [meta
sequenceId="79"] MDS_SND_RCV:No Route Found from svc_id = IMMD(24), to svc_id =
IMMND(25) on Adest = <0x0002020f, 665691278>
<139>1 2017-06-01T00:32:21.356469+02:00 SC-1 osafimmd 207 mds.log [meta
sequenceId="80"] MDS_SND_RCV: Normal send Message sent Failed from svc_id =
IMMD(24), to svc_id = IMMND(25)
<139>1 2017-06-01T00:32:21.356491+02:00 SC-1 osafimmd 207 mds.log [meta
sequenceId="81"] MDS_SND_RCV: Adest=<0x0002020f,665691278>
<141>1 2017-06-01T00:32:21.356528+02:00 SC-1 osafamfd 258 mds.log [meta
sequenceId="117"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= IMMA_OM(26) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.356553+02:00 SC-1 python 440 mds.log [meta
sequenceId="9"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id =
IMMA_OM(26) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.356579+02:00 SC-1 osafamfd 258 mds.log [meta
sequenceId="118"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= IMMA_OI(27) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.356651+02:00 SC-1 osafckptd 312 mds.log [meta
sequenceId="102"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= IMMA_OI(27) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.356777+02:00 SC-1 osaffmd 197 mds.log [meta
sequenceId="44"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= GFM(23) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.356986+02:00 SC-1 osaflogd 228 mds.log [meta
sequenceId="148"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= IMMA_OI(27) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
<141>1 2017-06-01T00:32:21.357081+02:00 SC-1 osafimmd 207 mds.log [meta
sequenceId="82"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id
= IMMD(24) pwe_id=1 Adest = <rem_node[2]:dest_tipc_id_ref[665691278]>
there is a "discovery" mechanism in MDS that waits default 1.5 seconds for a
topology event such as service up. It seems this that 1.5 seconds
has been exceeded.
---
** [tickets:#2426] mds: MDS send failure**
**Status:** accepted
**Milestone:** 5.17.08
**Created:** Thu Apr 13, 2017 11:22 AM UTC by Hung Nguyen
**Last Updated:** Thu Jun 01, 2017 11:31 AM UTC
**Owner:** Hans Nordebäck
**Attachments:**
-
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/2426/attachment/logs.tgz)
(1.8 MB; application/x-compressed)
IMMD@SC-2 recived a message from IMMND@SC-1 but failed to send a message back
to IMMND@SC-1.
Both IMMD and IMMND use MDS_SENDTYPE_SND.
RDE also got that failure.
~~~
18:33:18 SC-1 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to
2020f9d120640
18:33:18 SC-1 osafrded[183]: message repeated 2 times: [ WA Failed to send
RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640]
18:33:18 SC-2 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to
2010fc4b8a390
18:33:18 SC-2 osafimmd[202]: WA IMMD - MDS Send Failed
18:33:18 SC-2 osafimmd[202]: ER Failed to send accept message to IMMND 2010f
~~~
Attached is the logs.
---
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
