[tickets] [opensaf:tickets] #2485 amfnd: missing susi response if component is restarted

2017-06-14 Thread Minh Hon Chau via Opensaf-tickets 
- **status**: review --> fixed
- **assigned_to**: Minh Hon Chau -->  nobody 
- **Comment**:

Commits
release: [cadf0443630292bc99cb2ee900b2d84580b47e07]
develope: [a3213500fb83042d97c0b2b82940c257f1668013]



---

** [tickets:#2485] amfnd: missing susi response if component is restarted**

**Status:** fixed
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 12:57 AM UTC by Gary Lee
**Last Updated:** Tue Jun 13, 2017 02:59 AM UTC
**Owner:** nobody


An SI contains multiple CSIs. If a restart component admin operation arrives at 
amfnd before all CSIs are assigned,
the SUSI response is not sent to AMFD.

This code in avnd_comp_csi_assign_done() appears to be the problem area.

  /* while restarting, we wont use assign all, so csi will not be null */
  if (csi && m_AVND_COMP_CSI_CURR_ASSIGN_STATE_IS_RESTARTING(csi)) {
m_AVND_COMP_CSI_CURR_ASSIGN_STATE_SET(csi,
  AVND_COMP_CSI_ASSIGN_STATE_ASSIGNED);
goto done;
  }

Perhaps we should not initiate a restart in avnd_evt_comp_admin_op_req(), if
a component is still in AVND_COMP_CSI_ASSIGN_STATE_ASSIGNING state.


---

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

[tickets] [opensaf:tickets] #2481 imm: node crashes due to missing discard node info during the sync

2017-06-14 Thread Zoran Milinkovic via Opensaf-tickets 
- **status**: review --> fixed
- **Comment**:

commit b5864c91a82fb27f02b09eaa2ffc3db456f1e67a
Author: Zoran Milinkovic 
Date:   Wed Jun 14 16:25:50 2017 +0200

imm: remove vector clearing for dead implementers, nodes and admin owners 
in objectSync [#2481]

After removing the clearing of dead implementer, node and admin owner 
vectors, re-executing on vectors will be done after the node is fully synced.



---

** [tickets:#2481] imm: node crashes due to missing discard node info during 
the sync**

**Status:** fixed
**Milestone:** 5.17.06
**Created:** Fri Jun 02, 2017 02:39 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Jun 02, 2017 03:24 PM UTC
**Owner:** Zoran Milinkovic


When a node receives the discard node message during the sync, re-executing 
discard node is not done after the node is synced.

Jun  1 09:09:46 PL-16 osafimmnd[20197]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Jun  1 09:09:46 PL-16 osafimmnd[20197]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Jun  1 09:09:48 PL-16 osafimmnd[20197]: NO Global discard node received for 
nodeId:2090f pid:20533
Jun  1 09:09:48 PL-16 osafimmnd[20197]: NO NODE STATE-> 
IMM_NODE_FULLY_AVAILABLE 2715
Jun  1 09:09:48 PL-16 osafimmnd[20197]: NO RepositoryInitModeT is 
SA_IMM_INIT_FROM_FILE
Jun  1 09:09:48 PL-16 osafimmnd[20197]: WA IMM Access Control mode is DISABLED!
Jun  1 09:09:48 PL-16 osafimmnd[20197]: NO Epoch set to 58 in ImmModel

It results in many messages like:
Jun  1 09:09:55 PL-16 osafimmnd[20197]: NO Sync-verify: Veteran node has 
different Implementer-id 41 for implementer: @safPmService1333912, should be 0 
according to finalizeSync. Assunimg implSet bypased finSync
Jun  1 09:10:07 PL-16 osafimmnd[20197]: NO Sync-verify: Veteran node has 
different Implementer-id 41 for implementer: @safPmService1333912, should be 0 
according to finalizeSync. Assunimg implSet bypased finSync

And at the end, when the IMM data inconsistency is detected, IMM aborts:
Jun 1 09:18:19 PL-16 osafimmnd[20197]: ER Sync-verify: Established node has 
different Implementer-id: 41 for name: @safPmService1333912, sync says 578.



---

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

[tickets] [opensaf:tickets] #2495 imm: saImmOmCcbApply times out due to miscalculation for old critical CCBs

2017-06-14 Thread Zoran Milinkovic via Opensaf-tickets 
- **status**: accepted --> review
- **Comment**:

https://sourceforge.net/p/opensaf/mailman/message/35893768/



---

** [tickets:#2495] imm: saImmOmCcbApply times out due to miscalculation for old 
critical CCBs**

**Status:** review
**Milestone:** 5.17.06
**Created:** Tue Jun 13, 2017 02:57 PM UTC by Zoran Milinkovic
**Last Updated:** Wed Jun 14, 2017 03:17 AM UTC
**Owner:** Zoran Milinkovic


When IMM fetches old critical CCBs, IMM does not add timed out CCBs in a vector 
due to miscalculation for expired CCBs.
Instead of adding expired CCBs to the vector, IMM continues to calculate 
timeout in minus.

2017-05-25 17:58:27 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:27 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-0.382578
2017-05-25 17:58:28 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:28 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-1.387785
2017-05-25 17:58:29 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:29 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-2.392967
2017-05-25 17:58:30 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:30 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-3.398186
2017-05-25 17:58:31 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:31 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-4.403361
2017-05-25 17:58:32 SC-1 osafimmnd[205]: WA Timeout (6) on transaction in 
critical state! ccb:2
2017-05-25 17:58:32 SC-1 osafimmnd[205]: NO Ccb 2 is old, but also large (1) 
will wait secs:-5.408588
.

The bug was introduced in OpenSAF 5.1 with ticket #1704


---

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

[tickets] [opensaf:tickets] #2496 amf: amfd crashes while trying to free invalid memory.

2017-06-14 Thread Praveen via Opensaf-tickets 
- **status**: accepted --> review



---

** [tickets:#2496] amf: amfd crashes while trying to free invalid memory.**

**Status:** review
**Milestone:** 5.17.06
**Created:** Wed Jun 14, 2017 08:49 AM UTC by Praveen
**Last Updated:** Wed Jun 14, 2017 08:49 AM UTC
**Owner:** Praveen


Steps to reproduce:
1)Bring AMF demo up on one controller.
2)Issue lock operation on active SU.
3)When component is still processing quiesced assignment, run below command:
immlist safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
4)AMF wil crash for updating runtime atributes of SU in su_rt_attr_cb().

bt:
\#0  0x7fac6971fcc9 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
\#1  0x7fac697230d8 in __GI_abort () at abort.c:89
\#2  0x7fac6975c394 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7fac6986ab28 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
\#3  0x7fac6976866e in malloc_printerr (ptr=,
str=0x7fac6986acc8 "free(): invalid next size (fast)", action=1) at 
malloc.c:4996
\#4  _int_free (av=, p=, have_lock=0) at 
malloc.c:3840
\#5  0x7fac6b4c471a in su_rt_attr_cb (immOiHandle=, 
objectName=,
attributeNames=) at src/amf/amfd/su.cc:1501
\#6  0x7fac6b4531f1 in rt_attr_update_cb (immoi_handle=94489411855, 
object_name=0x7fac640041b8,
attribute_names=0x7fac6c104290) at src/amf/amfd/imm.cc:881
\#7  0x7fac6a99bc42 in imma_process_callback_info 
(cb=cb@entry=0x7fac6aba6320 , cl_node=0x7fac6c0cf250,
callback=callback@entry=0x7fac64004190, immHandle=94489411855) at 
src/imm/agent/imma_proc.cc:3266
\#8  0x7fac6a99bf79 in imma_hdl_callbk_dispatch_all (cb=0x7fac6aba6320 
, immHandle=94489411855)
at src/imm/agent/imma_proc.cc:1812
\#9  0x7fac6a99301d in saImmOiDispatch (immOiHandle=94489411855, 
dispatchFlags=SA_DISPATCH_ALL)
at src/imm/agent/imma_oi_api.cc:642
\#10 0x7fac6b412868 in main_loop () at src/amf/amfd/main.cc:717
\#11 main (argc=, argv=) at 
src/amf/amfd/main.cc:848



---

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

[tickets] [opensaf:tickets] #2496 amf: amfd crashes while trying to free invalid memory.

2017-06-14 Thread Praveen via Opensaf-tickets 



---

** [tickets:#2496] amf: amfd crashes while trying to free invalid memory.**

**Status:** accepted
**Milestone:** 5.17.06
**Created:** Wed Jun 14, 2017 08:49 AM UTC by Praveen
**Last Updated:** Wed Jun 14, 2017 08:49 AM UTC
**Owner:** Praveen


Steps to reproduce:
1)Bring AMF demo up on one controller.
2)Issue lock operation on active SU.
3)When component is still processing quiesced assignment, run below command:
immlist safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
4)AMF wil crash for updating runtime atributes of SU in su_rt_attr_cb().

bt:
\#0  0x7fac6971fcc9 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
\#1  0x7fac697230d8 in __GI_abort () at abort.c:89
\#2  0x7fac6975c394 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7fac6986ab28 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
\#3  0x7fac6976866e in malloc_printerr (ptr=,
str=0x7fac6986acc8 "free(): invalid next size (fast)", action=1) at 
malloc.c:4996
\#4  _int_free (av=, p=, have_lock=0) at 
malloc.c:3840
\#5  0x7fac6b4c471a in su_rt_attr_cb (immOiHandle=, 
objectName=,
attributeNames=) at src/amf/amfd/su.cc:1501
\#6  0x7fac6b4531f1 in rt_attr_update_cb (immoi_handle=94489411855, 
object_name=0x7fac640041b8,
attribute_names=0x7fac6c104290) at src/amf/amfd/imm.cc:881
\#7  0x7fac6a99bc42 in imma_process_callback_info 
(cb=cb@entry=0x7fac6aba6320 , cl_node=0x7fac6c0cf250,
callback=callback@entry=0x7fac64004190, immHandle=94489411855) at 
src/imm/agent/imma_proc.cc:3266
\#8  0x7fac6a99bf79 in imma_hdl_callbk_dispatch_all (cb=0x7fac6aba6320 
, immHandle=94489411855)
at src/imm/agent/imma_proc.cc:1812
\#9  0x7fac6a99301d in saImmOiDispatch (immOiHandle=94489411855, 
dispatchFlags=SA_DISPATCH_ALL)
at src/imm/agent/imma_oi_api.cc:642
\#10 0x7fac6b412868 in main_loop () at src/amf/amfd/main.cc:717
\#11 main (argc=, argv=) at 
src/amf/amfd/main.cc:848



---

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