Hi Mahesh,
Here's the immnd trace and mds log for this problem.
~~~
11:26:21.778367 osafimmnd[5238] NOTIFY |MDTM: svc down event for svc_id =
IMMA_OM(26), subscri. by svc_id = IMMND(25) pwe_id=1 Adest =
<nodeid[1]:osafimmnd[5238]>
11:26:21.778474 osafimmnd[5238] NOTIFY |MDTM: svc up event for svc_id =
IMMA_OM(26), subscri. by svc_id = IMMND(25) pwe_id=1 Adest =
<nodeid[1]:osafimmnd[5238]>
~~~
~~~
11:26:21.779135 osafimmnd [5238:immsv_evt.c:5473] T8 Received:
IMMND_EVT_MDS_INFO (1) from 0
11:26:21.779147 osafimmnd [5238:immnd_evt.c:10368] T2 IMMA DOWN EVENT
11:26:21.779225 osafimmnd [5238:immsv_evt.c:5473] T8 Received:
IMMND_EVT_MDS_INFO (1) from 0
11:26:21.779237 osafimmnd [5238:immnd_evt.c:10443] T2 IMMA UP EVENT
~~~
IMM received an NCSMDS_DOWN event and an NCSMDS_UP event right after that.
There's no message from client, so the client didn't call
ImmOmFinalize()/ImmOmInitialize().
It seemed that the connection is not stable/flickering or something like that
(?)
Dsock is a tipc socket, maybe this is a problem with tipc (?)
When there's a "withdrawn event", MDS starts a timer to remove the process info
after 10 seconds.
That's the reason why IMM can't read the PID.
~~~
11:26:31.878622 osafimmnd [5238:mds_dt_common.c:0862] TR TIMEOUT, deleting
entry for 2010ffc93cf53, pid:5725
11:26:31.878655 osafimmnd [5238:mds_c_db.c:2527] >> mds_process_info_del:
dest:2010ffc93cf53, pid:5725, svc:26
~~~
The question is: should/does MDS clear the timer when it receives "published
event" from the same adest+svc_id ?
The problem can be solved if the timer is cleared.
Attachments:
-
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/62c4df9d/b855/attachment/logs.tgz)
(5.5 MB; application/x-compressed)
---
** [tickets:#1825] MDS: When saImmOmInitialize was invoked, MDS sent ‘pid = 0’
in MDS_CALLBACK_RECEIVE_INFO.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri May 13, 2016 12:34 PM UTC by Rafael
**Last Updated:** Tue May 17, 2016 11:44 AM UTC
**Owner:** nobody
**Attachments:**
-
[sc2_mds.log](https://sourceforge.net/p/opensaf/tickets/1825/attachment/sc2_mds.log)
(2.6 MB; text/x-log)
This happens only some of the time.
First this is called from an application:
saImmOmInitialize(immHandle, NULL, &version)
Then the system log shows this error:
May 13 02:31:53 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0
(7150) for 2020fb1d13cb8, MDS problem?
May 13 02:31:53 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0
(7150) for 2020fb1d13cb8, MDS problem?
May 13 02:31:55 sc2 osafimmnd[6042]: NO Ccb 176 COMMITTED (LDE)
May 13 02:31:55 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0
(7150) for 2020fb1d13cb8, MDS problem?
May 13 02:31:55 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0
(7150) for 2020fb1d13cb8, MDS problem?
---
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.------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
