Update:
I checked the log again and saw that the IMMA down event (NCSMDS_DOWN) is not
unexpected.
It just came late.
~~~
11:26:21.775374 [immsv_evt.c:5473] T8 Received: IMMND_EVT_A2ND_IMM_FINALIZE (5)
from 2010f
11:26:21.775529 [mds_main.c:0153] TR MDS: received 79 from 2010ffc93cf53, pid
5725
11:26:21.776493 [mds_main.c:0153] TR MDS: received 77 from 2010ffc93cf53, pid
5725
11:26:21.776703 [immsv_evt.c:5473] T8 Received: IMMND_EVT_A2ND_IMM_INIT (3)
from 2010f
11:26:21.779147 [immnd_evt.c:10368] T2 IMMA DOWN EVENT
11:26:21.779237 [immnd_evt.c:10443] T2 IMMA UP EVENT
~~~
The normal order would be
~~~
17:29:00.897880 [immsv_evt.c:5473] T8 Received: IMMND_EVT_A2ND_IMM_FINALIZE (5)
from 2010f
17:29:00.898182 [mds_main.c:0153] TR MDS: received 79 from 2010fd6dc3d6d, pid
685
17:29:00.898526 [immnd_evt.c:10386] T2 IMMA DOWN EVENT
17:29:00.899954 [immnd_evt.c:10461] T2 IMMA UP EVENT
17:29:00.900299 [mds_main.c:0153] TR MDS: received 77 from 2010f28dd3e79, pid
685
17:29:00.900532 [immsv_evt.c:5473] T8 Received: IMMND_EVT_A2ND_IMM_INIT (3)
from 2010f
~~~
So the problem is not tipc connection flickering.
It's just that the event came late.
We can't control the order since MDS events and MDS messages come from seperate
sockets (Dsock and BSRsock) and the auth server is an seperate thread.
The only thing we can make sure that will come in order is NCSMDS_DOWN and
NCSMDS_UP.
So I still think that MDS should clear the down timer when receiving NCSMDS_UP.
---
** [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:** Wed May 18, 2016 09:07 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 [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.------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
