[tickets] [opensaf:tickets] #2604 imm: osafimmpbed coredump when building with coverage enabled
- **status**: accepted --> fixed - **Comment**: develop (5.17.10) [code:bc4979] ~~~ commit bc497981905f39aaa5b63cdf85b7557972650d94 Author: Hung Nguyen Date: Mon Oct 2 13:28:40 2017 +0700 imm: Don't call exit() in IMM library [#2604] When PBE loses connection with IMMND, we don't call exit() in IMM library. Instead, we mark the handle as exposed and then PBE will exit when it fails to call saImmOmDispatch. ~~~ release [code:9094ca] ~~~ commit 9094ca52ef7649a803097ed86663774abc61d6f9 Author: Hung Nguyen Date: Mon Oct 2 13:28:40 2017 +0700 imm: Don't call exit() in IMM library [#2604] When PBE loses connection with IMMND, we don't call exit() in IMM library. Instead, we mark the handle as exposed and then PBE will exit when it fails to call saImmOmDispatch. ~~~ --- ** [tickets:#2604] imm: osafimmpbed coredump when building with coverage enabled** **Status:** fixed **Milestone:** 5.17.10 **Created:** Sun Oct 01, 2017 02:20 AM UTC by Hung Nguyen **Last Updated:** Sun Oct 01, 2017 02:20 AM UTC **Owner:** Hung Nguyen When IMMND is down or unregisters MDS (for headless), pbe may call exit() in both main thread and MDS thread. ~~~ 09:26:40.343 SC-1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db handle 09:26:40.343 SC-1 osafimmpbed: IN IMM PBE process EXITING... ### main thread 09:26:40.347 SC-1 osafimmnd[213]: WA SC Absence IS allowed:900 IMMD service is DOWN 09:26:40.347 SC-1 osafimmnd[213]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS 09:26:40.348 SC-1 osafimmnd[213]: NO Removing client id:1050002010f sv_id:27 09:26:40.349 SC-1 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting ### MDS thread ~~~ ~~~ 11:34:20.183 SC-2 osafimmpbed: NO IMM PBE received SIG_TERM, closing db handle 11:34:20.184 SC-2 osafimmpbed: IN IMM PBE process EXITING... ### main thread 11:34:20.194 SC-2 osafimmnd[213]: exiting for shutdown 11:34:20.195 SC-2 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting ### MDS thread ~~~ In exit(), gcov_do_dump() is called. Calling gcov_do_dump() in both threads causes PBE to carsh. ~~~ Thread 3 (Thread 0x7f3a4bc74740 (LWP 242)): #0 0x7f3a4a62270b in do_fcntl (arg=, cmd=7, fd=22) at ../sysdeps/unix/sysv/linux/fcntl.c:31 #1 __libc_fcntl (fd=22, cmd=) at ../sysdeps/unix/sysv/linux/fcntl.c:75 #2 0x7f3a4aea1621 in __gcov_open () from /usr/local/lib/libopensaf_core.so.0 #3 0x7f3a4aea220e in gcov_do_dump () from /usr/local/lib/libopensaf_core.so.0 #4 0x7f3a4aea3172 in gcov_exit () from /usr/local/lib/libopensaf_core.so.0 #5 0x7f3a4a28336a in __cxa_finalize (d=0x7f3a4b0cbe20) at cxa_finalize.c:56 #6 0x7f3a4ae05da3 in __do_global_dtors_aux () from /usr/local/lib/libopensaf_core.so.0 #7 0x7ffe44419580 in ?? () #8 0x7f3a4ba6ec17 in _dl_fini () at dl-fini.c:235 Backtrace stopped: frame did not save the PC Thread 2 (Thread 0x7f3a4bc71b00 (LWP 245)): ... Thread 1 (Thread 0x7f3a4bc51b00 (LWP 247)): #0 0x7f3a49b1ee78 in __gcov_read_summary () from /usr/local/lib/opensaf/libimm_common.so.0 #1 0x7f3a49b1fefe in gcov_do_dump () from /usr/local/lib/opensaf/libimm_common.so.0 #2 0x7f3a49b20592 in gcov_exit () from /usr/local/lib/opensaf/libimm_common.so.0 #3 0x7f3a4a282ff8 in __run_exit_handlers (status=1, listp=0x7f3a4a60c5f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #4 0x7f3a4a283045 in __GI_exit (status=) at exit.c:104 #5 0x7f3a4b38c6b0 in imma_mark_clients_stale (cb=0x7f3a4b5d33c0 , mark_exposed=false) at src/imm/agent/imma_db.cc:690 #6 0x7f3a4b392973 in imma_mds_svc_evt (cb=0x7f3a4b5d33c0 , svc_evt=0x7f3a44000a90) at src/imm/agent/imma_mds.cc:413 #7 0x7f3a4b39228d in imma_mds_callback (info=0x7f3a44000a80) at src/imm/agent/imma_mds.cc:221 #8 0x7f3a4ae61287 in mds_mcm_user_event_callback (local_svc_hdl=562945658454043, pwe_id=1, svc_id=25, role=V_DEST_RL_ACTIVE, vdest_id=65535, adest=564113889558741, event_type=NCSMDS_DOWN, svc_sub_part_ver=1 '\001', archword_type=10 '\n') at src/mds/mds_c_api.c:4555 #9 0x7f3a4ae5ed76 in mds_mcm_svc_down (pwe_id=1, svc_id=25, role=V_DEST_RL_ACTIVE, scope=NCSMDS_SCOPE_NONE, vdest_id=65535, vdest_policy=NCS_VDEST_TYPE_N_WAY_ROUND_ROBIN, adest=564113889558741, my_pcon=false, local_svc_hdl=562945658454043, subtn_ref_val=2, svc_sub_part_ver=1 '\001', archword_type=10 '\n') at src/mds/mds_c_api.c:3583 #10 0x7f3a4ae87ca0 in mds_mdtm_process_recvdata (rcv_bytes=34, buff_in=0x7f3a44003110 "V\022\064V\001\002V\001\004\031\240\033\377\377\240\033\377\377") at src/mds/mds_dt_trans.c:1150 #11 0x7f3a4ae86ad4 in mdtm_process_poll_recv_data_tcp () at src/mds/mds_dt_trans.c:815 #12 0x7f3a4ae87599 in mdtm_process_recv_events_tcp () at src/mds/mds_dt_trans.c:995 #13 0x7f3a4a6196ba in start_thread (arg=0x7f3a4bc51b00) at pthread_create.c:333 #14 0x7
[tickets] [opensaf:tickets] #2604 imm: osafimmpbed coredump when building with coverage enabled
--- ** [tickets:#2604] imm: osafimmpbed coredump when building with coverage enabled** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Oct 01, 2017 02:20 AM UTC by Hung Nguyen **Last Updated:** Sun Oct 01, 2017 02:20 AM UTC **Owner:** Hung Nguyen When IMMND is down or unregisters MDS (for headless), pbe may call exit() in both main thread and MDS thread. ~~~ 09:26:40.343 SC-1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db handle 09:26:40.343 SC-1 osafimmpbed: IN IMM PBE process EXITING... ### main thread 09:26:40.347 SC-1 osafimmnd[213]: WA SC Absence IS allowed:900 IMMD service is DOWN 09:26:40.347 SC-1 osafimmnd[213]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS 09:26:40.348 SC-1 osafimmnd[213]: NO Removing client id:1050002010f sv_id:27 09:26:40.349 SC-1 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting ### MDS thread ~~~ ~~~ 11:34:20.183 SC-2 osafimmpbed: NO IMM PBE received SIG_TERM, closing db handle 11:34:20.184 SC-2 osafimmpbed: IN IMM PBE process EXITING... ### main thread 11:34:20.194 SC-2 osafimmnd[213]: exiting for shutdown 11:34:20.195 SC-2 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting ### MDS thread ~~~ In exit(), gcov_do_dump() is called. Calling gcov_do_dump() in both threads causes PBE to carsh. ~~~ Thread 3 (Thread 0x7f3a4bc74740 (LWP 242)): #0 0x7f3a4a62270b in do_fcntl (arg=, cmd=7, fd=22) at ../sysdeps/unix/sysv/linux/fcntl.c:31 #1 __libc_fcntl (fd=22, cmd=) at ../sysdeps/unix/sysv/linux/fcntl.c:75 #2 0x7f3a4aea1621 in __gcov_open () from /usr/local/lib/libopensaf_core.so.0 #3 0x7f3a4aea220e in gcov_do_dump () from /usr/local/lib/libopensaf_core.so.0 #4 0x7f3a4aea3172 in gcov_exit () from /usr/local/lib/libopensaf_core.so.0 #5 0x7f3a4a28336a in __cxa_finalize (d=0x7f3a4b0cbe20) at cxa_finalize.c:56 #6 0x7f3a4ae05da3 in __do_global_dtors_aux () from /usr/local/lib/libopensaf_core.so.0 #7 0x7ffe44419580 in ?? () #8 0x7f3a4ba6ec17 in _dl_fini () at dl-fini.c:235 Backtrace stopped: frame did not save the PC Thread 2 (Thread 0x7f3a4bc71b00 (LWP 245)): ... Thread 1 (Thread 0x7f3a4bc51b00 (LWP 247)): #0 0x7f3a49b1ee78 in __gcov_read_summary () from /usr/local/lib/opensaf/libimm_common.so.0 #1 0x7f3a49b1fefe in gcov_do_dump () from /usr/local/lib/opensaf/libimm_common.so.0 #2 0x7f3a49b20592 in gcov_exit () from /usr/local/lib/opensaf/libimm_common.so.0 #3 0x7f3a4a282ff8 in __run_exit_handlers (status=1, listp=0x7f3a4a60c5f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #4 0x7f3a4a283045 in __GI_exit (status=) at exit.c:104 #5 0x7f3a4b38c6b0 in imma_mark_clients_stale (cb=0x7f3a4b5d33c0 , mark_exposed=false) at src/imm/agent/imma_db.cc:690 #6 0x7f3a4b392973 in imma_mds_svc_evt (cb=0x7f3a4b5d33c0 , svc_evt=0x7f3a44000a90) at src/imm/agent/imma_mds.cc:413 #7 0x7f3a4b39228d in imma_mds_callback (info=0x7f3a44000a80) at src/imm/agent/imma_mds.cc:221 #8 0x7f3a4ae61287 in mds_mcm_user_event_callback (local_svc_hdl=562945658454043, pwe_id=1, svc_id=25, role=V_DEST_RL_ACTIVE, vdest_id=65535, adest=564113889558741, event_type=NCSMDS_DOWN, svc_sub_part_ver=1 '\001', archword_type=10 '\n') at src/mds/mds_c_api.c:4555 #9 0x7f3a4ae5ed76 in mds_mcm_svc_down (pwe_id=1, svc_id=25, role=V_DEST_RL_ACTIVE, scope=NCSMDS_SCOPE_NONE, vdest_id=65535, vdest_policy=NCS_VDEST_TYPE_N_WAY_ROUND_ROBIN, adest=564113889558741, my_pcon=false, local_svc_hdl=562945658454043, subtn_ref_val=2, svc_sub_part_ver=1 '\001', archword_type=10 '\n') at src/mds/mds_c_api.c:3583 #10 0x7f3a4ae87ca0 in mds_mdtm_process_recvdata (rcv_bytes=34, buff_in=0x7f3a44003110 "V\022\064V\001\002V\001\004\031\240\033\377\377\240\033\377\377") at src/mds/mds_dt_trans.c:1150 #11 0x7f3a4ae86ad4 in mdtm_process_poll_recv_data_tcp () at src/mds/mds_dt_trans.c:815 #12 0x7f3a4ae87599 in mdtm_process_recv_events_tcp () at src/mds/mds_dt_trans.c:995 #13 0x7f3a4a6196ba in start_thread (arg=0x7f3a4bc51b00) at pthread_create.c:333 #14 0x7f3a4a34f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 ~~~ In imma_mark_clients_stale(), we should not call exit() directly. Instead, we should mark the handle as exposed and then the main thread of PBE will exit due to ERR_BAD_HANDLE. In general, exit() shouldn't be called in any library/agent. --- 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
[tickets] [opensaf:tickets] #2591 imm: Admo id is not updated after resurrecting the client
- **status**: review --> fixed
---
** [tickets:#2591] imm: Admo id is not updated after resurrecting the client**
**Status:** fixed
**Milestone:** 5.17.10
**Created:** Mon Sep 25, 2017 07:08 AM UTC by Hung Nguyen
**Last Updated:** Sat Sep 30, 2017 01:41 PM UTC
**Owner:** Hung Nguyen
Steps to reproduce:
1. OmAdminOwnerInitialize (ROF=False)
1. OmAdminOwnerSet
1. Kill osafimmnd and wait for it to finishing syncing
1. OmAdminOperationInvoke returns ERR_BAD_HANDLE, it should return OK.
-
In admin_op_invoke_common(), admo id is obtained before checking for the client
being stale.
~~~
adminOwnerId = ao_node->mAdminOwnerId;
...
if (cl_node->stale) {
... // If stale, ao_node->mAdminOwnerId my be upadted with new value here
}
~~~
In case of the client being stale, new admo id will be retrieved from the
server and set to ao_node->mAdminOwnerId.
adminOwnerId should be assigned after resurrecting.
---
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] #2591 imm: Admo id is not updated after resurrecting the client
- **Comment**:
develop (5.17.10) [code:704bdb]
~~~
commit 704bdbcfb4fe3f400fb731d99fdfb3dc567de626
Author: Hung Nguyen
Date: Sat Sep 30 20:31:05 2017 +0700
imm: Update admo id after resurrecting [#2591]
Update admo id after resurrecting.
~~~
release [code:597b98]
~~~
commit 597b98026c1101e675230ee1914f18f451745396
Author: Hung Nguyen
Date: Sat Sep 30 20:31:05 2017 +0700
imm: Update admo id after resurrecting [#2591]
Update admo id after resurrecting.
~~~
---
** [tickets:#2591] imm: Admo id is not updated after resurrecting the client**
**Status:** review
**Milestone:** 5.17.10
**Created:** Mon Sep 25, 2017 07:08 AM UTC by Hung Nguyen
**Last Updated:** Tue Sep 26, 2017 03:08 AM UTC
**Owner:** Hung Nguyen
Steps to reproduce:
1. OmAdminOwnerInitialize (ROF=False)
1. OmAdminOwnerSet
1. Kill osafimmnd and wait for it to finishing syncing
1. OmAdminOperationInvoke returns ERR_BAD_HANDLE, it should return OK.
-
In admin_op_invoke_common(), admo id is obtained before checking for the client
being stale.
~~~
adminOwnerId = ao_node->mAdminOwnerId;
...
if (cl_node->stale) {
... // If stale, ao_node->mAdminOwnerId my be upadted with new value here
}
~~~
In case of the client being stale, new admo id will be retrieved from the
server and set to ao_node->mAdminOwnerId.
adminOwnerId should be assigned after resurrecting.
---
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] #2591 imm: Admo id is not updated after resurrecting the client
- **status**: accepted --> review
---
** [tickets:#2591] imm: Admo id is not updated after resurrecting the client**
**Status:** review
**Milestone:** 5.17.10
**Created:** Mon Sep 25, 2017 07:08 AM UTC by Hung Nguyen
**Last Updated:** Mon Sep 25, 2017 07:08 AM UTC
**Owner:** Hung Nguyen
Steps to reproduce:
1. OmAdminOwnerInitialize (ROF=False)
1. OmAdminOwnerSet
1. Kill osafimmnd and wait for it to finishing syncing
1. OmAdminOperationInvoke returns ERR_BAD_HANDLE, it should return OK.
-
In admin_op_invoke_common(), admo id is obtained before checking for the client
being stale.
~~~
adminOwnerId = ao_node->mAdminOwnerId;
...
if (cl_node->stale) {
... // If stale, ao_node->mAdminOwnerId my be upadted with new value here
}
~~~
In case of the client being stale, new admo id will be retrieved from the
server and set to ao_node->mAdminOwnerId.
adminOwnerId should be assigned after resurrecting.
---
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] #2591 imm: Admo id is not updated after resurrecting the client
---
** [tickets:#2591] imm: Admo id is not updated after resurrecting the client**
**Status:** accepted
**Milestone:** 5.17.10
**Created:** Mon Sep 25, 2017 07:08 AM UTC by Hung Nguyen
**Last Updated:** Mon Sep 25, 2017 07:08 AM UTC
**Owner:** Hung Nguyen
Steps to reproduce:
1. OmAdminOwnerInitialize (ROF=False)
1. OmAdminOwnerSet
1. Kill osafimmnd and wait for it to finishing syncing
1. OmAdminOperationInvoke returns ERR_BAD_HANDLE, it should return OK.
-
In admin_op_invoke_common(), admo id is obtained before checking for the client
being stale.
~~~
adminOwnerId = ao_node->mAdminOwnerId;
...
if (cl_node->stale) {
... // If stale, ao_node->mAdminOwnerId my be upadted with new value here
}
~~~
In case of the client being stale, new admo id will be retrieved from the
server and set to ao_node->mAdminOwnerId.
adminOwnerId should be assigned after resurrecting.
---
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] #2576 imm: Admin owner name is overwritten when committing modification
- **status**: accepted --> fixed
- **Comment**:
develop (5.17.10) [code:61e9fd]
~~~
commit 61e9fd96d66786cfb6e607a2594fc168c799a95d
Author: Hung Nguyen
Date: Thu Sep 14 10:20:30 2017 +0700
imm: Don't allow setting new admo name when object is in a critical CCB
[#2576]
When object is in a critical CCB and has no admo,
ERR_TRY_AGAIN will be returned if setting a new admo name to the object.
If setting a different admo name, ERR_EXIST will be returned as stated in
IMM specification.
~~~
release [code:41b573]
~~~
commit 41b57348300cbad799e8f449568dd300b3d8f655
Author: Hung Nguyen
Date: Thu Sep 14 10:20:30 2017 +0700
imm: Don't allow setting new admo name when object is in a critical CCB
[#2576]
When object is in a critical CCB and has no admo,
ERR_TRY_AGAIN will be returned if setting a new admo name to the object.
If setting a different admo name, ERR_EXIST will be returned as stated in
IMM specification.
~~~
---
** [tickets:#2576] imm: Admin owner name is overwritten when committing
modification**
**Status:** fixed
**Milestone:** 5.17.10
**Created:** Fri Sep 08, 2017 07:12 AM UTC by Hung Nguyen
**Last Updated:** Mon Sep 11, 2017 09:49 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[reproduce_n_logs.tgz](https://sourceforge.net/p/opensaf/tickets/2576/attachment/reproduce_n_logs.tgz)
(14.7 kB; application/x-compressed)
Steps to reproduce:
* Create an object to test. The xml file can be found attached in this ticket.
~~~
# immcfg -f /hostfs/TestClass_simple.xml
# immcfg -c Test test=1
~~~
* Delay the CcbCompleted callback of pbe to simulate IO/disk latency.
The gdb file can be found in attachments of this ticket.
~~~
# gdb --command=pbe_delay_committing.gdb /usr/local/lib/opensaf/osafimmpbed
$(pidof osafimmpbed)
~~~
* Run the test. The source code of the test can be found attached to this
ticket.
~~~
# ccb_modify_test
~~~
* Now check the admo name of the object, it will show **"admo1"** (it should be
**"admo2"**).
~~~
# immlist -a SaImmAttrAdminOwnerName test=1
SaImmAttrAdminOwnerName=admo1
~~~
-
Here's what the test does:
* Create a CCB and modify **"test=1"**. The admo name is **"admo1"**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo1", SA_TRUE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, {"test=1"}, SA_IMM_ONE);
saImmOmCcbInitialize(owner_handle, 0, &ccb_handle);
saImmOmCcbObjectModify_2(ccb_handle, "test=1", attr_mods);
~~~
* saImmOmCcbApply returns ERR_TIMEOUT as we delay PBE.
~~~cpp
saImmOmCcbApply(ccb_handle);
~~~
* Finalize the handle
~~~cpp
saImmOmFinalize(handle);
~~~
* Initialize new admo and set to the same object **"test=1"**. **ROF** is
**FALSE**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo2", SA_FALSE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, object_names, SA_IMM_ONE);
saImmOmFinalize(handle);
~~~
* At this time the admo that is set to the object is **"admo2"**.
* But when the ccb is committed, the admo name (**"admo2"**) is overwritten by
the admo name in the after image (**"admo1"**).
~~~
11:39:49 SC-1 osafimmnd[214]: NO Ccb 3 COMMITTED ()
~~~
~~~cpp
11:39:49.132941 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6096] >> ccbCommit
11:39:49.132946 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6103] T5 Commit
CCB 3
11:39:49.132950 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6109] T5 Ccb 3
comitted by PBE now in state:9
11:39:49.132954 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6111] T5 Comitting
Ccb 3 in IMMND
11:39:49.132959 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5934] >>
commitModify
11:39:49.132964 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5935] T5 COMMITING
MODIFY of test=1
11:39:49.132989 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6027] <<
commitModify
11:39:49.133893 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6194] NO Ccb 3
COMMITTED ()
11:39:49.133929 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:] << ccbCommit
for (oavi = afterImage->mAttrValueMap.begin();
oavi != afterImage->mAttrValueMap.end(); ++oavi) {
AttrMap::iterator i4 = classInfo->mAttrMap.find(oavi->first);
osafassert(i4 != classInfo->mAttrMap.end());
osafassert(i4->second->mFlags & SA_IMM_ATTR_CONFIG);
beforeImage->mAttrValueMap[oavi->first] = oavi->second;
if (oavi->first == std::string(SA_IMM_ATTR_ADMIN_OWNER_NAME)) {
beforeImage->mAdminOwnerAttrVal = oavi->second;
}
}
~~~
---
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/t
[tickets] [opensaf:tickets] #2576 imm: Admin owner name is overwritten when committing modification
- **status**: review --> accepted
---
** [tickets:#2576] imm: Admin owner name is overwritten when committing
modification**
**Status:** accepted
**Milestone:** 5.17.10
**Created:** Fri Sep 08, 2017 07:12 AM UTC by Hung Nguyen
**Last Updated:** Mon Sep 11, 2017 07:15 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[reproduce_n_logs.tgz](https://sourceforge.net/p/opensaf/tickets/2576/attachment/reproduce_n_logs.tgz)
(14.7 kB; application/x-compressed)
Steps to reproduce:
* Create an object to test. The xml file can be found attached in this ticket.
~~~
# immcfg -f /hostfs/TestClass_simple.xml
# immcfg -c Test test=1
~~~
* Delay the CcbCompleted callback of pbe to simulate IO/disk latency.
The gdb file can be found in attachments of this ticket.
~~~
# gdb --command=pbe_delay_committing.gdb /usr/local/lib/opensaf/osafimmpbed
$(pidof osafimmpbed)
~~~
* Run the test. The source code of the test can be found attached to this
ticket.
~~~
# ccb_modify_test
~~~
* Now check the admo name of the object, it will show **"admo1"** (it should be
**"admo2"**).
~~~
# immlist -a SaImmAttrAdminOwnerName test=1
SaImmAttrAdminOwnerName=admo1
~~~
-
Here's what the test does:
* Create a CCB and modify **"test=1"**. The admo name is **"admo1"**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo1", SA_TRUE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, {"test=1"}, SA_IMM_ONE);
saImmOmCcbInitialize(owner_handle, 0, &ccb_handle);
saImmOmCcbObjectModify_2(ccb_handle, "test=1", attr_mods);
~~~
* saImmOmCcbApply returns ERR_TIMEOUT as we delay PBE.
~~~cpp
saImmOmCcbApply(ccb_handle);
~~~
* Finalize the handle
~~~cpp
saImmOmFinalize(handle);
~~~
* Initialize new admo and set to the same object **"test=1"**. **ROF** is
**FALSE**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo2", SA_FALSE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, object_names, SA_IMM_ONE);
saImmOmFinalize(handle);
~~~
* At this time the admo that is set to the object is **"admo2"**.
* But when the ccb is committed, the admo name (**"admo2"**) is overwritten by
the admo name in the after image (**"admo1"**).
~~~
11:39:49 SC-1 osafimmnd[214]: NO Ccb 3 COMMITTED ()
~~~
~~~cpp
11:39:49.132941 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6096] >> ccbCommit
11:39:49.132946 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6103] T5 Commit
CCB 3
11:39:49.132950 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6109] T5 Ccb 3
comitted by PBE now in state:9
11:39:49.132954 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6111] T5 Comitting
Ccb 3 in IMMND
11:39:49.132959 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5934] >>
commitModify
11:39:49.132964 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5935] T5 COMMITING
MODIFY of test=1
11:39:49.132989 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6027] <<
commitModify
11:39:49.133893 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6194] NO Ccb 3
COMMITTED ()
11:39:49.133929 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:] << ccbCommit
for (oavi = afterImage->mAttrValueMap.begin();
oavi != afterImage->mAttrValueMap.end(); ++oavi) {
AttrMap::iterator i4 = classInfo->mAttrMap.find(oavi->first);
osafassert(i4 != classInfo->mAttrMap.end());
osafassert(i4->second->mFlags & SA_IMM_ATTR_CONFIG);
beforeImage->mAttrValueMap[oavi->first] = oavi->second;
if (oavi->first == std::string(SA_IMM_ATTR_ADMIN_OWNER_NAME)) {
beforeImage->mAdminOwnerAttrVal = oavi->second;
}
}
~~~
---
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] #2576 imm: Admin owner name is overwritten when committing modification
- **status**: accepted --> review
---
** [tickets:#2576] imm: Admin owner name is overwritten when committing
modification**
**Status:** review
**Milestone:** 5.17.10
**Created:** Fri Sep 08, 2017 07:12 AM UTC by Hung Nguyen
**Last Updated:** Fri Sep 08, 2017 07:12 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[reproduce_n_logs.tgz](https://sourceforge.net/p/opensaf/tickets/2576/attachment/reproduce_n_logs.tgz)
(14.7 kB; application/x-compressed)
Steps to reproduce:
* Create an object to test. The xml file can be found attached in this ticket.
~~~
# immcfg -f /hostfs/TestClass_simple.xml
# immcfg -c Test test=1
~~~
* Delay the CcbCompleted callback of pbe to simulate IO/disk latency.
The gdb file can be found in attachments of this ticket.
~~~
# gdb --command=pbe_delay_committing.gdb /usr/local/lib/opensaf/osafimmpbed
$(pidof osafimmpbed)
~~~
* Run the test. The source code of the test can be found attached to this
ticket.
~~~
# ccb_modify_test
~~~
* Now check the admo name of the object, it will show **"admo1"** (it should be
**"admo2"**).
~~~
# immlist -a SaImmAttrAdminOwnerName test=1
SaImmAttrAdminOwnerName=admo1
~~~
-
Here's what the test does:
* Create a CCB and modify **"test=1"**. The admo name is **"admo1"**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo1", SA_TRUE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, {"test=1"}, SA_IMM_ONE);
saImmOmCcbInitialize(owner_handle, 0, &ccb_handle);
saImmOmCcbObjectModify_2(ccb_handle, "test=1", attr_mods);
~~~
* saImmOmCcbApply returns ERR_TIMEOUT as we delay PBE.
~~~cpp
saImmOmCcbApply(ccb_handle);
~~~
* Finalize the handle
~~~cpp
saImmOmFinalize(handle);
~~~
* Initialize new admo and set to the same object **"test=1"**. **ROF** is
**FALSE**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo2", SA_FALSE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, object_names, SA_IMM_ONE);
saImmOmFinalize(handle);
~~~
* At this time the admo that is set to the object is **"admo2"**.
* But when the ccb is committed, the admo name (**"admo2"**) is overwritten by
the admo name in the after image (**"admo1"**).
~~~
11:39:49 SC-1 osafimmnd[214]: NO Ccb 3 COMMITTED ()
~~~
~~~cpp
11:39:49.132941 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6096] >> ccbCommit
11:39:49.132946 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6103] T5 Commit
CCB 3
11:39:49.132950 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6109] T5 Ccb 3
comitted by PBE now in state:9
11:39:49.132954 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6111] T5 Comitting
Ccb 3 in IMMND
11:39:49.132959 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5934] >>
commitModify
11:39:49.132964 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5935] T5 COMMITING
MODIFY of test=1
11:39:49.132989 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6027] <<
commitModify
11:39:49.133893 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6194] NO Ccb 3
COMMITTED ()
11:39:49.133929 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:] << ccbCommit
for (oavi = afterImage->mAttrValueMap.begin();
oavi != afterImage->mAttrValueMap.end(); ++oavi) {
AttrMap::iterator i4 = classInfo->mAttrMap.find(oavi->first);
osafassert(i4 != classInfo->mAttrMap.end());
osafassert(i4->second->mFlags & SA_IMM_ATTR_CONFIG);
beforeImage->mAttrValueMap[oavi->first] = oavi->second;
if (oavi->first == std::string(SA_IMM_ATTR_ADMIN_OWNER_NAME)) {
beforeImage->mAdminOwnerAttrVal = oavi->second;
}
}
~~~
---
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] #2571 imm: OiAdminOperationResult doesn't check for validity of input invocation
- **status**: review --> fixed - **Comment**: develop (5.17.10) [code:10a835] ~~~ commit 10a83558372bbeae8b2d09e0fefd55cbc11dbd5d Author: Hung Nguyen Date: Wed Sep 6 17:10:47 2017 +0700 imm: Validate input invocation for saImmOiAdminOperationResult [#2571] Add new set to IMMA_CLIENT_NODE to store the invocations. The invocation is added to the set when dispatching the callback and is removed from the set in saImmOiAdminOperationResult. ~~~ release [code:31ac0f] ~~~ commit 31ac0f2febebb8212286baba298cad6d2539a5e5 Author: Hung Nguyen Date: Wed Sep 6 17:10:47 2017 +0700 imm: Validate input invocation for saImmOiAdminOperationResult [#2571] Add new set to IMMA_CLIENT_NODE to store the invocations. The invocation is added to the set when dispatching the callback and is removed from the set in saImmOiAdminOperationResult. ~~~ --- ** [tickets:#2571] imm: OiAdminOperationResult doesn't check for validity of input invocation** **Status:** fixed **Milestone:** 5.17.10 **Created:** Tue Sep 05, 2017 11:53 AM UTC by Hung Nguyen **Last Updated:** Wed Sep 06, 2017 11:43 AM UTC **Owner:** Hung Nguyen When using OiAdminOperationResult() with invalid value of invocation, it returns OK. saImmOiAdminOperationResult(immOiHandle, -1, SA_AIS_OK); It should return ERR_INVALID_PARAM in this case. --- 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] #2576 imm: Admin owner name is overwritten when committing modification
---
** [tickets:#2576] imm: Admin owner name is overwritten when committing
modification**
**Status:** accepted
**Milestone:** 5.17.10
**Created:** Fri Sep 08, 2017 07:12 AM UTC by Hung Nguyen
**Last Updated:** Fri Sep 08, 2017 07:12 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[reproduce_n_logs.tgz](https://sourceforge.net/p/opensaf/tickets/2576/attachment/reproduce_n_logs.tgz)
(14.7 kB; application/x-compressed)
Steps to reproduce:
* Create an object to test. The xml file can be found attached in this ticket.
~~~
# immcfg -f /hostfs/TestClass_simple.xml
# immcfg -c Test test=1
~~~
* Delay the CcbCompleted callback of pbe to simulate IO/disk latency.
The gdb file can be found in attachments of this ticket.
~~~
# gdb --command=pbe_delay_committing.gdb /usr/local/lib/opensaf/osafimmpbed
$(pidof osafimmpbed)
~~~
* Run the test. The source code of the test can be found attached to this
ticket.
~~~
# ccb_modify_test
~~~
* Now check the admo name of the object, it will show **"admo1"** (it should be
**"admo2"**).
~~~
# immlist -a SaImmAttrAdminOwnerName test=1
SaImmAttrAdminOwnerName=admo1
~~~
-
Here's what the test does:
* Create a CCB and modify **"test=1"**. The admo name is **"admo1"**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo1", SA_TRUE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, {"test=1"}, SA_IMM_ONE);
saImmOmCcbInitialize(owner_handle, 0, &ccb_handle);
saImmOmCcbObjectModify_2(ccb_handle, "test=1", attr_mods);
~~~
* saImmOmCcbApply returns ERR_TIMEOUT as we delay PBE.
~~~cpp
saImmOmCcbApply(ccb_handle);
~~~
* Finalize the handle
~~~cpp
saImmOmFinalize(handle);
~~~
* Initialize new admo and set to the same object **"test=1"**. **ROF** is
**FALSE**.
~~~cpp
saImmOmInitialize(&handle, NULL, &version);
saImmOmAdminOwnerInitialize(handle, "admo2", SA_FALSE, &owner_handle);
saImmOmAdminOwnerSet(owner_handle, object_names, SA_IMM_ONE);
saImmOmFinalize(handle);
~~~
* At this time the admo that is set to the object is **"admo2"**.
* But when the ccb is committed, the admo name (**"admo2"**) is overwritten by
the admo name in the after image (**"admo1"**).
~~~
11:39:49 SC-1 osafimmnd[214]: NO Ccb 3 COMMITTED ()
~~~
~~~cpp
11:39:49.132941 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6096] >> ccbCommit
11:39:49.132946 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6103] T5 Commit
CCB 3
11:39:49.132950 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6109] T5 Ccb 3
comitted by PBE now in state:9
11:39:49.132954 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6111] T5 Comitting
Ccb 3 in IMMND
11:39:49.132959 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5934] >>
commitModify
11:39:49.132964 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:5935] T5 COMMITING
MODIFY of test=1
11:39:49.132989 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6027] <<
commitModify
11:39:49.133893 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:6194] NO Ccb 3
COMMITTED ()
11:39:49.133929 osafimmnd [214:214:src/imm/immnd/ImmModel.cc:] << ccbCommit
for (oavi = afterImage->mAttrValueMap.begin();
oavi != afterImage->mAttrValueMap.end(); ++oavi) {
AttrMap::iterator i4 = classInfo->mAttrMap.find(oavi->first);
osafassert(i4 != classInfo->mAttrMap.end());
osafassert(i4->second->mFlags & SA_IMM_ATTR_CONFIG);
beforeImage->mAttrValueMap[oavi->first] = oavi->second;
if (oavi->first == std::string(SA_IMM_ATTR_ADMIN_OWNER_NAME)) {
beforeImage->mAdminOwnerAttrVal = oavi->second;
}
}
~~~
---
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] #2573 imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH
- **status**: review --> fixed - **Comment**: develop (5.17.10) [code:455781] ~~~ commit 4557812c01ecea474b8f9d0fece36dca6976537a Author: Hung Nguyen Date: Wed Sep 6 18:30:54 2017 +0700 imm: Regenerate PBE on SQLITE_CORRUPT and SQLITE_MISMATCH [#2573] Regenerate PBE on SQLITE_CORRUPT and SQLITE_MISMATCH. ~~~ release [code:0b5653] ~~~ commit 0b56535e10d48db45c337f3afaae4e7e17bec5c3 Author: Hung Nguyen Date: Wed Sep 6 18:30:54 2017 +0700 imm: Regenerate PBE on SQLITE_CORRUPT and SQLITE_MISMATCH [#2573] Regenerate PBE on SQLITE_CORRUPT and SQLITE_MISMATCH. ~~~ --- ** [tickets:#2573] imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH** **Status:** fixed **Milestone:** 5.17.10 **Created:** Wed Sep 06, 2017 11:04 AM UTC by Hung Nguyen **Last Updated:** Wed Sep 06, 2017 11:43 AM UTC **Owner:** Hung Nguyen PBE should regenerate the database on SQLITE_CORRUPT and SQLITE_MISMATCH instead of re-attaching to the corrupt database. ~~~ 04:25:53 PL-4 osafimmpbed: ER SQL object statement for table 'SaAmfCompCsType' failed with error code: 11 04:25:53 PL-4 osafimmpbed: ER objectToPBE failed in sqlite_prepare_ccb. Handle is closed - exiting 04:25:54 PL-4 osafimmpbed: IN arg[0] == '/usr/lib64/opensaf/osafimmpbed' 04:25:54 PL-4 osafimmpbed: IN arg[1] == '--recover' 04:25:54 PL-4 osafimmpbed: IN arg[2] == '--pbe' 04:25:54 PL-4 osafimmpbed: IN arg[3] == '/storage/clear/coremw/etc/imm.db' 04:25:54 PL-4 osafimmpbed: WA Journal file /storage/clear/coremw/etc/imm.db-journal of non zero size exists at start of PBE/immdump => sqlite recovery 04:25:54 PL-4 osafimmpbed: NO Successfully opened pre-existing sqlite pbe file /storage/clear/coremw/etc/imm.db 04:25:54 PL-4 osafimmpbed: IN saImmRepositoryInit: SA_IMM_KEEP_REPOSITORY - attaching to repository ~~~ --- 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] #2571 imm: OiAdminOperationResult doesn't check for validity of input invocation
- **status**: accepted --> review --- ** [tickets:#2571] imm: OiAdminOperationResult doesn't check for validity of input invocation** **Status:** review **Milestone:** 5.17.10 **Created:** Tue Sep 05, 2017 11:53 AM UTC by Hung Nguyen **Last Updated:** Tue Sep 05, 2017 11:53 AM UTC **Owner:** Hung Nguyen When using OiAdminOperationResult() with invalid value of invocation, it returns OK. saImmOiAdminOperationResult(immOiHandle, -1, SA_AIS_OK); It should return ERR_INVALID_PARAM in this case. --- 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] #2573 imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH
- **status**: accepted --> review --- ** [tickets:#2573] imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Sep 06, 2017 11:04 AM UTC by Hung Nguyen **Last Updated:** Wed Sep 06, 2017 11:04 AM UTC **Owner:** Hung Nguyen PBE should regenerate the database on SQLITE_CORRUPT and SQLITE_MISMATCH instead of re-attaching to the corrupt database. ~~~ 04:25:53 PL-4 osafimmpbed: ER SQL object statement for table 'SaAmfCompCsType' failed with error code: 11 04:25:53 PL-4 osafimmpbed: ER objectToPBE failed in sqlite_prepare_ccb. Handle is closed - exiting 04:25:54 PL-4 osafimmpbed: IN arg[0] == '/usr/lib64/opensaf/osafimmpbed' 04:25:54 PL-4 osafimmpbed: IN arg[1] == '--recover' 04:25:54 PL-4 osafimmpbed: IN arg[2] == '--pbe' 04:25:54 PL-4 osafimmpbed: IN arg[3] == '/storage/clear/coremw/etc/imm.db' 04:25:54 PL-4 osafimmpbed: WA Journal file /storage/clear/coremw/etc/imm.db-journal of non zero size exists at start of PBE/immdump => sqlite recovery 04:25:54 PL-4 osafimmpbed: NO Successfully opened pre-existing sqlite pbe file /storage/clear/coremw/etc/imm.db 04:25:54 PL-4 osafimmpbed: IN saImmRepositoryInit: SA_IMM_KEEP_REPOSITORY - attaching to repository ~~~ --- 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] #2573 imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH
--- ** [tickets:#2573] imm: PBE is not regenerated on SQLITE_CORRUPT and SQLITE_MISMATCH** **Status:** accepted **Milestone:** 5.17.10 **Created:** Wed Sep 06, 2017 11:04 AM UTC by Hung Nguyen **Last Updated:** Wed Sep 06, 2017 11:04 AM UTC **Owner:** Hung Nguyen PBE should regenerate the database on SQLITE_CORRUPT and SQLITE_MISMATCH instead of re-attaching to the corrupt database. ~~~ 04:25:53 PL-4 osafimmpbed: ER SQL object statement for table 'SaAmfCompCsType' failed with error code: 11 04:25:53 PL-4 osafimmpbed: ER objectToPBE failed in sqlite_prepare_ccb. Handle is closed - exiting 04:25:54 PL-4 osafimmpbed: IN arg[0] == '/usr/lib64/opensaf/osafimmpbed' 04:25:54 PL-4 osafimmpbed: IN arg[1] == '--recover' 04:25:54 PL-4 osafimmpbed: IN arg[2] == '--pbe' 04:25:54 PL-4 osafimmpbed: IN arg[3] == '/storage/clear/coremw/etc/imm.db' 04:25:54 PL-4 osafimmpbed: WA Journal file /storage/clear/coremw/etc/imm.db-journal of non zero size exists at start of PBE/immdump => sqlite recovery 04:25:54 PL-4 osafimmpbed: NO Successfully opened pre-existing sqlite pbe file /storage/clear/coremw/etc/imm.db 04:25:54 PL-4 osafimmpbed: IN saImmRepositoryInit: SA_IMM_KEEP_REPOSITORY - attaching to repository ~~~ --- 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] #2571 imm: OiAdminOperationResult doesn't check for validity of input invocation
--- ** [tickets:#2571] imm: OiAdminOperationResult doesn't check for validity of input invocation** **Status:** accepted **Milestone:** 5.17.10 **Created:** Tue Sep 05, 2017 11:53 AM UTC by Hung Nguyen **Last Updated:** Tue Sep 05, 2017 11:53 AM UTC **Owner:** Hung Nguyen When using OiAdminOperationResult() with invalid value of invocation, it returns OK. saImmOiAdminOperationResult(immOiHandle, -1, SA_AIS_OK); It should return ERR_INVALID_PARAM in this case. --- 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] Re: #2532 mds: TCP SVC_UP event is not received after subscribing
Hi, In logs_n_traces.tgz file, I already included: * IMMND trace (osafimmnd) * IMMA trace (imma.trace) * MDS log with MDS_LOG_LEVEL=5 for osafimmnd and immomtest (mds.log) * MDS log with MDS_LOG_LEVEL=5 for immomtest (mds.log) Just to be clear, are you requesting those traces for TIPC? Thanks, --- ** [tickets:#2532] mds: TCP SVC_UP event is not received after subscribing** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 05:59 AM UTC by Hung Nguyen **Last Updated:** Mon Aug 28, 2017 03:27 AM UTC **Owner:** nobody **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2532/attachment/logs_n_traces.tgz) (1.5 MB; application/x-compressed) MDS is successfully installed on IMMA and IMMA subscribed to IMMD successfully. IMMND also received IMMA SVC_UP event but IMMA didn't receive SVC_UP event for IMMND. ~~~ <142>1 2017-07-20T13:00:36.072773+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14043"] MCM:API: svc_id = IMMA_OM(26) on VDEST id = 65535, SVC_PVT_VER = 0 Install Successfull > ... <142>1 2017-07-20T13:00:36.073091+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14074"] MCM:API: svc_subscribe :svc_id = IMMA_OM(26) on VDEST id = 65535 Subscription to svc_id = IMMND(25) Successful > ... <142>1 2017-07-20T13:00:36.073904+02:00 PL-4 osafimmnd 177 mds.log [meta sequenceId="96185"] MCM:API: svc_up : svc_id = IMMND(25) on DEST id = 65535 got UP for svc_id = IMMA_OM(26) on Adest = , rem_svc_pvt_ver=0, rem_svc_archword=10 ~~~ IMMA waited for the SVC_UP event for 30 sec but didn't receive anything. ~~~ Jul 20 13:00:36.071465 imma [278:278:src/imm/agent/imma_init.cc:0263] >> imma_startup Jul 20 13:00:36.071474 imma [278:278:src/imm/agent/imma_init.cc:0273] TR use count 0 Jul 20 13:00:36.071484 imma [278:278:src/base/ncs_main_pub.c:0220] TR NCS:PROCESS_ID=278 Jul 20 13:00:36.071494 imma [278:278:src/base/sysf_def.c:0089] TR INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071584 imma [278:278:src/base/sysf_def.c:0124] TR DONE INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071832 imma [278:278:src/base/ncs_main_pub.c:0757] TR NCS:NODE_ID=0x0002040F Jul 20 13:00:36.072329 imma [278:278:src/mbc/mbcsv_dl_api.c:0059] >> mbcsv_lib_req Jul 20 13:00:36.072350 imma [278:278:src/mbc/mbcsv_dl_api.c:0096] >> mbcsv_lib_init Jul 20 13:00:36.072378 imma [278:278:src/mbc/mbcsv_mbx.c:0174] >> mbcsv_initialize_mbx_list Jul 20 13:00:36.072389 imma [278:278:src/mbc/mbcsv_mbx.c:0189] << mbcsv_initialize_mbx_list Jul 20 13:00:36.072399 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0158] >> mbcsv_initialize_peer_list Jul 20 13:00:36.072409 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0173] << mbcsv_initialize_peer_list Jul 20 13:00:36.072419 imma [278:278:src/mbc/mbcsv_dl_api.c:0075] << mbcsv_lib_req Jul 20 13:00:36.072440 imma [278:278:src/base/ncs_main_pub.c:0389] TR MBCSV:MBCA:ON Jul 20 13:00:36.073104 imma [278:278:src/imm/agent/imma_init.cc:0063] >> imma_sync_with_immnd Jul 20 13:00:36.073114 imma [278:278:src/imm/agent/imma_init.cc:0071] TR Blocking first client Jul 20 13:01:06.102156 imma [278:278:src/imm/agent/imma_init.cc:0081] TR Blocking wait released Jul 20 13:01:06.102375 imma [278:278:src/imm/agent/imma_init.cc:0091] << imma_sync_with_immnd Jul 20 13:01:06.102413 imma [278:278:src/imm/agent/imma_init.cc:0179] TR Client agent successfully initialized Jul 20 13:01:06.102427 imma [278:278:src/imm/agent/imma_init.cc:0296] << imma_startup: use count 1 ~~~ Attached is traces and 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
[tickets] [opensaf:tickets] Re: #2532 mds: TCP SVC_UP event is not received after subscribing
Hi, It's very hard to reproduce the issue. Only immomtest was run when the problem occured. The cluster was also in stable state, all nodes was not rebooting or starting. We don't run tests with TIPC, so I don't know if this also happens with TIPC. The cluster is lxc (Linux Containers). Thanks, --- ** [tickets:#2532] mds: TCP SVC_UP event is not received after subscribing** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 05:59 AM UTC by Hung Nguyen **Last Updated:** Thu Aug 24, 2017 10:29 AM UTC **Owner:** nobody **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2532/attachment/logs_n_traces.tgz) (1.5 MB; application/x-compressed) MDS is successfully installed on IMMA and IMMA subscribed to IMMD successfully. IMMND also received IMMA SVC_UP event but IMMA didn't receive SVC_UP event for IMMND. ~~~ <142>1 2017-07-20T13:00:36.072773+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14043"] MCM:API: svc_id = IMMA_OM(26) on VDEST id = 65535, SVC_PVT_VER = 0 Install Successfull > ... <142>1 2017-07-20T13:00:36.073091+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14074"] MCM:API: svc_subscribe :svc_id = IMMA_OM(26) on VDEST id = 65535 Subscription to svc_id = IMMND(25) Successful > ... <142>1 2017-07-20T13:00:36.073904+02:00 PL-4 osafimmnd 177 mds.log [meta sequenceId="96185"] MCM:API: svc_up : svc_id = IMMND(25) on DEST id = 65535 got UP for svc_id = IMMA_OM(26) on Adest = , rem_svc_pvt_ver=0, rem_svc_archword=10 ~~~ IMMA waited for the SVC_UP event for 30 sec but didn't receive anything. ~~~ Jul 20 13:00:36.071465 imma [278:278:src/imm/agent/imma_init.cc:0263] >> imma_startup Jul 20 13:00:36.071474 imma [278:278:src/imm/agent/imma_init.cc:0273] TR use count 0 Jul 20 13:00:36.071484 imma [278:278:src/base/ncs_main_pub.c:0220] TR NCS:PROCESS_ID=278 Jul 20 13:00:36.071494 imma [278:278:src/base/sysf_def.c:0089] TR INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071584 imma [278:278:src/base/sysf_def.c:0124] TR DONE INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071832 imma [278:278:src/base/ncs_main_pub.c:0757] TR NCS:NODE_ID=0x0002040F Jul 20 13:00:36.072329 imma [278:278:src/mbc/mbcsv_dl_api.c:0059] >> mbcsv_lib_req Jul 20 13:00:36.072350 imma [278:278:src/mbc/mbcsv_dl_api.c:0096] >> mbcsv_lib_init Jul 20 13:00:36.072378 imma [278:278:src/mbc/mbcsv_mbx.c:0174] >> mbcsv_initialize_mbx_list Jul 20 13:00:36.072389 imma [278:278:src/mbc/mbcsv_mbx.c:0189] << mbcsv_initialize_mbx_list Jul 20 13:00:36.072399 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0158] >> mbcsv_initialize_peer_list Jul 20 13:00:36.072409 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0173] << mbcsv_initialize_peer_list Jul 20 13:00:36.072419 imma [278:278:src/mbc/mbcsv_dl_api.c:0075] << mbcsv_lib_req Jul 20 13:00:36.072440 imma [278:278:src/base/ncs_main_pub.c:0389] TR MBCSV:MBCA:ON Jul 20 13:00:36.073104 imma [278:278:src/imm/agent/imma_init.cc:0063] >> imma_sync_with_immnd Jul 20 13:00:36.073114 imma [278:278:src/imm/agent/imma_init.cc:0071] TR Blocking first client Jul 20 13:01:06.102156 imma [278:278:src/imm/agent/imma_init.cc:0081] TR Blocking wait released Jul 20 13:01:06.102375 imma [278:278:src/imm/agent/imma_init.cc:0091] << imma_sync_with_immnd Jul 20 13:01:06.102413 imma [278:278:src/imm/agent/imma_init.cc:0179] TR Client agent successfully initialized Jul 20 13:01:06.102427 imma [278:278:src/imm/agent/imma_init.cc:0296] << imma_startup: use count 1 ~~~ Attached is traces and 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
[tickets] [opensaf:tickets] #2532 mds: SVC_UP event is not received after subscribing
--- ** [tickets:#2532] mds: SVC_UP event is not received after subscribing** **Status:** unassigned **Milestone:** 5.17.08 **Created:** Fri Jul 21, 2017 05:59 AM UTC by Hung Nguyen **Last Updated:** Fri Jul 21, 2017 05:59 AM UTC **Owner:** nobody **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2532/attachment/logs_n_traces.tgz) (1.5 MB; application/x-compressed) MDS is successfully installed on IMMA and IMMA subscribed to IMMD successfully. IMMND also received IMMA SVC_UP event but IMMA didn't receive SVC_UP event for IMMND. ~~~ <142>1 2017-07-20T13:00:36.072773+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14043"] MCM:API: svc_id = IMMA_OM(26) on VDEST id = 65535, SVC_PVT_VER = 0 Install Successfull > ... <142>1 2017-07-20T13:00:36.073091+02:00 PL-4 immomtest 278 mds.log [meta sequenceId="14074"] MCM:API: svc_subscribe :svc_id = IMMA_OM(26) on VDEST id = 65535 Subscription to svc_id = IMMND(25) Successful > ... <142>1 2017-07-20T13:00:36.073904+02:00 PL-4 osafimmnd 177 mds.log [meta sequenceId="96185"] MCM:API: svc_up : svc_id = IMMND(25) on DEST id = 65535 got UP for svc_id = IMMA_OM(26) on Adest = , rem_svc_pvt_ver=0, rem_svc_archword=10 ~~~ IMMA waited for the SVC_UP event for 30 sec but didn't receive anything. ~~~ Jul 20 13:00:36.071465 imma [278:278:src/imm/agent/imma_init.cc:0263] >> imma_startup Jul 20 13:00:36.071474 imma [278:278:src/imm/agent/imma_init.cc:0273] TR use count 0 Jul 20 13:00:36.071484 imma [278:278:src/base/ncs_main_pub.c:0220] TR NCS:PROCESS_ID=278 Jul 20 13:00:36.071494 imma [278:278:src/base/sysf_def.c:0089] TR INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071584 imma [278:278:src/base/sysf_def.c:0124] TR DONE INITIALIZING LEAP ENVIRONMENT Jul 20 13:00:36.071832 imma [278:278:src/base/ncs_main_pub.c:0757] TR NCS:NODE_ID=0x0002040F Jul 20 13:00:36.072329 imma [278:278:src/mbc/mbcsv_dl_api.c:0059] >> mbcsv_lib_req Jul 20 13:00:36.072350 imma [278:278:src/mbc/mbcsv_dl_api.c:0096] >> mbcsv_lib_init Jul 20 13:00:36.072378 imma [278:278:src/mbc/mbcsv_mbx.c:0174] >> mbcsv_initialize_mbx_list Jul 20 13:00:36.072389 imma [278:278:src/mbc/mbcsv_mbx.c:0189] << mbcsv_initialize_mbx_list Jul 20 13:00:36.072399 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0158] >> mbcsv_initialize_peer_list Jul 20 13:00:36.072409 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0173] << mbcsv_initialize_peer_list Jul 20 13:00:36.072419 imma [278:278:src/mbc/mbcsv_dl_api.c:0075] << mbcsv_lib_req Jul 20 13:00:36.072440 imma [278:278:src/base/ncs_main_pub.c:0389] TR MBCSV:MBCA:ON Jul 20 13:00:36.073104 imma [278:278:src/imm/agent/imma_init.cc:0063] >> imma_sync_with_immnd Jul 20 13:00:36.073114 imma [278:278:src/imm/agent/imma_init.cc:0071] TR Blocking first client Jul 20 13:01:06.102156 imma [278:278:src/imm/agent/imma_init.cc:0081] TR Blocking wait released Jul 20 13:01:06.102375 imma [278:278:src/imm/agent/imma_init.cc:0091] << imma_sync_with_immnd Jul 20 13:01:06.102413 imma [278:278:src/imm/agent/imma_init.cc:0179] TR Client agent successfully initialized Jul 20 13:01:06.102427 imma [278:278:src/imm/agent/imma_init.cc:0296] << imma_startup: use count 1 ~~~ Attached is traces and 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
[tickets] [opensaf:tickets] #2528 clm: CLM does not handle ERR_BAD_HANDLE from saImmOmSearchInitialize
- **status**: review --> fixed - **Comment**: develop (5.17.08) [code:74c67f] ~~~ commit 74c67fe68fc08c75e834fe2cc2153c604c9b014d Author: Zoran Milinkovic Date: Thu Jul 20 17:14:51 2017 +0700 clm: handle ERR_BAD_HANDLE for saImmOmSearchInitialize [#2528] CLM handles ERR_BAD_HANDLE for saImmOmSearchInitialize in clms_cluster_config_get. As part of this patch, handling of IMM version is improved in the same function. ~~~ release [code:4afc6d] ~~~ commit 4afc6dc5c1ee9c3b27e03155aa952c6466217468 Author: Zoran Milinkovic Date: Thu Jul 20 17:14:51 2017 +0700 clm: handle ERR_BAD_HANDLE for saImmOmSearchInitialize [#2528] CLM handles ERR_BAD_HANDLE for saImmOmSearchInitialize in clms_cluster_config_get. As part of this patch, handling of IMM version is improved in the same function. ~~~ --- ** [tickets:#2528] clm: CLM does not handle ERR_BAD_HANDLE from saImmOmSearchInitialize** **Status:** fixed **Milestone:** 5.17.08 **Created:** Fri Jul 14, 2017 12:18 PM UTC by Zoran Milinkovic **Last Updated:** Fri Jul 14, 2017 01:18 PM UTC **Owner:** Zoran Milinkovic CLM fails with ERR_BAD_HANDLE in saImmOmSearchInitialize call. CLM should reinitialize OM handle and repeat search at least once. Jul 11 21:00:40 SC-1 osafrded[5886]: NO Got peer info response from node 0x2020f with role ACTIVE Jul 11 21:00:40 SC-1 osafclmd[5976]: WA OpenSAF imm lib: Message loss detected for dest 564115135000812 service id:25 Jul 11 21:00:40 SC-1 osafimmnd[5931]: WA IMMND - Client Node Get Failed for client handle: 1357209796879 Jul 11 21:00:40 SC-1 osafclmd[5976]: WA OpenSAF imm lib: Message loss detected for dest 564115135000812 service id:25 Jul 11 21:00:40 SC-1 osafclmd[5976]: WA marking handle as exposed Jul 11 21:00:40 SC-1 osafclmd[5976]: ER No Object of SaClmNode Class was found Jul 11 21:00:40 SC-1 osafclmd[5976]: ER clms_node_create_config failed rc:9 Jul 11 21:00:40 SC-1 osafclmd[5976]: ER clms_imm_activate FAILED Jul 11 21:00:40 SC-1 osafclmd[5976]: ER initialize_for_assignment FAILED 9 --- 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] #2527 imm: PBE is not regenerated on data inconsistency with sql constraint error
- **status**: review --> fixed
- **Comment**:
develop (5.17.08) [code:04293b]
~~~
commit 04293b8abd7c98ebc984cfd7186f63f8a2937bfc
Author: Zoran Milinkovic
Date: Wed Jul 19 12:28:30 2017 +0700
imm: regenerate PBE on SQL constraint error [#2527]
PBE will be regenerated on SQL constraint error code.
~~~
release [code:c542e7]
~~~
commit c542e7b0aa4a67097e57811b8ba768eb2b7593d3
Author: Zoran Milinkovic
Date: Wed Jul 19 12:28:30 2017 +0700
imm: regenerate PBE on SQL constraint error [#2527]
PBE will be regenerated on SQL constraint error code.
~~~
---
** [tickets:#2527] imm: PBE is not regenerated on data inconsistency with sql
constraint error**
**Status:** fixed
**Milestone:** 5.17.08
**Created:** Wed Jul 12, 2017 11:48 AM UTC by Zoran Milinkovic
**Last Updated:** Wed Jul 12, 2017 12:11 PM UTC
**Owner:** Zoran Milinkovic
When PBE detects that the database is corrupted with SQL contraint error code,
PBE should regenerate the database instead of reataching to the existing
database.
PBE inconsistency was detected... PBE exit and reatached:
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[3617]: ER SQL
statement('INSERT INTO objects (obj_id, class_id, dn, last_ccb) VALUES (?, ?,
?, ?)') failed with error code: 19
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[3617]: ER objectToPBE failed
in sqlite_prepare_ccb. Handle is closed - exiting
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO Implementer locally
disconnected. Marking it as doomed 120 <1359, 2d80f> (OpenSafImmPBE)
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO Implementer
disconnected 120 <1359, 2d80f> (OpenSafImmPBE)
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmnd[1645]: WA Persistent back-end
process has apparently died.
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO STARTING PBE process.
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO
pbe-db-file-path:/cluster/storage/clear/coremw/etc/imm.db VETERAN:1 B:0
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: IN arg[0] ==
'/usr/lib64/opensaf/osafimmpbed'
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: IN arg[1] ==
'--recover'
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: IN arg[2] == '--pbe'
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: IN arg[3] ==
'/cluster/storage/clear/coremw/etc/imm.db'
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: NO Successfully
opened pre-existing sqlite pbe file /cluster/storage/clear/coremw/etc/imm.db
Jul 07 10:55:49 fi15-rc-bgf19-20170621 osafimmpbed[5629]: IN
saImmRepositoryInit: SA_IMM_KEEP_REPOSITORY - attaching to repository
PBE inconsistency detected again
Jul 07 10:55:51 fi15-rc-bgf19-20170621 osafimmpbed[5629]: ER SQL
statement('INSERT INTO objects (obj_id, class_id, dn, last_ccb) VALUES (?, ?,
?, ?)') failed with error code: 19
Jul 07 10:55:51 fi15-rc-bgf19-20170621 osafimmpbed[5629]: ER objectToPBE failed
in sqlite_prepare_ccb. Handle is closed - exiting
Jul 07 10:55:51 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO Implementer locally
disconnected. Marking it as doomed 122 <5604, 2d80f> (OpenSafImmPBE)
Jul 07 10:55:51 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO Implementer
disconnected 122 <5604, 2d80f> (OpenSafImmPBE)
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmnd[1645]: WA Persistent back-end
process has apparently died.
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO STARTING PBE process.
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmnd[1645]: NO
pbe-db-file-path:/cluster/storage/clear/coremw/etc/imm.db VETERAN:1 B:0
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: IN arg[0] ==
'/usr/lib64/opensaf/osafimmpbed'
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: IN arg[1] ==
'--recover'
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: IN arg[2] == '--pbe'
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: IN arg[3] ==
'/cluster/storage/clear/coremw/etc/imm.db'
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: NO Successfully
opened pre-existing sqlite pbe file /cluster/storage/clear/coremw/etc/imm.db
Jul 07 10:55:52 fi15-rc-bgf19-20170621 osafimmpbed[6392]: IN
saImmRepositoryInit: SA_IMM_KEEP_REPOSITORY - attaching to repository
and the same situation was repeated 5 times until PBE was regenerated.
---
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.s
[tickets] [opensaf:tickets] #2512 clmtest: test case 7 7 return failed when new node is added to test environment
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:7193ab] ~~~ commit 7193ab9d6261f13efe5ce173f3b9bee248401ef3 Author: Hoang Vo Date: Wed Jun 28 13:43:48 2017 +0700 clmtest: update non-member node_id for new test environment [#2512] clmtest 7 7 check saClmClusterNodeGet with non-member node, previously designed as 0x2060F. change test node_id to 0x2990F to avoid future conflict when test environment is upgraded. ~~~ 5.17.06 (release) [code:432e64] ~~~ commit 432e64ff4bbc4bd1c7c5c3c2e3cdfbe02576cb98 Author: Hoang Vo Date: Wed Jun 28 13:43:48 2017 +0700 clmtest: update non-member node_id for new test environment [#2512] clmtest 7 7 check saClmClusterNodeGet with non-member node, previously designed as 0x2060F. change test node_id to 0x2990F to avoid future conflict when test environment is upgraded. ~~~ --- ** [tickets:#2512] clmtest: test case 7 7 return failed when new node is added to test environment** **Status:** fixed **Milestone:** 5.17.06 **Created:** Tue Jun 27, 2017 09:22 AM UTC by Vo Minh Hoang **Last Updated:** Tue Jun 27, 2017 09:39 AM UTC **Owner:** Vo Minh Hoang clmtest 7 7 check saClmClusterNodeGet with non-member node, previously designed as 0x2060F. In new test envionment, a new node is added so 0x2060F is a member node then make test case failed. propose: change test node_id to 0x2990F to avoid future conflict when test environment is upgraded. --- 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] #2497 clmtest: independent test cases
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:07bbef] ~~~ commit 07bbefc4f8cf70102906c1aed51371ee67c1fb75 Author: Hoang Vo Date: Tue Jun 20 16:42:34 2017 +0700 clmtest: correct independent test cases [#2497] clmtest 10 3 and 10 4 does not initialize its data struct but reuse global one lead to failure result when run alone. ~~~ 5.17.06 (release) [code:7a3a65] ~~~ commit 7a3a65972db57a15b82625f94986346b7eae0652 Author: Hoang Vo Date: Tue Jun 20 16:42:34 2017 +0700 clmtest: correct independent test cases [#2497] clmtest 10 3 and 10 4 does not initialize its data struct but reuse global one lead to failure result when run alone. ~~~ --- ** [tickets:#2497] clmtest: independent test cases** **Status:** fixed **Milestone:** 5.17.06 **Created:** Thu Jun 15, 2017 07:42 AM UTC by Vo Minh Hoang **Last Updated:** Thu Jun 15, 2017 08:34 AM UTC **Owner:** Vo Minh Hoang Some test cases in clmtest return correct value when run with suit but return ER result when run alone: clmtest 10 3 clmtest 10 4 --- 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] #2487 imm: IMMND crashes in immnd_proc_discard_other_nodes
- **status**: review --> fixed
- **Comment**:
5.17.08 (develop) [code:0129b4]
~~~
commit 0129b4ce2fc7601ef37bfea62fec65c30cd472c4
Author: Hung Nguyen
Date: Fri Jun 9 13:21:33 2017 +0700
imm: Allow stale clients to be discarded when going to headless [#2487]
Just like immnd_proc_imma_discard_stales(), in
immnd_proc_discard_other_nodes() we should unset the mIsStale flag of the
clients.
So that the clients can be discarded.
~~~
5.17.06 (release) [code:869c88]
~~~
commit 869c88a12facab111cbd315631b69a60639365a0
Author: Hung Nguyen
Date: Fri Jun 9 13:21:33 2017 +0700
imm: Allow stale clients to be discarded when going to headless [#2487]
Just like immnd_proc_imma_discard_stales(), in
immnd_proc_discard_other_nodes() we should unset the mIsStale flag of the
clients.
So that the clients can be discarded.
~~~
---
** [tickets:#2487] imm: IMMND crashes in immnd_proc_discard_other_nodes**
**Status:** fixed
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 10:58 AM UTC by Hung Nguyen
**Last Updated:** Fri Jun 09, 2017 08:19 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[logs_n_traces.7z](https://sourceforge.net/p/opensaf/tickets/2487/attachment/logs_n_traces.7z)
(13.5 MB; application/octet-stream)
IMMD was down when discarding a IMMA connection, that caused a failure and the
client was marked as stale.
~~~css
12:20:03.331159 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12127] T2 IMMA
DOWN EVENT
...
12:20:03.332028 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332031 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332035 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332038 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332042 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332046 osafimmnd [206:206:src/imm/immnd/immnd_mds.c:0781] T2 Director
Service Is Down
12:20:03.332062 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0156] WA Discard
implementer failed for implId:35 (immd_down)- will retry later
12:20:03.332073 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332083 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14012] NO
Implementer locally disconnected. Marking it as doomed 35 <97, 2020f>
(safLogService)
12:20:03.332087 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332090 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
12:20:03.332093 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0320] T5 Stale
marked client id:610002020f sv_id:27
~~~
Later when discarding other nodes, immnd_proc_imma_discard_connection()
returned false because the client was previously marked as stale
~~~
immModel_discardImplementer(cb, implId, scAbsence, NULL, NULL);
}
if (cl_node->mIsStale) {
TRACE_LEAVE();
return false;
}
~~~
~~~css
12:20:03.332133 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12219] NO IMMD
SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS
12:20:03.332201 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:2819] >>
immnd_proc_discard_other_nodes
...
12:20:03.332406 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332410 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332413 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332416 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332419 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332423 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332431 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13967] NO
Implementer disconnected 35 <97, 2020f> (safLogService)
12:20:03.332435 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332438 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
~~~
And IMMND crashed due to assertion failure
~~~css
12:20:03 SC-2 osafimmnd[206]: NO Implementer disconnected 35 <97, 2020f>
(safLogService)
12:20:03 SC-2 osafimmnd[206]: src/imm/immnd/immnd_proc.c:2828:
immnd_proc_discard_other_nodes: Assertion
'immnd_proc_imma_discard_connection(cb, cl_node, true)' failed.
~~~
Attached is logs and traces.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe fro
[tickets] [opensaf:tickets] #2484 imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:db1965] ~~~ commit db1965d634eac2f375f455b7b7d3e9f70ff0c47c Author: Hung Nguyen Date: Tue Jun 6 14:27:48 2017 +0700 immtest: Explicitly clear implementer name in OI long DN testcases [#2484] Explicitly clear implementer name in OI long DN testcases. ~~~ 5.17.06 (release) [code:4acdec] ~~~ commit 4acdecc368b6326d5997eec406474bdf51452064 Author: Hung Nguyen Date: Tue Jun 6 14:27:48 2017 +0700 immtest: Explicitly clear implementer name in OI long DN testcases [#2484] Explicitly clear implementer name in OI long DN testcases. ~~~ --- ** [tickets:#2484] imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN** **Status:** fixed **Milestone:** 5.17.06 **Created:** Tue Jun 06, 2017 04:25 AM UTC by Hung Nguyen **Last Updated:** Tue Jun 06, 2017 08:42 AM UTC **Owner:** Hung Nguyen ~~~ # immoitest --longDn 7 Suite 7: Long DN 1 PASSED SA_AIS_OK - Object create callback; 2 PASSED SA_AIS_OK - Object modify callback; 3 PASSED SA_AIS_OK - Object delete callback; 4 PASSED SA_AIS_OK - Rt Object create and delete; error: in src/imm/apitest/implementer/test_saImmOiLongDn.c at 500: SA_AIS_ERR_TRY_AGAIN (6), expected SA_AIS_OK (1) - exiting ~~~ The testcases of testsuite 7 use the same implementer name. At the end of each testcase, the implementer name is not explicitly cleared with saImmOiImplementerClear(). Instead, saImmOiFinalize() is called. The difference between OiImplementerClear() and OiFinalize() is: \- OiImplementerClear() returns after the implementer is fully discarded on all nodes \- saImmOiFinalize() returns after the implementer is locally discarded on the originating node (no guarantee of being fully discarded) So if you set the same implementer name after saImmOiFinalize(), chances are you will get ERR_TRY_AGAIN. --- 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] #2470 imm: IMMND coredump when discarding client
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:a2200e] ~~~ commit a2200ef57c047abb66150ae6ff9c4a762337ad02 Author: Hung Nguyen Date: Mon May 29 16:52:45 2017 +0700 imm: Clear mLastResult before sending response to agent [#2470] In immnd_evt_proc_search_next(), before jumping to agent_rsp, mLastResult must be cleared. So that it will not be freed again in immnd_proc_imma_discard_connection(). ~~~ 5.17.06 (release) [code:3420dc] ~~~ commit 3420dcfd9d1d64da38ff05ff568e37e66958cfb0 Author: Hung Nguyen Date: Mon May 29 16:52:45 2017 +0700 imm: Clear mLastResult before sending response to agent [#2470] In immnd_evt_proc_search_next(), before jumping to agent_rsp, mLastResult must be cleared. So that it will not be freed again in immnd_proc_imma_discard_connection(). ~~~ --- ** [tickets:#2470] imm: IMMND coredump when discarding client** **Status:** fixed **Milestone:** 5.17.06 **Created:** Mon May 29, 2017 04:05 AM UTC by Hung Nguyen **Last Updated:** Mon May 29, 2017 11:36 AM UTC **Owner:** Hung Nguyen **mLastResult** of **ImmSearchOp** was double freed in **immnd_evt_proc_search_next()** and later in **immnd_proc_imma_discard_connection()**. In **immnd_evt_proc_search_next()**, before jumping to **agent_rsp**, **mLastResult** must be cleared. So that it will not be freed again in **immnd_proc_imma_discard_connection()**. ~~~ 2017-04-25T05:30:24.483922-04:00 local0.warning scm2 osafimmnd[2793]: WA ERR_NO_RESOURCES: SearchNext: Implementer died during fetch of pure RTA 2017-04-25T05:30:24.670234-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' component restart probation timer started (timeout: 600 ns) 2017-04-25T05:30:24.670313-04:00 local0.notice scm2 osafamfnd[4402]: NO Restarting a component of 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1) 2017-04-25T05:30:24.670514-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safComp=IMMND,safSu=SCM2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' ~~~ ~~~ GNU gdb (Wind River Linux Sourcery CodeBench 4.8-28) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-wrs-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib64/opensaf/osafimmnd...Reading symbols from /usr/lib64/opensaf/.debug/osafimmnd...done. done. [New LWP 2793] [New LWP 2797] [New LWP 2795] [New LWP 2796] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib64/opensaf/osafimmnd osafimmnd'. Program terminated with signal 6, Aborted. #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x003d84a38508 in __GI_abort () at abort.c:89 #2 0x003d84a6e964 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x3d84b65f88 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x003d84a786be in malloc_printerr (action=3, str=0x3d84b62052 "free(): invalid pointer", ptr=) at malloc.c:4895 #4 0x003d84a79397 in _int_free (av=, p=0xf8c0f0, have_lock=0) at malloc.c:3751 #5 0x004088af in freeSearchNext (rsp=0xbe5d60, freeTop=SA_TRUE) at immnd_evt.c:1378 #6 0x00424602 in immnd_proc_imma_discard_connection (cb=0x6eee60 <_immnd_cb>, cl_node=0x956b60, scAbsence=false) at immnd_proc.c:108 #7 0x0040a657 in immnd_evt_proc_imm_finalize (cb=0x6eee60 <_immnd_cb>, evt=0x7ff2640029c0, sinfo=0x7ff264002b00, isOm=SA_TRUE) at immnd_evt.c:2071 #8 0x0040614c in immnd_process_evt () at immnd_evt.c:535 #9 0x00422e14 in main (argc=2, argv=0x7fff532890f8) at immnd_main.c:370 (gdb) ~~~ --- 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
[tickets] [opensaf:tickets] #2487 imm: IMMND crashes in immnd_proc_discard_other_nodes
- **status**: accepted --> review
---
** [tickets:#2487] imm: IMMND crashes in immnd_proc_discard_other_nodes**
**Status:** review
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 10:58 AM UTC by Hung Nguyen
**Last Updated:** Wed Jun 07, 2017 10:58 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[logs_n_traces.7z](https://sourceforge.net/p/opensaf/tickets/2487/attachment/logs_n_traces.7z)
(13.5 MB; application/octet-stream)
IMMD was down when discarding a IMMA connection, that caused a failure and the
client was marked as stale.
~~~css
12:20:03.331159 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12127] T2 IMMA
DOWN EVENT
...
12:20:03.332028 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332031 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332035 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332038 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332042 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332046 osafimmnd [206:206:src/imm/immnd/immnd_mds.c:0781] T2 Director
Service Is Down
12:20:03.332062 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0156] WA Discard
implementer failed for implId:35 (immd_down)- will retry later
12:20:03.332073 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332083 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14012] NO
Implementer locally disconnected. Marking it as doomed 35 <97, 2020f>
(safLogService)
12:20:03.332087 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332090 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
12:20:03.332093 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0320] T5 Stale
marked client id:610002020f sv_id:27
~~~
Later when discarding other nodes, immnd_proc_imma_discard_connection()
returned false because the client was previously marked as stale
~~~
immModel_discardImplementer(cb, implId, scAbsence, NULL, NULL);
}
if (cl_node->mIsStale) {
TRACE_LEAVE();
return false;
}
~~~
~~~css
12:20:03.332133 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12219] NO IMMD
SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS
12:20:03.332201 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:2819] >>
immnd_proc_discard_other_nodes
...
12:20:03.332406 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332410 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332413 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332416 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332419 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332423 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332431 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13967] NO
Implementer disconnected 35 <97, 2020f> (safLogService)
12:20:03.332435 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332438 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
~~~
And IMMND crashed due to assertion failure
~~~css
12:20:03 SC-2 osafimmnd[206]: NO Implementer disconnected 35 <97, 2020f>
(safLogService)
12:20:03 SC-2 osafimmnd[206]: src/imm/immnd/immnd_proc.c:2828:
immnd_proc_discard_other_nodes: Assertion
'immnd_proc_imma_discard_connection(cb, cl_node, true)' failed.
~~~
Attached is logs and traces.
---
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] #2487 imm: IMMND crashes in immnd_proc_discard_other_nodes
---
** [tickets:#2487] imm: IMMND crashes in immnd_proc_discard_other_nodes**
**Status:** accepted
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 10:58 AM UTC by Hung Nguyen
**Last Updated:** Wed Jun 07, 2017 10:58 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[logs_n_traces.7z](https://sourceforge.net/p/opensaf/tickets/2487/attachment/logs_n_traces.7z)
(13.5 MB; application/octet-stream)
IMMD was down when discarding a IMMA connection, that caused a failure and the
client was marked as stale.
~~~css
12:20:03.331159 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12127] T2 IMMA
DOWN EVENT
...
12:20:03.332028 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332031 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332035 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332038 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332042 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332046 osafimmnd [206:206:src/imm/immnd/immnd_mds.c:0781] T2 Director
Service Is Down
12:20:03.332062 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0156] WA Discard
implementer failed for implId:35 (immd_down)- will retry later
12:20:03.332073 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332083 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14012] NO
Implementer locally disconnected. Marking it as doomed 35 <97, 2020f>
(safLogService)
12:20:03.332087 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332090 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
12:20:03.332093 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0320] T5 Stale
marked client id:610002020f sv_id:27
~~~
Later when discarding other nodes, immnd_proc_imma_discard_connection()
returned false because the client was previously marked as stale
~~~
immModel_discardImplementer(cb, implId, scAbsence, NULL, NULL);
}
if (cl_node->mIsStale) {
TRACE_LEAVE();
return false;
}
~~~
~~~css
12:20:03.332133 osafimmnd [206:206:src/imm/immnd/immnd_evt.c:12219] NO IMMD
SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS
12:20:03.332201 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:2819] >>
immnd_proc_discard_other_nodes
...
12:20:03.332406 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0091] >>
immnd_proc_imma_discard_connection
12:20:03.332410 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0096] T5
Attempting discard connection id:610002020f
12:20:03.332413 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14042] >>
discardContinuations
12:20:03.332416 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14095] <<
discardContinuations
12:20:03.332419 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0138] T5
Discarding implementer id:35 for connection: 97
12:20:03.332423 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13961] >>
discardImplementer
12:20:03.332431 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:13967] NO
Implementer disconnected 35 <97, 2020f> (safLogService)
12:20:03.332435 osafimmnd [206:206:src/imm/immnd/ImmModel.cc:14038] <<
discardImplementer
12:20:03.332438 osafimmnd [206:206:src/imm/immnd/immnd_proc.c:0169] <<
immnd_proc_imma_discard_connection
~~~
And IMMND crashed due to assertion failure
~~~css
12:20:03 SC-2 osafimmnd[206]: NO Implementer disconnected 35 <97, 2020f>
(safLogService)
12:20:03 SC-2 osafimmnd[206]: src/imm/immnd/immnd_proc.c:2828:
immnd_proc_discard_other_nodes: Assertion
'immnd_proc_imma_discard_connection(cb, cl_node, true)' failed.
~~~
Attached is logs and traces.
---
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] #2484 imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN
- **status**: accepted --> review --- ** [tickets:#2484] imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN** **Status:** review **Milestone:** 5.17.06 **Created:** Tue Jun 06, 2017 04:25 AM UTC by Hung Nguyen **Last Updated:** Tue Jun 06, 2017 04:25 AM UTC **Owner:** Hung Nguyen ~~~ # immoitest --longDn 7 Suite 7: Long DN 1 PASSED SA_AIS_OK - Object create callback; 2 PASSED SA_AIS_OK - Object modify callback; 3 PASSED SA_AIS_OK - Object delete callback; 4 PASSED SA_AIS_OK - Rt Object create and delete; error: in src/imm/apitest/implementer/test_saImmOiLongDn.c at 500: SA_AIS_ERR_TRY_AGAIN (6), expected SA_AIS_OK (1) - exiting ~~~ The testcases of testsuite 7 use the same implementer name. At the end of each testcase, the implementer name is not explicitly cleared with saImmOiImplementerClear(). Instead, saImmOiFinalize() is called. The difference between OiImplementerClear() and OiFinalize() is: \- OiImplementerClear() returns after the implementer is fully discarded on all nodes \- saImmOiFinalize() returns after the implementer is locally discarded on the originating node (no guarantee of being fully discarded) So if you set the same implementer name after saImmOiFinalize(), chances are you will get ERR_TRY_AGAIN. --- 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] #2478 clmtest: failed test cases
- **status**: review --> fixed - **Milestone**: 5.17.08 --> 5.17.06 - **Comment**: 5.17.08 (develop) [code:664e46] ~~~ commit 664e46e54ef3c4b2e11b84e5efc73916ba6f6fc2 Author: Hoang Vo Date: Tue Jun 6 17:39:02 2017 +0700 clmtest: Correct test case following AIS [#2478] Correct test case following AIS. ~~~ 5.17.06 (release) [code:360bb7] ~~~ commit 360bb7dee0b8d85ae7e25d70ba1c7d7eab034b8a Author: Hoang Vo Date: Tue Jun 6 17:39:02 2017 +0700 clmtest: Correct test case following AIS [#2478] Correct test case following AIS. ~~~ --- ** [tickets:#2478] clmtest: failed test cases** **Status:** fixed **Milestone:** 5.17.06 **Created:** Fri Jun 02, 2017 06:20 AM UTC by Vo Minh Hoang **Last Updated:** Fri Jun 02, 2017 07:32 AM UTC **Owner:** Vo Minh Hoang Test cases failed due to inconsistence with specification: Suite 2 - saClmSelectionObjectGet NULL handle Suite 5 - saClmClusterNodeGet & saClmClusterNodeGet_4 with NULL timeout Suite 5 - saClmClusterNodeGet & saClmClusterNodeGet_4 with nodeId of non member node Suite 7 - saClmClusterTrack_4 with null handle or invalid handle Suite 7 - saClmClusterTrack_4 with null flags --- 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] #2484 imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN
--- ** [tickets:#2484] imm: Testsuit 7 of immoitest fails with ERR_TRY_AGAIN** **Status:** accepted **Milestone:** 5.17.06 **Created:** Tue Jun 06, 2017 04:25 AM UTC by Hung Nguyen **Last Updated:** Tue Jun 06, 2017 04:25 AM UTC **Owner:** Hung Nguyen ~~~ # immoitest --longDn 7 Suite 7: Long DN 1 PASSED SA_AIS_OK - Object create callback; 2 PASSED SA_AIS_OK - Object modify callback; 3 PASSED SA_AIS_OK - Object delete callback; 4 PASSED SA_AIS_OK - Rt Object create and delete; error: in src/imm/apitest/implementer/test_saImmOiLongDn.c at 500: SA_AIS_ERR_TRY_AGAIN (6), expected SA_AIS_OK (1) - exiting ~~~ The testcases of testsuite 7 use the same implementer name. At the end of each testcase, the implementer name is not explicitly cleared with saImmOiImplementerClear(). Instead, saImmOiFinalize() is called. The difference between OiImplementerClear() and OiFinalize() is: \- OiImplementerClear() returns after the implementer is fully discarded on all nodes \- saImmOiFinalize() returns after the implementer is locally discarded on the originating node (no guarantee of being fully discarded) So if you set the same implementer name after saImmOiFinalize(), chances are you will get ERR_TRY_AGAIN. --- 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] #2470 imm: IMMND coredump when discarding client
- **status**: accepted --> review --- ** [tickets:#2470] imm: IMMND coredump when discarding client** **Status:** review **Milestone:** 5.17.06 **Created:** Mon May 29, 2017 04:05 AM UTC by Hung Nguyen **Last Updated:** Mon May 29, 2017 04:05 AM UTC **Owner:** Hung Nguyen **mLastResult** of **ImmSearchOp** was double freed in **immnd_evt_proc_search_next()** and later in **immnd_proc_imma_discard_connection()**. In **immnd_evt_proc_search_next()**, before jumping to **agent_rsp**, **mLastResult** must be cleared. So that it will not be freed again in **immnd_proc_imma_discard_connection()**. ~~~ 2017-04-25T05:30:24.483922-04:00 local0.warning scm2 osafimmnd[2793]: WA ERR_NO_RESOURCES: SearchNext: Implementer died during fetch of pure RTA 2017-04-25T05:30:24.670234-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' component restart probation timer started (timeout: 600 ns) 2017-04-25T05:30:24.670313-04:00 local0.notice scm2 osafamfnd[4402]: NO Restarting a component of 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1) 2017-04-25T05:30:24.670514-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safComp=IMMND,safSu=SCM2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' ~~~ ~~~ GNU gdb (Wind River Linux Sourcery CodeBench 4.8-28) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-wrs-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib64/opensaf/osafimmnd...Reading symbols from /usr/lib64/opensaf/.debug/osafimmnd...done. done. [New LWP 2793] [New LWP 2797] [New LWP 2795] [New LWP 2796] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib64/opensaf/osafimmnd osafimmnd'. Program terminated with signal 6, Aborted. #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x003d84a38508 in __GI_abort () at abort.c:89 #2 0x003d84a6e964 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x3d84b65f88 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x003d84a786be in malloc_printerr (action=3, str=0x3d84b62052 "free(): invalid pointer", ptr=) at malloc.c:4895 #4 0x003d84a79397 in _int_free (av=, p=0xf8c0f0, have_lock=0) at malloc.c:3751 #5 0x004088af in freeSearchNext (rsp=0xbe5d60, freeTop=SA_TRUE) at immnd_evt.c:1378 #6 0x00424602 in immnd_proc_imma_discard_connection (cb=0x6eee60 <_immnd_cb>, cl_node=0x956b60, scAbsence=false) at immnd_proc.c:108 #7 0x0040a657 in immnd_evt_proc_imm_finalize (cb=0x6eee60 <_immnd_cb>, evt=0x7ff2640029c0, sinfo=0x7ff264002b00, isOm=SA_TRUE) at immnd_evt.c:2071 #8 0x0040614c in immnd_process_evt () at immnd_evt.c:535 #9 0x00422e14 in main (argc=2, argv=0x7fff532890f8) at immnd_main.c:370 (gdb) ~~~ --- 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] #2470 imm: IMMND coredump when discarding client
--- ** [tickets:#2470] imm: IMMND coredump when discarding client** **Status:** accepted **Milestone:** 5.17.06 **Created:** Mon May 29, 2017 04:05 AM UTC by Hung Nguyen **Last Updated:** Mon May 29, 2017 04:05 AM UTC **Owner:** Hung Nguyen **mLastResult** of **ImmSearchOp** was double freed in **immnd_evt_proc_search_next()** and later in **immnd_proc_imma_discard_connection()**. In **immnd_evt_proc_search_next()**, before jumping to **agent_rsp**, **mLastResult** must be cleared. So that it will not be freed again in **immnd_proc_imma_discard_connection()**. ~~~ 2017-04-25T05:30:24.483922-04:00 local0.warning scm2 osafimmnd[2793]: WA ERR_NO_RESOURCES: SearchNext: Implementer died during fetch of pure RTA 2017-04-25T05:30:24.670234-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' component restart probation timer started (timeout: 600 ns) 2017-04-25T05:30:24.670313-04:00 local0.notice scm2 osafamfnd[4402]: NO Restarting a component of 'safSu=SCM2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1) 2017-04-25T05:30:24.670514-04:00 local0.notice scm2 osafamfnd[4402]: NO 'safComp=IMMND,safSu=SCM2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' ~~~ ~~~ GNU gdb (Wind River Linux Sourcery CodeBench 4.8-28) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-wrs-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib64/opensaf/osafimmnd...Reading symbols from /usr/lib64/opensaf/.debug/osafimmnd...done. done. [New LWP 2793] [New LWP 2797] [New LWP 2795] [New LWP 2796] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib64/opensaf/osafimmnd osafimmnd'. Program terminated with signal 6, Aborted. #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x003d84a353e9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x003d84a38508 in __GI_abort () at abort.c:89 #2 0x003d84a6e964 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x3d84b65f88 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x003d84a786be in malloc_printerr (action=3, str=0x3d84b62052 "free(): invalid pointer", ptr=) at malloc.c:4895 #4 0x003d84a79397 in _int_free (av=, p=0xf8c0f0, have_lock=0) at malloc.c:3751 #5 0x004088af in freeSearchNext (rsp=0xbe5d60, freeTop=SA_TRUE) at immnd_evt.c:1378 #6 0x00424602 in immnd_proc_imma_discard_connection (cb=0x6eee60 <_immnd_cb>, cl_node=0x956b60, scAbsence=false) at immnd_proc.c:108 #7 0x0040a657 in immnd_evt_proc_imm_finalize (cb=0x6eee60 <_immnd_cb>, evt=0x7ff2640029c0, sinfo=0x7ff264002b00, isOm=SA_TRUE) at immnd_evt.c:2071 #8 0x0040614c in immnd_process_evt () at immnd_evt.c:535 #9 0x00422e14 in main (argc=2, argv=0x7fff532890f8) at immnd_main.c:370 (gdb) ~~~ --- 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] #2461 imm: Adm Impl continuation and Search Impl continuation are not discarded when peer IMMND is down
- **summary**: imm: AdmOp continuation is not discarded when peer IMMND is down --> imm: Adm Impl continuation and Search Impl continuation are not discarded when peer IMMND is down - Description has changed: Diff: --- old +++ new @@ -9,3 +9,5 @@ 13:06:30 SC-2 osafimmnd[224]: ER Problem in sending to peer IMMND over MDS. Discarding admin op reply. 13:06:30 SC-2 osafimmnd[224]: WA Error code 2 returned for message type 21 - ignoring ~~~ + +This ticket also fix the familiar problem with Search Impl continuation. - **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:40b8e4] ~~~ commit 40b8e4a53b9de7efbda2e7eb141da4701df7 Author: Hung Nguyen Date: Wed May 17 14:10:16 2017 +0700 imm: Discard Adm Impl continuation and Search Impl continuation when peer IMMND is down [#2461] Discard Adm Impl continuation and Search Impl continuation when peer IMMND is down. ~~~ 5.17.06 (release) [code:8ef603] ~~~ commit 8ef603fd8d48016493df3c3fb9d3cba22078aece Author: Hung Nguyen Date: Wed May 17 14:10:16 2017 +0700 imm: Discard Adm Impl continuation and Search Impl continuation when peer IMMND is down [#2461] Discard Adm Impl continuation and Search Impl continuation when peer IMMND is down. ~~~ --- ** [tickets:#2461] imm: Adm Impl continuation and Search Impl continuation are not discarded when peer IMMND is down** **Status:** fixed **Milestone:** 5.17.06 **Created:** Mon May 15, 2017 06:46 AM UTC by Hung Nguyen **Last Updated:** Wed May 17, 2017 08:03 AM UTC **Owner:** Hung Nguyen Reproduce steps: \- OI is on SC-2 \- OM client on SC-1 invokes an admin operation \- Before OI sends admin operation response to IMMND on SC-2, bring IMMND on SC-1 down \- The admop continuation (**sAdmImplContinuationMap**) on SC-2 is not discarded and when receiving the response, it fails to send to IMMND on SC-1 because **mReply_dest** is not correct anymore. ~~~ 13:06:30 SC-2 osafimmnd[224]: WA MDS Send Failed to service:IMMND rc:2 13:06:30 SC-2 osafimmnd[224]: ER Problem in sending to peer IMMND over MDS. Discarding admin op reply. 13:06:30 SC-2 osafimmnd[224]: WA Error code 2 returned for message type 21 - ignoring ~~~ This ticket also fix the familiar problem with Search Impl continuation. --- 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] #2418 imm: Info of dead IMMND remains in standby IMMD
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:ff044b] ~~~ commit ff044b93c3182997cbe9ab318245846c876ecd02 Author: Hung Nguyen Date: Mon May 15 14:09:06 2017 +0700 imm: Clear dead IMMND info before switching to ACTIVE role [#2418] During cold-sync, standby IMMD may receive info of dead IMMND. Before switching to active, the IMMD should clear those dead IMMND info. ~~~ 5.17.06 (release) [code:b6d724] ~~~ commit b6d724a849988ef91dcfad4c0267df7a8ea96e4b Author: Hung Nguyen Date: Mon May 15 14:09:06 2017 +0700 imm: Clear dead IMMND info before switching to ACTIVE role [#2418] During cold-sync, standby IMMD may receive info of dead IMMND. Before switching to active, the IMMD should clear those dead IMMND info. ~~~ --- ** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD** **Status:** fixed **Milestone:** 5.17.06 **Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen **Last Updated:** Wed May 17, 2017 08:12 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz) (149.4 kB; application/x-compressed) When Standby IMMD is up at the same time with a IMMND exiting, the info of that IMMND might not be removed from **immnd_tree** of the Standby IMMD. Details of the problem is explained in the sequence diagram below [sequence diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA) SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting ~~~ 18:35:03 SC-1 osafimmnd[441]: exiting for shutdown 18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:568511936070075) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:567412424442298) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:566312912814523) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:565213401186744) 18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4, dest:564113889558969) ~~~ Down event for IMMND@SC-1 was received on SC-5 but not on SC-2. **The symptoms:** 1. If the down IMMND is the corrdinator, that results in when that Standby IMMD becomes Active, it fails to elect new coordinator as there's already a coordinator in the **immnd_tree**. ~~~ 18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed => electing new coord ~~~ No more logs about newly elected coordinator were printed out. 2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch. ~~~ 18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING 18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord 18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting ~~~ --- 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] #2447 imm: Avoid IMMND from sending introduce message when IMMD is not back from headless
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:a2798c] ~~~ commit a2798cef6b42f6c000d5bc0d4b9593eca367ea87 Author: Hung Nguyen Date: Mon May 8 13:30:10 2017 +0700 imm: Skip sending re-intro message if IMMD is not up [#2447] Skip sending re-intro message if IMMD is not up. ~~~ --- ** [tickets:#2447] imm: Avoid IMMND from sending introduce message when IMMD is not back from headless** **Status:** fixed **Milestone:** 5.17.08 **Created:** Wed May 03, 2017 04:04 AM UTC by Hung Nguyen **Last Updated:** Tue May 09, 2017 08:29 AM UTC **Owner:** Hung Nguyen During headless, IMMND keeps sending introduce message even when IMMD is not up yet. ~~~ May 3 10:53:15 PL-3 osafimmnd[195]: NO MDS unregisterede. sleeping ... May 3 10:53:16 PL-3 osafimmnd[195]: NO Sleep done registering IMMND with MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO SUCCESS IN REGISTERING IMMND WITH MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:18 PL-3 osafclmna[185]: NO Starting to promote this node to a system controller May 3 10:53:22 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:23 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:23 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:24 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:24 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:25 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:25 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 ... ~~~ --- 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] #2446 imm: CcbErrorStrings about OI/PBE are not set in all nodes
- **status**: review --> fixed
- **Comment**:
5.17.06 (release) [code:a16e75]
~~~
commit a16e75230da4d41e7359728e2451c7683da69183
Author: Hung Nguyen
Date: Mon May 8 11:09:34 2017 +0700
imm: Remove CcbErrStrings that are set only on nodes with OI/PBE [#2446]
Remove CcbErrStrings that are set only on nodes with OI/PBE.
~~~
5.17.08 (develop) [code:f9906a]
~~~
commit f9906af0227fb859bfda991a5ed03d664c6e152e
Author: Hung Nguyen
Date: Mon May 8 11:09:34 2017 +0700
imm: Remove CcbErrStrings that are set only on nodes with OI/PBE [#2446]
Remove CcbErrStrings that are set only on nodes with OI/PBE.
~~~
---
** [tickets:#2446] imm: CcbErrorStrings about OI/PBE are not set in all nodes**
**Status:** fixed
**Milestone:** 5.17.06
**Created:** Wed May 03, 2017 03:32 AM UTC by Hung Nguyen
**Last Updated:** Tue May 09, 2017 08:29 AM UTC
**Owner:** Hung Nguyen
Example:
~~~
if (implConn) {
/*The implementer is local, make the up-call */
...
/*Fetch client node for OI ! */
immnd_client_node_get(cb, implHandle, &oi_cl_node);
if (oi_cl_node == NULL || oi_cl_node->mIsStale) {
...
immModel_setCcbErrorString(
cb, evt->info.objCreate.ccbId,
IMM_RESOURCE_ABORT "Client died");
}
~~~
The error string is only sent to OM client when the OM client is on the same
node with the OI.
That causes inconsistency between OM being on the same node with OI and OM
being on different node than OI.
---
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] #2418 imm: Info of dead IMMND remains in standby IMMD
- **status**: fixed --> review - **Comment**: Re-open this ticket since the new active IMMD (switches from STANDBY role) has problem with dead IMMND in the immnd_tree. The dead IMMND should be cleanup before switching to ACTIVE. --- ** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD** **Status:** review **Milestone:** 5.17.06 **Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen **Last Updated:** Tue Apr 25, 2017 06:45 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz) (149.4 kB; application/x-compressed) When Standby IMMD is up at the same time with a IMMND exiting, the info of that IMMND might not be removed from **immnd_tree** of the Standby IMMD. Details of the problem is explained in the sequence diagram below [sequence diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA) SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting ~~~ 18:35:03 SC-1 osafimmnd[441]: exiting for shutdown 18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:568511936070075) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:567412424442298) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:566312912814523) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:565213401186744) 18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4, dest:564113889558969) ~~~ Down event for IMMND@SC-1 was received on SC-5 but not on SC-2. **The symptoms:** 1. If the down IMMND is the corrdinator, that results in when that Standby IMMD becomes Active, it fails to elect new coordinator as there's already a coordinator in the **immnd_tree**. ~~~ 18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed => electing new coord ~~~ No more logs about newly elected coordinator were printed out. 2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch. ~~~ 18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING 18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord 18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting ~~~ --- 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] #2461 imm: AdmOp continuation is not discarded when peer IMMND is down
- **status**: accepted --> review --- ** [tickets:#2461] imm: AdmOp continuation is not discarded when peer IMMND is down** **Status:** review **Milestone:** 5.17.06 **Created:** Mon May 15, 2017 06:46 AM UTC by Hung Nguyen **Last Updated:** Mon May 15, 2017 06:46 AM UTC **Owner:** Hung Nguyen Reproduce steps: \- OI is on SC-2 \- OM client on SC-1 invokes an admin operation \- Before OI sends admin operation response to IMMND on SC-2, bring IMMND on SC-1 down \- The admop continuation (**sAdmImplContinuationMap**) on SC-2 is not discarded and when receiving the response, it fails to send to IMMND on SC-1 because **mReply_dest** is not correct anymore. ~~~ 13:06:30 SC-2 osafimmnd[224]: WA MDS Send Failed to service:IMMND rc:2 13:06:30 SC-2 osafimmnd[224]: ER Problem in sending to peer IMMND over MDS. Discarding admin op reply. 13:06:30 SC-2 osafimmnd[224]: WA Error code 2 returned for message type 21 - ignoring ~~~ --- 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] #2461 imm: AdmOp continuation is not discarded when peer IMMND is down
--- ** [tickets:#2461] imm: AdmOp continuation is not discarded when peer IMMND is down** **Status:** accepted **Milestone:** 5.17.06 **Created:** Mon May 15, 2017 06:46 AM UTC by Hung Nguyen **Last Updated:** Mon May 15, 2017 06:46 AM UTC **Owner:** Hung Nguyen Reproduce steps: \- OI is on SC-2 \- OM client on SC-1 invokes an admin operation \- Before OI sends admin operation response to IMMND on SC-2, bring IMMND on SC-1 down \- The admop continuation (**sAdmImplContinuationMap**) on SC-2 is not discarded and when receiving the response, it fails to send to IMMND on SC-1 because **mReply_dest** is not correct anymore. ~~~ 13:06:30 SC-2 osafimmnd[224]: WA MDS Send Failed to service:IMMND rc:2 13:06:30 SC-2 osafimmnd[224]: ER Problem in sending to peer IMMND over MDS. Discarding admin op reply. 13:06:30 SC-2 osafimmnd[224]: WA Error code 2 returned for message type 21 - ignoring ~~~ --- 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] #2446 imm: CcbErrorStrings about OI/PBE are not set in all nodes
- **status**: accepted --> review
---
** [tickets:#2446] imm: CcbErrorStrings about OI/PBE are not set in all nodes**
**Status:** review
**Milestone:** 5.17.06
**Created:** Wed May 03, 2017 03:32 AM UTC by Hung Nguyen
**Last Updated:** Wed May 03, 2017 03:32 AM UTC
**Owner:** Hung Nguyen
Example:
~~~
if (implConn) {
/*The implementer is local, make the up-call */
...
/*Fetch client node for OI ! */
immnd_client_node_get(cb, implHandle, &oi_cl_node);
if (oi_cl_node == NULL || oi_cl_node->mIsStale) {
...
immModel_setCcbErrorString(
cb, evt->info.objCreate.ccbId,
IMM_RESOURCE_ABORT "Client died");
}
~~~
The error string is only sent to OM client when the OM client is on the same
node with the OI.
That causes inconsistency between OM being on the same node with OI and OM
being on different node than OI.
---
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] #2447 imm: Avoid IMMND from sending introduce message when IMMD is not back from headless
- **status**: accepted --> review --- ** [tickets:#2447] imm: Avoid IMMND from sending introduce message when IMMD is not back from headless** **Status:** review **Milestone:** 5.17.08 **Created:** Wed May 03, 2017 04:04 AM UTC by Hung Nguyen **Last Updated:** Wed May 03, 2017 04:04 AM UTC **Owner:** Hung Nguyen During headless, IMMND keeps sending introduce message even when IMMD is not up yet. ~~~ May 3 10:53:15 PL-3 osafimmnd[195]: NO MDS unregisterede. sleeping ... May 3 10:53:16 PL-3 osafimmnd[195]: NO Sleep done registering IMMND with MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO SUCCESS IN REGISTERING IMMND WITH MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:18 PL-3 osafclmna[185]: NO Starting to promote this node to a system controller May 3 10:53:22 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:23 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:23 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:24 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:24 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:25 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:25 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 ... ~~~ --- 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] #2447 imm: Avoid IMMND from sending introduce message when IMMD is not back from headless
--- ** [tickets:#2447] imm: Avoid IMMND from sending introduce message when IMMD is not back from headless** **Status:** accepted **Milestone:** 5.17.08 **Created:** Wed May 03, 2017 04:04 AM UTC by Hung Nguyen **Last Updated:** Wed May 03, 2017 04:04 AM UTC **Owner:** Hung Nguyen During headless, IMMND keeps sending introduce message even when IMMD is not up yet. ~~~ May 3 10:53:15 PL-3 osafimmnd[195]: NO MDS unregisterede. sleeping ... May 3 10:53:16 PL-3 osafimmnd[195]: NO Sleep done registering IMMND with MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO SUCCESS IN REGISTERING IMMND WITH MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:18 PL-3 osafclmna[185]: NO Starting to promote this node to a system controller May 3 10:53:22 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:23 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:23 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:24 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:24 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:25 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:25 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 ... ~~~ --- 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] #2446 imm: CcbErrorStrings about OI/PBE are not set in all nodes
---
** [tickets:#2446] imm: CcbErrorStrings about OI/PBE are not set in all nodes**
**Status:** accepted
**Milestone:** 5.17.06
**Created:** Wed May 03, 2017 03:32 AM UTC by Hung Nguyen
**Last Updated:** Wed May 03, 2017 03:32 AM UTC
**Owner:** Hung Nguyen
Example:
~~~
if (implConn) {
/*The implementer is local, make the up-call */
...
/*Fetch client node for OI ! */
immnd_client_node_get(cb, implHandle, &oi_cl_node);
if (oi_cl_node == NULL || oi_cl_node->mIsStale) {
...
immModel_setCcbErrorString(
cb, evt->info.objCreate.ccbId,
IMM_RESOURCE_ABORT "Client died");
}
~~~
The error string is only sent to OM client when the OM client is on the same
node with the OI.
That causes inconsistency between OM being on the same node with OI and OM
being on different node than OI.
---
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] #2367 imm: Improve ccb error string handling
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:94fe6f] ~~~ commit 94fe6f2ca5c34bafc86f001807ea08ce39f60a34 Author: Hieu Nguyen Date: Thu Apr 27 10:17:51 2017 +0700 imm: Improve ccb error string handling [#2367] ~~~ --- ** [tickets:#2367] imm: Improve ccb error string handling** **Status:** fixed **Milestone:** 5.17.08 **Created:** Mon Mar 13, 2017 03:34 AM UTC by Hung Nguyen **Last Updated:** Mon Apr 24, 2017 04:13 AM UTC **Owner:** Hieu Nguyen * Use ::setCcbErrorString in ::ccbObjDelContinuation and::ccbCompletedContinuation instead of working directly with ccb->mErrorStrings * Only store error strings on originating node where OM client resides. --- 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] #2418 imm: Info of dead IMMND remains in standby IMMD
- **status**: review --> fixed --- ** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD** **Status:** fixed **Milestone:** 5.17.06 **Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen **Last Updated:** Tue Apr 25, 2017 06:44 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz) (149.4 kB; application/x-compressed) When Standby IMMD is up at the same time with a IMMND exiting, the info of that IMMND might not be removed from **immnd_tree** of the Standby IMMD. Details of the problem is explained in the sequence diagram below [sequence diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA) SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting ~~~ 18:35:03 SC-1 osafimmnd[441]: exiting for shutdown 18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:568511936070075) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:567412424442298) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:566312912814523) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:565213401186744) 18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4, dest:564113889558969) ~~~ Down event for IMMND@SC-1 was received on SC-5 but not on SC-2. **The symptoms:** 1. If the down IMMND is the corrdinator, that results in when that Standby IMMD becomes Active, it fails to elect new coordinator as there's already a coordinator in the **immnd_tree**. ~~~ 18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed => electing new coord ~~~ No more logs about newly elected coordinator were printed out. 2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch. ~~~ 18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING 18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord 18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting ~~~ --- 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] #2418 imm: Info of dead IMMND remains in standby IMMD
- **Blocker**: --> False - **Milestone**: 5.0.2 --> 5.17.06 - **Comment**: 5.17.08 (develop) [code:85c90b] ~~~ commit 85c90b4abead8bd66e1f20be3f84255645880597 Author: Hung Nguyen Date: Tue Apr 25 13:24:29 2017 +0700 imm: Ignore the sync'ed IMMND nodes that are not up [#2418] ~~~ 5.17.06 (release) [code:c1a37f] ~~~ commit c1a37fb5032c0e63165bc36e79d5a79be3fd19dd Author: Hung Nguyen Date: Tue Apr 25 13:24:29 2017 +0700 imm: Ignore the sync'ed IMMND nodes that are not up [#2418] ~~~ default (mercurial) [staging:dc6067] ~~~ changeset: 8777:dc60670bfd3b user: Hung Nguyen date:Tue Apr 25 13:40:04 2017 +0700 summary: imm: Ignore the sync'ed IMMND nodes that are not up [#2418] ~~~ --- ** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD** **Status:** review **Milestone:** 5.17.06 **Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen **Last Updated:** Thu Apr 13, 2017 10:08 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz) (149.4 kB; application/x-compressed) When Standby IMMD is up at the same time with a IMMND exiting, the info of that IMMND might not be removed from **immnd_tree** of the Standby IMMD. Details of the problem is explained in the sequence diagram below [sequence diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA) SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting ~~~ 18:35:03 SC-1 osafimmnd[441]: exiting for shutdown 18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:568511936070075) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:567412424442298) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:566312912814523) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:565213401186744) 18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4, dest:564113889558969) ~~~ Down event for IMMND@SC-1 was received on SC-5 but not on SC-2. **The symptoms:** 1. If the down IMMND is the corrdinator, that results in when that Standby IMMD becomes Active, it fails to elect new coordinator as there's already a coordinator in the **immnd_tree**. ~~~ 18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed => electing new coord ~~~ No more logs about newly elected coordinator were printed out. 2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch. ~~~ 18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING 18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord 18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting ~~~ --- 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] #2433 imm: Add more details to no dangling CcbErrorString
- **status**: accepted --> fixed - **Blocker**: --> False - **Comment**: 5.17.08 (develop) [code:29bc93] ~~~ commit 29bc93f4e457c64daa14bd22cf811aac8e16a1ba Author: Hung Nguyen Date: Mon Apr 24 14:20:53 2017 +0700 imm: Add more details to no dangling CcbErrorString [#2433] Add more details to no dangling CcbErrorString. ~~~ --- ** [tickets:#2433] imm: Add more details to no dangling CcbErrorString** **Status:** fixed **Milestone:** 5.17.08 **Created:** Wed Apr 19, 2017 06:29 AM UTC by Hung Nguyen **Last Updated:** Wed Apr 19, 2017 06:29 AM UTC **Owner:** Hung Nguyen ~~~ root@SC-1:~# immcfg -d test=1 error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Validation abort: No dangling validation failed ~~~ Add more details about the object name to CcbErrorString to provide more information for users. --- 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] #1765 ckpt : saCkptCheckpointOpen api call failed and returing SA_AIS_ERR_LIBRARY after couple of failover
- **status**: review --> fixed - **Milestone**: 5.0.2 --> 5.17.06 - **Comment**: 5.17.08 (develop) [code:bfebed] ~~~ commit bfebede5783121fc363f63536bbb89ba3355152e Author: Hoang Vo Date: Fri Apr 21 09:13:18 2017 +0700 cpd: to correct failover behavior of cpsv [#1765] Problem: In case failover multiple times, the cpnd is down for a moment so there is no cpnd opening specific checkpoint. This lead to retention timer is trigger. When cpnd is up again but has different pid so retention timer is not stoped. Repica is deleted at retention while its information still be in ckpt database. Fix: - Stop timer of removed node. - Update data in patricia trees (for retention value consistence). ~~~ 5.17.06 (release) [code:90973e] ~~~ commit 90973efa1f9b4002590450fd21e6b1a71f085296 Author: Hoang Vo Date: Fri Apr 21 09:13:18 2017 +0700 cpd: to correct failover behavior of cpsv [#1765] Problem: In case failover multiple times, the cpnd is down for a moment so there is no cpnd opening specific checkpoint. This lead to retention timer is trigger. When cpnd is up again but has different pid so retention timer is not stoped. Repica is deleted at retention while its information still be in ckpt database. Fix: - Stop timer of removed node. - Update data in patricia trees (for retention value consistence). ~~~ default (mecurial) [staging:edc930] ~~~ changeset: 8774:edc930fcc8fc user:Hoang Vo date:Fri Apr 21 09:32:25 2017 +0700 summary: cpd: to correct failover behavior of cpsv [#1765] ~~~ --- ** [tickets:#1765] ckpt : saCkptCheckpointOpen api call failed and returing SA_AIS_ERR_LIBRARY after couple of failover** **Status:** fixed **Milestone:** 5.17.06 **Created:** Fri Apr 15, 2016 06:26 AM UTC by Ritu Raj **Last Updated:** Tue Apr 04, 2017 01:34 PM UTC **Owner:** Vo Minh Hoang **Attachments:** - [ckpt_trace.tar.bz2](https://sourceforge.net/p/opensaf/tickets/1765/attachment/ckpt_trace.tar.bz2) (3.2 MB; application/x-bzip) setup: Changeset- 7436 Version - opensaf 5.0 FC 4 nodes configured with single PBE and a load of 30K objects * Issue observed : saCkptCheckpointOpen api call failed and returing SA_AIS_ERR_LIBRARY after couple of failover * Steps to reproduce: > Ran couple of failover and observed saCkptCheckpointOpen failed. > below is the snippet of agent trace: Apr 15 8:08:50.275115 cpa [28883:cpa_mds.c:0776] << cpa_mds_msg_sync_send: retval = 1 Apr 15 8:08:50.275128 cpa [28883:cpa_api.c:1043] T4 Cpa CkptOpen failed with return value:2,ckptHandle:63 Apr 15 8:08:50.275141 cpa [28883:cpa_api.c:1146] << **saCkptCheckpointOpen: API return code = 2** > Traces of both controllers and agent trace of payload is attached. --- 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] #2420 imm: IMMND on PL hangs when headless
- **status**: review --> fixed
- **Milestone**: 5.0.2 --> 5.17.06
- **Comment**:
5.17.08 (develop) [code:11325e]
~~~
commit 11325e3b7643c4d0500771ef7e022fcc47f1d31a
Author: Hung Nguyen
Date: Thu Apr 20 14:37:18 2017 +0700
imm: Use waitpid with WNOHANG to check for sync process and pbe process
[#2420]
Use waitpid with WNOHANG to check for sync process and pbe process.
The processes are checked before resending the intro message.
The intro message is only sent when those processes exit.
~~~
5.17.06 (release) [code:51233a]
~~~
commit 51233a54a11809ac48e27c043361b0ac95c5b71a
Author: Hung Nguyen
Date: Thu Apr 20 14:37:18 2017 +0700
imm: Use waitpid with WNOHANG to check for sync process and pbe process
[#2420]
Use waitpid with WNOHANG to check for sync process and pbe process.
The processes are checked before resending the intro message.
The intro message is only sent when those processes exit.
~~~
default (mecurial) [staging:2aa1ed]
~~~
changeset: 8773:2aa1edbd41e9
user: Hung Nguyen
date:Tue Apr 11 19:05:48 2017 +0700
summary: imm: Use waitpid with WNOHANG to check for sync process and pbe
process [#2420]
~~~
---
** [tickets:#2420] imm: IMMND on PL hangs when headless**
**Status:** fixed
**Milestone:** 5.17.06
**Created:** Tue Apr 11, 2017 07:13 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 11, 2017 12:11 PM UTC
**Owner:** Hung Nguyen
IMMND on PL hangs at waitpid() after coordinator removal.
When pbe process is in D State (Uninterruptible sleep (usually IO)), waitpid()
will be hung if WNOHANG is not specified.
~~~
LOG_WA("SC were absent and PBE appears hung, sending SIGKILL");
kill(cb->pbePid, SIGKILL);
waitpid(cb->pbePid, NULL, 0);
~~~
The bug is introduced by [#2296].
Solution: Use waitpid() with WNOHANG specified. Check for pbe/sync process
exiting before sending introduce message during headless.
---
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] #2433 imm: Add more details to no dangling CcbErrorString
--- ** [tickets:#2433] imm: Add more details to no dangling CcbErrorString** **Status:** accepted **Milestone:** 5.17.08 **Created:** Wed Apr 19, 2017 06:29 AM UTC by Hung Nguyen **Last Updated:** Wed Apr 19, 2017 06:29 AM UTC **Owner:** Hung Nguyen ~~~ root@SC-1:~# immcfg -d test=1 error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Validation abort: No dangling validation failed ~~~ Add more details about the object name to CcbErrorString to provide more information for users. --- 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] #2426 mds: MDS send failure
--- ** [tickets:#2426] mds: MDS send failure** **Status:** unassigned **Milestone:** 5.17.08 **Created:** Thu Apr 13, 2017 11:22 AM UTC by Hung Nguyen **Last Updated:** Thu Apr 13, 2017 11:22 AM UTC **Owner:** nobody **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
[tickets] [opensaf:tickets] #2401 imm: Check for response when using MDS SNDRSP
- **status**: review --> fixed
- **Milestone**: 5.0.2 --> 5.17.06
- **Comment**:
develop [code:754f34]
~~~
commit 754f34d5c94cdef78ecddd6d499ea96b6dfe9540
Author: Hung Nguyen
Date: Thu Apr 13 13:58:47 2017 +0700
imm: Check if response is NULL when sending MDS sync message [#2401]
Check if response is NULL when sending MDS sync message.
~~~
release [code:87616d]
~~~
commit 87616d21636686095e5779fe894ec438a2cff701
Author: Hung Nguyen
Date: Thu Apr 13 13:58:47 2017 +0700
imm: Check if response is NULL when sending MDS sync message [#2401]
Check if response is NULL when sending MDS sync message.
~~~
default (hg) [staging:8374cd]
~~~
changeset: 8766:8374cdffbd62
user: Hung Nguyen
date:Thu Apr 13 13:18:36 2017 +0700
summary: imm: Check if response is NULL when sending MDS sync message
[#2401]
~~~
---
** [tickets:#2401] imm: Check for response when using MDS SNDRSP**
**Status:** fixed
**Milestone:** 5.17.06
**Created:** Wed Mar 29, 2017 09:02 AM UTC by Hung Nguyen
**Last Updated:** Wed Apr 05, 2017 07:36 AM UTC
**Owner:** Hung Nguyen
Sometimes, ncsmds_api() returned NCSCC_RC_SUCCESS even when
NCSMDS_INFO.info.svc_send.info.sndrsp.o_rsp is NULL.
The library may crash when that happens
~~~
[New LWP 478]
[New LWP 480]
[New LWP 481]
[New LWP 482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/lib/opensaf/osafamfd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
Thread 1 (Thread 0x7f00cb1b5780 (LWP 478)):
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
No locals.
#1 0x7f00ca2e8ef1 in osaf_extended_name_lend (value=0x0,
name=0x7ffc65188f50) at src/base/osaf_extended_name.c:82
length =
#2 0x7f00c909a166 in saImmOmSearchNext_2
(searchHandle=searchHandle@entry=1490679334504883525,
objectName=objectName@entry=0x7ffc65188f50,
attributes=attributes@entry=0x7ffc65188ea0) at src/imm/agent/imma_om_api.cc:7580
objName = 0x0
rc =
#3 0x7f00cab8a7dc in immutil_saImmOmSearchNext_2
(searchHandle=1490679334504883525, objectName=0x7ffc65188f50,
attributes=0x7ffc65188ea0) at src/osaf/immutil/immutil.c:1817
rc =
nTries =
#4 0x5619eccab268 in avd_su_config_get
(sg_name="safSg=AmfDemo,safApp=AmfDemo2", sg=sg@entry=0x5619ed8e5b40) at
src/amf/amfd/su.cc:704
searchHandle = 1490679334504883525
su_name = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2"
className = 0x5619eccc1a33 "SaAmfSU"
su =
configAttributes = {0x5619ecccebde "saAmfSUType", 0x5619eccced2c
"saAmfSURank", 0x5619eccc1913 "saAmfSUHostedByNode", 0x5619ecccebfd
"saAmfSUHostNodeOrNodeGroup", 0x5619ecccec29 "saAmfSUFailover", 0x5619eccced11
"saAmfSUMaintenanceCampaign", 0x5619eccbb477 "saAmfSUAdminState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65188ea8}}
__FUNCTION__ = "avd_su_config_get"
error = SA_AIS_OK
rc =
tmp_su_name = {_opaque = {0 }}
attributes = 0x5619ed8e5c70
#5 0x5619ecc61711 in avd_sg_config_get (app_dn="safApp=AmfDemo2",
app=app@entry=0x5619ed8abc40) at src/amf/amfd/sg.cc:470
searchHandle = 1490679334503167364
dn = {_opaque = {29, 24947, 21350, 15719, 27969, 17510, 28005, 11375,
24947, 16742, 28784, 16701, 26221, 25924, 28525, 50, 0 }}
className = 0x5619eccc1a23 "SaAmfSG"
configAttributes = {0x5619eccc84e6 "saAmfSGType", 0x5619eccc8516
"saAmfSGSuHostNodeGroup", 0x5619eccc84f2 "saAmfSGAutoRepair", 0x5619eccc8504
"saAmfSGAutoAdjust", 0x5619eccc857c "saAmfSGNumPrefActiveSUs", 0x5619eccc8594
"saAmfSGNumPrefStandbySUs", 0x5619eccc85ad "saAmfSGNumPrefInserviceSUs",
0x5619eccc85c8 "saAmfSGNumPrefAssignedSUs", 0x5619eccc85e2
"saAmfSGMaxActiveSIsperSU", 0x5619eccc85fb "saAmfSGMaxStandbySIsperSU",
0x5619eccc8615 "saAmfSGAutoAdjustProb", 0x5619eccc862b
"saAmfSGCompRestartProb", 0x5619eccc8642 "saAmfSGCompRestartMax",
0x5619eccc8658 "saAmfSGSuRestartProb", 0x5619eccc866d "saAmfSGSuRestartMax",
0x5619eccc8313 "saAmfSGAdminState", 0x5619eccc833e "osafAmfSGFsmState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
sg = 0x5619ed8e5b40
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65189108}}
__FUNCTION
[tickets] [opensaf:tickets] #2408 IMM: Fix cppcheck 1.78 memory leak error at tools
- **status**: review --> fixed - **Comment**: develop [code:021003] commit 021003cbe581ae0eebd29981a2654f6f1f7f3095 Author: Hieu Nguyen Date: Wed Apr 12 12:45:53 2017 +0700 imm: Fixed memory leak in imm_cfg.c [#2408] Fixed memory leak in unique_admiOwner() function of imm_cfg.c file release [code:8d7687] ~~~ commit 8d76876f236e4116bcca9a2f7ee67e6f1dfc7ae8 Author: Hieu Nguyen Date: Wed Apr 12 12:45:53 2017 +0700 imm: Fixed memory leak in imm_cfg.c [#2408] Fixed memory leak in unique_admiOwner() function of imm_cfg.c file ~~~ default (hg) [staging:69b0ff] ~~~ changeset: 8762:69b0ffd9694b user:Hieu Nguyen date:Wed Apr 12 13:26:51 2017 +0700 summary: imm: Fixed memory leak in imm_cfg.c file [#2408] ~~~ --- ** [tickets:#2408] IMM: Fix cppcheck 1.78 memory leak error at tools** **Status:** fixed **Milestone:** 5.17.08 **Created:** Mon Apr 03, 2017 02:16 AM UTC by Hieu Nguyen **Last Updated:** Mon Apr 10, 2017 01:40 PM UTC **Owner:** Hieu Nguyen opensaf-staging/src/imm/tools/imm_cfg.c:861]: (error) Memory leak: unique_adminOwner --- 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] #2420 imm: IMMND on PL hangs when headless
- **status**: accepted --> review
---
** [tickets:#2420] imm: IMMND on PL hangs when headless**
**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Apr 11, 2017 07:13 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 11, 2017 07:13 AM UTC
**Owner:** Hung Nguyen
IMMND on PL hangs at waitpid() after coordinator removal.
When pbe process is in D State (Uninterruptible sleep (usually IO)), waitpid()
will be hung if WNOHANG is not specified.
~~~
LOG_WA("SC were absent and PBE appears hung, sending SIGKILL");
kill(cb->pbePid, SIGKILL);
waitpid(cb->pbePid, NULL, 0);
~~~
The bug is introduced by [#2296].
Solution: Use waitpid() with WNOHANG specified. Check for pbe/sync process
exiting before sending introduce message during headless.
---
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] #2422 imm: ObjectMutation is added to sPbeRtMutations even when validation for duplicate values fails
---
** [tickets:#2422] imm: ObjectMutation is added to sPbeRtMutations even when
validation for duplicate values fails**
**Status:** assigned
**Milestone:** 5.0.2
**Created:** Tue Apr 11, 2017 10:15 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 11, 2017 10:15 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[SC-1_log.7z](https://sourceforge.net/p/opensaf/tickets/2422/attachment/SC-1_log.7z)
(23.3 kB; application/octet-stream)
~~~
# immlist -c Test
<< Test - CONFIG >>
test : SA_STRING_T [1] {RDN, CONFIG, INITIALIZED}
list : SA_UINT32_T [0..*] {RUNTIME, CACHED, PERSISTENT, MULTI_VALUE,
NO_DUPLICATES}
~~~
Reproduce:
1. Create object
2. Add value=10 to 'list' attribute => SA_AIS_OK
3. Add value=10 to 'list' attribute => ERR_INVALID_PARAM
4. Add value=9 to 'list' attribute => ERR_TRY_AGAIN
PBE process is then killed by IMMND
~~~
17:08:09 SC-1 osafimmnd[441]: NO ERR_INVALID_PARAM: multivalued attr 'list'
with NO_DUPLICATES yet duplicate values provided in rta-update call.
Object:'test=1'.
17:08:09 SC-1 osafimmnd[441]: WA Got error on non local rt object update err: 7
17:08:19 SC-1 osafimmnd[441]: NO Implementer disconnected 9 <201, 2010f>
(xhunngu)
17:08:24 SC-1 osafimmnd[441]: NO Implementer connected: 10 (xhunngu) <202,
2010f>
17:08:34 SC-1 osafimmnd[441]: NO Implementer disconnected 10 <202, 2010f>
(xhunngu)
17:10:10 SC-1 osafimmnd[441]: WA IMMND - Client 201 went down so no response
17:10:40 SC-1 osafimmnd[441]: WA PBE process 463 appears stuck on runtime data
handling - sending SIGTERM
17:10:40 SC-1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db handle
17:10:40 SC-1 osafimmpbed: IN IMM PBE process EXITING...
~~~
Attached is 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
[tickets] [opensaf:tickets] #2420 imm: IMMND on PL hangs when headless
---
** [tickets:#2420] imm: IMMND on PL hangs when headless**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Tue Apr 11, 2017 07:13 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 11, 2017 07:13 AM UTC
**Owner:** Hung Nguyen
IMMND on PL hangs at waitpid() after coordinator removal.
When pbe process is in D State (Uninterruptible sleep (usually IO)), waitpid()
will be hung if WNOHANG is not specified.
~~~
LOG_WA("SC were absent and PBE appears hung, sending SIGKILL");
kill(cb->pbePid, SIGKILL);
waitpid(cb->pbePid, NULL, 0);
~~~
The bug is introduced by [#2296].
Solution: Use waitpid() with WNOHANG specified. Check for pbe/sync process
exiting before sending introduce message during headless.
---
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] #2418 imm: Info of dead IMMND remains in standby IMMD
--- ** [tickets:#2418] imm: Info of dead IMMND remains in standby IMMD** **Status:** accepted **Milestone:** 5.0.2 **Created:** Mon Apr 10, 2017 10:23 AM UTC by Hung Nguyen **Last Updated:** Mon Apr 10, 2017 10:23 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2418/attachment/log.tgz) (149.4 kB; application/x-compressed) When Standby IMMD is up at the same time with a IMMND exiting, the info of that IMMND might not be removed from **immnd_tree** of the Standby IMMD. Details of the problem is explained in the sequence diagram below [sequence diagram](http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCBhAKgWgJIFl8ARAKFElnhCWQGVMAhPQ0kkAIwHsAPZTgNwCmYOo2bFkAYjCCAJgC5kRAPIB1AHLJBQmgDMwnALbIC+dUT4JkCTrMHIAGiRJdeA4aKamii3AigoxLQAOgh+Acj4DOjI1LLIAM6CgdHIBgA29hCcdBBx7ACezvReLMjYAHxoWOIW8uic6bIJBQgwaYIAjgCuggkQziQYON7lVSW1ig1NLW0dCcCcCEmhEAAW9qbmyOlQ-chQbenddgnI65uE20vWtvZOzhw8fEIiw7VSMgpKapragnoDMYthYbjY7I5nK4Xh53t4ADQTbyKTAbExXCx7DqGdzxfRGaojMrsbooGSGECHM6HTy1IA) SC-5 was Active, SC-2 was Standby, IMMND on SC-1 was exiting ~~~ 18:35:03 SC-1 osafimmnd[441]: exiting for shutdown 18:35:03 SC-2 osafrded[413]: NO RDE role set to STANDBY 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:568511936070075) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:567412424442298) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:566312912814523) 18:35:03 SC-2 osafimmd[430]: NO MDS event from svc_id 25 (change:3, dest:565213401186744) 18:35:03 SC-5 osafimmd[433]: NO MDS event from svc_id 25 (change:4, dest:564113889558969) ~~~ Down event for IMMND@SC-1 was received on SC-5 but not on SC-2. **The symptoms:** 1. If the down IMMND is the corrdinator, that results in when that Standby IMMD becomes Active, it fails to elect new coordinator as there's already a coordinator in the **immnd_tree**. ~~~ 18:35:11 SC-2 osafimmd[430]: WA IMMND coordinator at 2050f apparently crashed => electing new coord ~~~ No more logs about newly elected coordinator were printed out. 2. When IMMND@SC-1 is up again, it will fail to introduce to IMMD because the IMMD already have IMMND@SC-1 in **immnd_tree** with a wrong epoch. ~~~ 18:35:29 SC-1 osafimmnd[441]: NO SERVER STATE: IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING 18:35:29 SC-1 osafimmnd[441]: NO This IMMND is now the NEW Coord 18:35:29 SC-1 osafimmnd[441]: ER 3 > 0, exiting ~~~ --- 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] #2401 imm: Check for response when using MDS SNDRSP
- **status**: accepted --> review
---
** [tickets:#2401] imm: Check for response when using MDS SNDRSP**
**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Mar 29, 2017 09:02 AM UTC by Hung Nguyen
**Last Updated:** Wed Mar 29, 2017 09:02 AM UTC
**Owner:** Hung Nguyen
Sometimes, ncsmds_api() returned NCSCC_RC_SUCCESS even when
NCSMDS_INFO.info.svc_send.info.sndrsp.o_rsp is NULL.
The library may crash when that happens
~~~
[New LWP 478]
[New LWP 480]
[New LWP 481]
[New LWP 482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/lib/opensaf/osafamfd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
Thread 1 (Thread 0x7f00cb1b5780 (LWP 478)):
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
No locals.
#1 0x7f00ca2e8ef1 in osaf_extended_name_lend (value=0x0,
name=0x7ffc65188f50) at src/base/osaf_extended_name.c:82
length =
#2 0x7f00c909a166 in saImmOmSearchNext_2
(searchHandle=searchHandle@entry=1490679334504883525,
objectName=objectName@entry=0x7ffc65188f50,
attributes=attributes@entry=0x7ffc65188ea0) at src/imm/agent/imma_om_api.cc:7580
objName = 0x0
rc =
#3 0x7f00cab8a7dc in immutil_saImmOmSearchNext_2
(searchHandle=1490679334504883525, objectName=0x7ffc65188f50,
attributes=0x7ffc65188ea0) at src/osaf/immutil/immutil.c:1817
rc =
nTries =
#4 0x5619eccab268 in avd_su_config_get
(sg_name="safSg=AmfDemo,safApp=AmfDemo2", sg=sg@entry=0x5619ed8e5b40) at
src/amf/amfd/su.cc:704
searchHandle = 1490679334504883525
su_name = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2"
className = 0x5619eccc1a33 "SaAmfSU"
su =
configAttributes = {0x5619ecccebde "saAmfSUType", 0x5619eccced2c
"saAmfSURank", 0x5619eccc1913 "saAmfSUHostedByNode", 0x5619ecccebfd
"saAmfSUHostNodeOrNodeGroup", 0x5619ecccec29 "saAmfSUFailover", 0x5619eccced11
"saAmfSUMaintenanceCampaign", 0x5619eccbb477 "saAmfSUAdminState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65188ea8}}
__FUNCTION__ = "avd_su_config_get"
error = SA_AIS_OK
rc =
tmp_su_name = {_opaque = {0 }}
attributes = 0x5619ed8e5c70
#5 0x5619ecc61711 in avd_sg_config_get (app_dn="safApp=AmfDemo2",
app=app@entry=0x5619ed8abc40) at src/amf/amfd/sg.cc:470
searchHandle = 1490679334503167364
dn = {_opaque = {29, 24947, 21350, 15719, 27969, 17510, 28005, 11375,
24947, 16742, 28784, 16701, 26221, 25924, 28525, 50, 0 }}
className = 0x5619eccc1a23 "SaAmfSG"
configAttributes = {0x5619eccc84e6 "saAmfSGType", 0x5619eccc8516
"saAmfSGSuHostNodeGroup", 0x5619eccc84f2 "saAmfSGAutoRepair", 0x5619eccc8504
"saAmfSGAutoAdjust", 0x5619eccc857c "saAmfSGNumPrefActiveSUs", 0x5619eccc8594
"saAmfSGNumPrefStandbySUs", 0x5619eccc85ad "saAmfSGNumPrefInserviceSUs",
0x5619eccc85c8 "saAmfSGNumPrefAssignedSUs", 0x5619eccc85e2
"saAmfSGMaxActiveSIsperSU", 0x5619eccc85fb "saAmfSGMaxStandbySIsperSU",
0x5619eccc8615 "saAmfSGAutoAdjustProb", 0x5619eccc862b
"saAmfSGCompRestartProb", 0x5619eccc8642 "saAmfSGCompRestartMax",
0x5619eccc8658 "saAmfSGSuRestartProb", 0x5619eccc866d "saAmfSGSuRestartMax",
0x5619eccc8313 "saAmfSGAdminState", 0x5619eccc833e "osafAmfSGFsmState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
sg = 0x5619ed8e5b40
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65189108}}
__FUNCTION__ = "avd_sg_config_get"
error = SA_AIS_OK
rc =
attributes = 0x5619ed8e4370
#6 0x5619ecbf8981 in avd_app_config_get () at src/amf/amfd/app.cc:460
searchHandle = 1490679334315192083
dn = {_opaque = {15, 24947, 16742, 28784, 16701, 26221, 25924, 28525,
50, 0 }}
className = 0x5619eccb9938 "SaAmfApplication"
configAttributes = {0x5619eccb987f "saAmfAppType", 0x5619eccb98cd
"saAmfApplicationAdminState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc651893b8}}
app = 0x5619ed8abc40
__FUNCTION__ = "avd_app_config
[tickets] [opensaf:tickets] #2401 imm: Check for response when using MDS SNDRSP
---
** [tickets:#2401] imm: Check for response when using MDS SNDRSP**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Wed Mar 29, 2017 09:02 AM UTC by Hung Nguyen
**Last Updated:** Wed Mar 29, 2017 09:02 AM UTC
**Owner:** Hung Nguyen
Sometimes, ncsmds_api() returned NCSCC_RC_SUCCESS even when
NCSMDS_INFO.info.svc_send.info.sndrsp.o_rsp is NULL.
The library may crash when that happens
~~~
[New LWP 478]
[New LWP 480]
[New LWP 481]
[New LWP 482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/lib/opensaf/osafamfd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
Thread 1 (Thread 0x7f00cb1b5780 (LWP 478)):
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
No locals.
#1 0x7f00ca2e8ef1 in osaf_extended_name_lend (value=0x0,
name=0x7ffc65188f50) at src/base/osaf_extended_name.c:82
length =
#2 0x7f00c909a166 in saImmOmSearchNext_2
(searchHandle=searchHandle@entry=1490679334504883525,
objectName=objectName@entry=0x7ffc65188f50,
attributes=attributes@entry=0x7ffc65188ea0) at src/imm/agent/imma_om_api.cc:7580
objName = 0x0
rc =
#3 0x7f00cab8a7dc in immutil_saImmOmSearchNext_2
(searchHandle=1490679334504883525, objectName=0x7ffc65188f50,
attributes=0x7ffc65188ea0) at src/osaf/immutil/immutil.c:1817
rc =
nTries =
#4 0x5619eccab268 in avd_su_config_get
(sg_name="safSg=AmfDemo,safApp=AmfDemo2", sg=sg@entry=0x5619ed8e5b40) at
src/amf/amfd/su.cc:704
searchHandle = 1490679334504883525
su_name = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2"
className = 0x5619eccc1a33 "SaAmfSU"
su =
configAttributes = {0x5619ecccebde "saAmfSUType", 0x5619eccced2c
"saAmfSURank", 0x5619eccc1913 "saAmfSUHostedByNode", 0x5619ecccebfd
"saAmfSUHostNodeOrNodeGroup", 0x5619ecccec29 "saAmfSUFailover", 0x5619eccced11
"saAmfSUMaintenanceCampaign", 0x5619eccbb477 "saAmfSUAdminState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65188ea8}}
__FUNCTION__ = "avd_su_config_get"
error = SA_AIS_OK
rc =
tmp_su_name = {_opaque = {0 }}
attributes = 0x5619ed8e5c70
#5 0x5619ecc61711 in avd_sg_config_get (app_dn="safApp=AmfDemo2",
app=app@entry=0x5619ed8abc40) at src/amf/amfd/sg.cc:470
searchHandle = 1490679334503167364
dn = {_opaque = {29, 24947, 21350, 15719, 27969, 17510, 28005, 11375,
24947, 16742, 28784, 16701, 26221, 25924, 28525, 50, 0 }}
className = 0x5619eccc1a23 "SaAmfSG"
configAttributes = {0x5619eccc84e6 "saAmfSGType", 0x5619eccc8516
"saAmfSGSuHostNodeGroup", 0x5619eccc84f2 "saAmfSGAutoRepair", 0x5619eccc8504
"saAmfSGAutoAdjust", 0x5619eccc857c "saAmfSGNumPrefActiveSUs", 0x5619eccc8594
"saAmfSGNumPrefStandbySUs", 0x5619eccc85ad "saAmfSGNumPrefInserviceSUs",
0x5619eccc85c8 "saAmfSGNumPrefAssignedSUs", 0x5619eccc85e2
"saAmfSGMaxActiveSIsperSU", 0x5619eccc85fb "saAmfSGMaxStandbySIsperSU",
0x5619eccc8615 "saAmfSGAutoAdjustProb", 0x5619eccc862b
"saAmfSGCompRestartProb", 0x5619eccc8642 "saAmfSGCompRestartMax",
0x5619eccc8658 "saAmfSGSuRestartProb", 0x5619eccc866d "saAmfSGSuRestartMax",
0x5619eccc8313 "saAmfSGAdminState", 0x5619eccc833e "osafAmfSGFsmState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
sg = 0x5619ed8e5b40
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc65189108}}
__FUNCTION__ = "avd_sg_config_get"
error = SA_AIS_OK
rc =
attributes = 0x5619ed8e4370
#6 0x5619ecbf8981 in avd_app_config_get () at src/amf/amfd/app.cc:460
searchHandle = 1490679334315192083
dn = {_opaque = {15, 24947, 16742, 28784, 16701, 26221, 25924, 28525,
50, 0 }}
className = 0x5619eccb9938 "SaAmfApplication"
configAttributes = {0x5619eccb987f "saAmfAppType", 0x5619eccb98cd
"saAmfApplicationAdminState", 0x0}
t_ = {trace_leave_called = false, file_ = 0x0, function_ = 0x0}
searchParam = {searchOneAttr = {attrName = 0x5619eccb998c
"SaImmAttrClassName", attrValueType = SA_IMM_ATTR_SASTRINGT, attrValue =
0x7ffc651893b8}}
app = 0x5619ed8abc40
__FUNCTION__ = "avd_app_config_get"
error = SA_AIS_ERR
[tickets] [opensaf:tickets] #2367 imm: Improve ccb error string handling
--- ** [tickets:#2367] imm: Improve ccb error string handling** **Status:** accepted **Milestone:** next **Created:** Mon Mar 13, 2017 03:34 AM UTC by Hung Nguyen **Last Updated:** Mon Mar 13, 2017 03:34 AM UTC **Owner:** Hung Nguyen * Use ::setCcbErrorString in ::ccbObjDelContinuation and::ccbCompletedContinuation instead of working directly with ccb->mErrorStrings * Only store error strings on originating node where OM client resides. --- 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.-- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2323 imm: CCB operations fail after SC absence (Headless)
- **status**: review --> fixed - **Comment**: default (5.2) [staging:8cbe1c] changeset: 8669:8cbe1c0a3335 user: Hung Nguyen date:Wed Mar 08 13:14:20 2017 +0700 summary: imm: Sync latest ccb-id to sync clients [#2323] opensaf-5.1.x [staging:b642a1] changeset: 8670:b642a1336cf3 user: Hung Nguyen date:Wed Mar 08 13:35:24 2017 +0700 summary: imm: Sync latest ccb-id to sync clients [#2323] opensaf-5.0.x [staging:bf11d1] changeset: 8671:bf11d1e7720a user: Hung Nguyen date:Wed Mar 08 13:35:24 2017 +0700 summary: imm: Sync latest ccb-id to sync clients [#2323] --- ** [tickets:#2323] imm: CCB operations fail after SC absence (Headless)** **Status:** fixed **Milestone:** 5.0.2 **Created:** Thu Feb 23, 2017 03:36 PM UTC by Hung Nguyen **Last Updated:** Wed Mar 01, 2017 08:53 AM UTC **Owner:** Hung Nguyen **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2323/attachment/logs_n_traces.tgz) (658.6 kB; application/gzip) Reproduce steps: ~~~ 1. Start SC-1 2. Commit some CCBs # immcfg -c Test test=0 # immcfg -c Test test=1 # immcfg -c Test test=2 # immcfg -c Test test=3 3. Start PL-3 4. Restart SC-1 5. When SC-1 is back, it fails to add operations to CCB # immcfg -c Test test=10 error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state ~~~ **cb->mLatestCcbId** was not updated on PL-3 when it joined the cluster so it still had value of zero. When SC-1 was back from headless, IMMND on PL-3 sent re-introduce message to IMMD on SC-1 with **cb->mLatestCcbId = 0**. IMMD failed to update **cb->ccb_id_count** so when new CCB is created, it will start from **0+1** instead of **mLatestCcbId + 1**. That results in the conflict with the CCB in **sCcbVector** and the CCB operation failure. Attached is logs and traces. --- 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.-- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()
[staging:416da1]
changeset: 8668:416da1e8fced
user:Hung Nguyen
date:Wed Mar 08 10:34:34 2017 +0700
summary: imm: Update imm minorVersion in apitest [#2329]
---
** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18
after calling saImmOmInitiailize()**
**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Tue Mar 07, 2017 12:18 PM UTC
**Owner:** Neelakanta Reddy
Changeset: 8634 5.2.FC
SLES four node cluster.
Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()
Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver
Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}
Expected: Output parameter should be filled with version actually supported by
IMM service.
---
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.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2323 imm: CCB operations fail after SC absence
- **status**: accepted --> review --- ** [tickets:#2323] imm: CCB operations fail after SC absence** **Status:** review **Milestone:** 5.0.2 **Created:** Thu Feb 23, 2017 03:36 PM UTC by Hung Nguyen **Last Updated:** Thu Feb 23, 2017 03:36 PM UTC **Owner:** Hung Nguyen **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2323/attachment/logs_n_traces.tgz) (658.6 kB; application/gzip) Reproduce steps: ~~~ 1. Start SC-1 2. Commit some CCBs # immcfg -c Test test=0 # immcfg -c Test test=1 # immcfg -c Test test=2 # immcfg -c Test test=3 3. Start PL-3 4. Restart SC-1 5. When SC-1 is back, it fails to add operations to CCB # immcfg -c Test test=10 error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state ~~~ **cb->mLatestCcbId** was not updated on PL-3 when it joined the cluster so it still had value of zero. When SC-1 was back from headless, IMMND on PL-3 sent re-introduce message to IMMD on SC-1 with **cb->mLatestCcbId = 0**. IMMD failed to update **cb->ccb_id_count** so when new CCB is created, it will start from **0+1** instead of **mLatestCcbId + 1**. That results in the conflict with the CCB in **sCcbVector** and the CCB operation failure. Attached is logs and traces. --- 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] #2323 imm: CCB operations fail after SC absence
--- ** [tickets:#2323] imm: CCB operations fail after SC absence** **Status:** accepted **Milestone:** 5.0.2 **Created:** Thu Feb 23, 2017 03:36 PM UTC by Hung Nguyen **Last Updated:** Thu Feb 23, 2017 03:36 PM UTC **Owner:** Hung Nguyen **Attachments:** - [logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2323/attachment/logs_n_traces.tgz) (658.6 kB; application/gzip) Reproduce steps: ~~~ 1. Start SC-1 2. Commit some CCBs # immcfg -c Test test=0 # immcfg -c Test test=1 # immcfg -c Test test=2 # immcfg -c Test test=3 3. Start PL-3 4. Restart SC-1 5. When SC-1 is back, it fails to add operations to CCB # immcfg -c Test test=10 error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) OI reports: IMM: Resource abort: CCB is not in an expected state ~~~ **cb->mLatestCcbId** was not updated on PL-3 when it joined the cluster so it still had value of zero. When SC-1 was back from headless, IMMND on PL-3 sent re-introduce message to IMMD on SC-1 with **cb->mLatestCcbId = 0**. IMMD failed to update **cb->ccb_id_count** so when new CCB is created, it will start from **0+1** instead of **mLatestCcbId + 1**. That results in the conflict with the CCB in **sCcbVector** and the CCB operation failure. Attached is logs and traces. --- 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] #2309 imm: IMMNDs on PLs fail to discard local OI when headless
- **status**: review --> fixed - **Comment**: default(5.2) [staging:0c6da9] changeset: 8605:0c6da910d0d4 user: Hung Nguyen date:Wed Feb 22 16:50:02 2017 +0700 summary: imm: Cleanup orphaned implementers and admowners when headless [#2309] opensaf-5.1.x [staging:f667c9] changeset: 8606:f667c97dab51 user: Hung Nguyen date:Wed Feb 22 16:51:55 2017 +0700 summary: imm: Cleanup orphaned implementers and admowners when headless [#2309] opensaf-5.0.x [staging:adc96b] changeset: 8607:adc96bde4277 user: Hung Nguyen date:Wed Feb 22 16:52:52 2017 +0700 summary: imm: Cleanup orphaned implementers and admowners when headless [#2309] --- ** [tickets:#2309] imm: IMMNDs on PLs fail to discard local OI when headless** **Status:** fixed **Milestone:** 5.0.2 **Created:** Wed Feb 15, 2017 04:22 AM UTC by Hung Nguyen **Last Updated:** Fri Feb 17, 2017 08:09 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2309/attachment/log.tgz) (251.2 kB; application/x-compressed) When killing a PL-based OI right before cluster goes headless, IMMND fails to discard the implementer. The implementer is only discarded locally, not really discarded. That results in the implementer is stuck in "dying" state, and any attempt to set the implementer will get ERR_TRY_AGAIN. ~~~ :::sql Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO Implementer connected: 6 (xhunngu) <29, 2030f> Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO implementer for class 'Test' is xhunngu => class extent is safe. Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer locally disconnected. Marking it as doomed 6 <29, 2030f> (xhunngu) Feb 15 10:57:20 PL-3 osafimmnd[1127]: WA SC Absence IS allowed:1800 IMMD service is DOWN Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 1 <0, 2010f(down)> (safLogService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 2 <0, 2010f(down)> (@safLogService_appl) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 3 <0, 2010f(down)> (safClmService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 4 <0, 2010f(down)> (safAmfService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Impl Discarded node 2010f Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO MDS unregisterede. sleeping ... Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Sleep done registering IMMND with MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO SUCCESS IN REGISTERING IMMND WITH MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:22 PL-3 osafclmna[1136]: NO Starting to promote this node to a system controller Feb 15 10:57:24 PL-3 osafamfnd[1144]: WA AMF director unexpectedly crashed Feb 15 10:57:24 PL-3 osafamfnd[1144]: NO Checking 'safSu=PL-3,safSg=NoRed,safApp=OpenSAF' for pending messages Feb 15 10:57:26 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:27 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:27 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:28 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 ~~~ --- 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] #2296 imm: IMMND on payload crashes after SC absence
- **status**: review --> fixed - **Comment**: default (5.2) [staging:21aab7] changeset: 8593:21aab7e03190 user: Hung Nguyen date:Tue Feb 21 14:46:41 2017 +0700 summary: imm: Fix problems with removing coordinator role when cluster goes headless [#2296] opensaf-5.1.x [staging:15aceb] changeset: 8594:15aceb2ce9dd user: Hung Nguyen date:Tue Feb 21 14:49:28 2017 +0700 summary: imm: Fix problems with removing coordinator role when cluster goes headless [#2296] opensaf-5.0.x [staging:78b886] changeset: 8595:78b886a029c4 user: Hung Nguyen date:Tue Feb 21 14:49:28 2017 +0700 summary: imm: Fix problems with removing coordinator role when cluster goes headless [#2296] --- ** [tickets:#2296] imm: IMMND on payload crashes after SC absence** **Status:** fixed **Milestone:** 5.0.2 **Created:** Thu Feb 09, 2017 08:44 AM UTC by Hung Nguyen **Last Updated:** Fri Feb 10, 2017 07:27 AM UTC **Owner:** Hung Nguyen **Attachments:** - [logs.tgz](https://sourceforge.net/p/opensaf/tickets/2296/attachment/logs.tgz) (5.2 MB; application/x-compressed) Removal of IMMND coordinator was introduced in [#1692]. Some cleanup actions are delayed until **immnd_proc_server()** is executed. In case the cluster is back from headless too fast, **immnd_proc_server()** will not be executed and IMMND will crashes later. ~~~ 2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO Announce sync, epoch:28 2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO SERVER STATE: IMM_SERVER_READY --> IMM_SERVER_SYNC_SERVER 2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO NODE STATE-> IMM_NODE_R_AVAILABLE 2017-02-05 21:36:41 PL-5 osafimmloadd: NO Sync starting 2017-02-05 21:36:42 PL-5 osafdtmd[393]: NO Lost contact with 'SC-1' 2017-02-05 21:36:42 PL-5 osafimmnd[406]: WA Director Service in NOACTIVE state - fevs replies pending:16 fevs highest processed:13154 2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA SC Absence IS allowed:900 IMMD service is DOWN 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:290002050f sv_id:26 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:14d0002050f sv_id:26 2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA Postponing hard delete of admin owner with id:41 when imm is not writable state 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1530002050f sv_id:27 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 147 <339, 2050f> (OpenSafImmPBE) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1550002050f sv_id:26 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 144 <0, 2010f(down)> (safLogService) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 145 <0, 2010f(down)> (@safLogService_appl) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 146 <0, 2010f(down)> (@OpenSafImmReplicatorA) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 143 <0, 2010f(down)> (safClmService) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 142 <0, 2010f(down)> (safAmfService) 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Impl Discarded node 2010f 2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO MDS unregisterede. sleeping ... 2017-02-05 21:36:43 PL-5 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting 2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO Sleep done registering IMMND with MDS 2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO SUCCESS IN REGISTERING IMMND WITH MDS 2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO MDS: mds_register_callback: dest 2050f01e8 already exist 2017-02-05 21:36:44 PL-5 osafimmnd[406]: WA IMMND - Client Node Get Failed for cli_hdl:1464583980303 2017-02-05 21:36:45 PL-5 osafdtmd[393]: NO Established contact with 'SC-1' 2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA MDS Send Failed 2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA Error code 2 returned for message type 17 - ignoring 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO IMMD service is UP ... ScAbsenseAllowed?:900 introduced?:2 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me highestProcessed:13154 highestReceived:13154 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Epoch set to 29 in ImmModel 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me highestProcessed:13154 highestReceived:13154 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO ERR_BAD_HANDLE: admin owner id 42 does not exist 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Implementer connected: 149 (OpenSafImmPBE) <0, 2040f> 2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me highestProcessed:13157 highestReceived:13158 2017-02-05 21:36:49 PL-5 osafimmnd[406]: ER Node is in a state that cannot accept start of sync, will terminate ~~~ IMMND failed to revert back to IMM_SERVER_READY/IMM_NO
[tickets] [opensaf:tickets] #2309 imm: IMMNDs on PLs fail to discard local OI when headless
- **status**: accepted --> review --- ** [tickets:#2309] imm: IMMNDs on PLs fail to discard local OI when headless** **Status:** review **Milestone:** 5.0.2 **Created:** Wed Feb 15, 2017 04:22 AM UTC by Hung Nguyen **Last Updated:** Wed Feb 15, 2017 04:22 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2309/attachment/log.tgz) (251.2 kB; application/x-compressed) When killing a PL-based OI right before cluster goes headless, IMMND fails to discard the implementer. The implementer is only discarded locally, not really discarded. That results in the implementer is stuck in "dying" state, and any attempt to set the implementer will get ERR_TRY_AGAIN. ~~~ :::sql Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO Implementer connected: 6 (xhunngu) <29, 2030f> Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO implementer for class 'Test' is xhunngu => class extent is safe. Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer locally disconnected. Marking it as doomed 6 <29, 2030f> (xhunngu) Feb 15 10:57:20 PL-3 osafimmnd[1127]: WA SC Absence IS allowed:1800 IMMD service is DOWN Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 1 <0, 2010f(down)> (safLogService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 2 <0, 2010f(down)> (@safLogService_appl) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 3 <0, 2010f(down)> (safClmService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 4 <0, 2010f(down)> (safAmfService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Impl Discarded node 2010f Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO MDS unregisterede. sleeping ... Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Sleep done registering IMMND with MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO SUCCESS IN REGISTERING IMMND WITH MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:22 PL-3 osafclmna[1136]: NO Starting to promote this node to a system controller Feb 15 10:57:24 PL-3 osafamfnd[1144]: WA AMF director unexpectedly crashed Feb 15 10:57:24 PL-3 osafamfnd[1144]: NO Checking 'safSu=PL-3,safSg=NoRed,safApp=OpenSAF' for pending messages Feb 15 10:57:26 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:27 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:27 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:28 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 ~~~ --- 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] #2309 imm: IMMNDs on PLs fail to discard local OI when headless
--- ** [tickets:#2309] imm: IMMNDs on PLs fail to discard local OI when headless** **Status:** accepted **Milestone:** 5.0.2 **Created:** Wed Feb 15, 2017 04:22 AM UTC by Hung Nguyen **Last Updated:** Wed Feb 15, 2017 04:22 AM UTC **Owner:** Hung Nguyen **Attachments:** - [log.tgz](https://sourceforge.net/p/opensaf/tickets/2309/attachment/log.tgz) (251.2 kB; application/x-compressed) When killing a PL-based OI right before cluster goes headless, IMMND fails to discard the implementer. The implementer is only discarded locally, not really discarded. That results in the implementer is stuck in "dying" state, and any attempt to set the implementer will get ERR_TRY_AGAIN. ~~~ :::sql Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO Implementer connected: 6 (xhunngu) <29, 2030f> Feb 15 10:56:58 PL-3 osafimmnd[1127]: NO implementer for class 'Test' is xhunngu => class extent is safe. Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer locally disconnected. Marking it as doomed 6 <29, 2030f> (xhunngu) Feb 15 10:57:20 PL-3 osafimmnd[1127]: WA SC Absence IS allowed:1800 IMMD service is DOWN Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 1 <0, 2010f(down)> (safLogService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 2 <0, 2010f(down)> (@safLogService_appl) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 3 <0, 2010f(down)> (safClmService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Implementer disconnected 4 <0, 2010f(down)> (safAmfService) Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO Impl Discarded node 2010f Feb 15 10:57:20 PL-3 osafimmnd[1127]: NO MDS unregisterede. sleeping ... Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Sleep done registering IMMND with MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO SUCCESS IN REGISTERING IMMND WITH MDS Feb 15 10:57:21 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:22 PL-3 osafclmna[1136]: NO Starting to promote this node to a system controller Feb 15 10:57:24 PL-3 osafamfnd[1144]: WA AMF director unexpectedly crashed Feb 15 10:57:24 PL-3 osafamfnd[1144]: NO Checking 'safSu=PL-3,safSg=NoRed,safApp=OpenSAF' for pending messages Feb 15 10:57:26 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:27 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 Feb 15 10:57:27 PL-3 osafimmnd[1127]: WA MDS Send Failed to service:IMMD rc:2 Feb 15 10:57:28 PL-3 osafimmnd[1127]: NO Re-introduce-me highestProcessed:653 highestReceived:653 ~~~ --- 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] #2276 imm: Update NO_DANGLING document with information about ATTR_DN
- **status**: review --> fixed - **Comment**: default (5.2) [staging:38f9e7] changeset: 8571:38f9e7f6ec5b user: Hung Nguyen date:Fri Feb 10 16:49:15 2017 +0700 summary: imm: Update NO_DANGLING document with information about ATTR_DN [#2276] opensaf-5.1.x [staging:c7e402] changeset: 8572:c7e402c9e46b user: Hung Nguyen date:Fri Feb 10 16:53:48 2017 +0700 summary: imm: Update NO_DANGLING document with information about ATTR_DN [#2276] opensaf-5.0.x [staging:ff6122] changeset: 8573:ff6122ce47a0 user: Hung Nguyen date:Fri Feb 10 16:53:48 2017 +0700 summary: imm: Update NO_DANGLING document with information about ATTR_DN [#2276] --- ** [tickets:#2276] imm: Update NO_DANGLING document with information about ATTR_DN** **Status:** fixed **Milestone:** 5.0.2 **Created:** Wed Jan 25, 2017 10:45 AM UTC by Hung Nguyen **Last Updated:** Mon Feb 06, 2017 03:51 AM UTC **Owner:** Hung Nguyen >From README.NO_DANGLING: > This flag can only be set for attribute definitions where the attribute data > type is SaNameT and the attribute is a CONFIG attribute. SaStringT API has been introduced in [#643]. We now can also use NO_DANGLING flag with SaStringT attributes that have DN flag. The NO_DANGLING document needs to be updated. --- 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] #2296 imm: IMMND on payload crashes after SC absence
- **status**: accepted --> review
---
** [tickets:#2296] imm: IMMND on payload crashes after SC absence**
**Status:** review
**Milestone:** 5.0.2
**Created:** Thu Feb 09, 2017 08:44 AM UTC by Hung Nguyen
**Last Updated:** Thu Feb 09, 2017 08:44 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/2296/attachment/logs.tgz)
(5.2 MB; application/x-compressed)
Removal of IMMND coordinator was introduced in [#1692].
Some cleanup actions are delayed until **immnd_proc_server()** is executed.
In case the cluster is back from headless too fast, **immnd_proc_server()**
will not be executed and IMMND will crashes later.
~~~
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO Announce sync, epoch:28
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO SERVER STATE: IMM_SERVER_READY -->
IMM_SERVER_SYNC_SERVER
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
2017-02-05 21:36:41 PL-5 osafimmloadd: NO Sync starting
2017-02-05 21:36:42 PL-5 osafdtmd[393]: NO Lost contact with 'SC-1'
2017-02-05 21:36:42 PL-5 osafimmnd[406]: WA Director Service in NOACTIVE state
- fevs replies pending:16 fevs highest processed:13154
2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA SC Absence IS allowed:900 IMMD
service is DOWN
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO IMMD SERVICE IS DOWN, HYDRA IS
CONFIGURED => UNREGISTERING IMMND form MDS
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:290002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:14d0002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA Postponing hard delete of admin
owner with id:41 when imm is not writable state
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1530002050f
sv_id:27
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 147 <339,
2050f> (OpenSafImmPBE)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1550002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 144 <0,
2010f(down)> (safLogService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 145 <0,
2010f(down)> (@safLogService_appl)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 146 <0,
2010f(down)> (@OpenSafImmReplicatorA)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 143 <0,
2010f(down)> (safClmService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 142 <0,
2010f(down)> (safAmfService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Impl Discarded node 2010f
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO MDS unregisterede. sleeping ...
2017-02-05 21:36:43 PL-5 osafimmpbed: WA PBE lost contact with parent IMMND -
Exiting
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO Sleep done registering IMMND with
MDS
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO SUCCESS IN REGISTERING IMMND WITH
MDS
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO MDS: mds_register_callback: dest
2050f01e8 already exist
2017-02-05 21:36:44 PL-5 osafimmnd[406]: WA IMMND - Client Node Get Failed for
cli_hdl:1464583980303
2017-02-05 21:36:45 PL-5 osafdtmd[393]: NO Established contact with 'SC-1'
2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA MDS Send Failed
2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA Error code 2 returned for message
type 17 - ignoring
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO IMMD service is UP ...
ScAbsenseAllowed?:900 introduced?:2
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13154 highestReceived:13154
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Epoch set to 29 in ImmModel
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13154 highestReceived:13154
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO ERR_BAD_HANDLE: admin owner id 42
does not exist
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Implementer connected: 149
(OpenSafImmPBE) <0, 2040f>
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13157 highestReceived:13158
2017-02-05 21:36:49 PL-5 osafimmnd[406]: ER Node is in a state that cannot
accept start of sync, will terminate
~~~
IMMND failed to revert back to IMM_SERVER_READY/IMM_NODE_FULLY_AVAILABLE and
crashed.
~~~
#0 0x7f23733bdc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 406
selftid = 406
#1 0x7f23733c1028 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x152d0009, sa_sigaction
= 0x152d0009}, sa_mask = {__val = {93865551367896, 30, 54, 139790248362720,
139790245522487, 17179869186, 139790248362720, 140726076478512, 0,
139790250985925, 54, 30, 54, 140726076478560, 139790245475049,
140726076478560}}, sa_flags = 0, sa_restorer = 0x2c774d2a0}
sigs = {__val = {32, 0 }}
#2 0x555ec6cac677 in ImmMode
[tickets] [opensaf:tickets] #2296 imm: IMMND on payload crashes after SC absence
---
** [tickets:#2296] imm: IMMND on payload crashes after SC absence**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Feb 09, 2017 08:44 AM UTC by Hung Nguyen
**Last Updated:** Thu Feb 09, 2017 08:44 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
-
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/2296/attachment/logs.tgz)
(5.2 MB; application/x-compressed)
Removal of IMMND coordinator was introduced in [#1692].
Some cleanup actions are delayed until **immnd_proc_server()** is executed.
In case the cluster is back from headless too fast, **immnd_proc_server()**
will not be executed and IMMND will crashes later.
~~~
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO Announce sync, epoch:28
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO SERVER STATE: IMM_SERVER_READY -->
IMM_SERVER_SYNC_SERVER
2017-02-05 21:36:41 PL-5 osafimmnd[406]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
2017-02-05 21:36:41 PL-5 osafimmloadd: NO Sync starting
2017-02-05 21:36:42 PL-5 osafdtmd[393]: NO Lost contact with 'SC-1'
2017-02-05 21:36:42 PL-5 osafimmnd[406]: WA Director Service in NOACTIVE state
- fevs replies pending:16 fevs highest processed:13154
2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA SC Absence IS allowed:900 IMMD
service is DOWN
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO IMMD SERVICE IS DOWN, HYDRA IS
CONFIGURED => UNREGISTERING IMMND form MDS
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:290002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:14d0002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: WA Postponing hard delete of admin
owner with id:41 when imm is not writable state
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1530002050f
sv_id:27
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 147 <339,
2050f> (OpenSafImmPBE)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Removing client id:1550002050f
sv_id:26
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 144 <0,
2010f(down)> (safLogService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 145 <0,
2010f(down)> (@safLogService_appl)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 146 <0,
2010f(down)> (@OpenSafImmReplicatorA)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 143 <0,
2010f(down)> (safClmService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Implementer disconnected 142 <0,
2010f(down)> (safAmfService)
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO Impl Discarded node 2010f
2017-02-05 21:36:43 PL-5 osafimmnd[406]: NO MDS unregisterede. sleeping ...
2017-02-05 21:36:43 PL-5 osafimmpbed: WA PBE lost contact with parent IMMND -
Exiting
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO Sleep done registering IMMND with
MDS
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO SUCCESS IN REGISTERING IMMND WITH
MDS
2017-02-05 21:36:44 PL-5 osafimmnd[406]: NO MDS: mds_register_callback: dest
2050f01e8 already exist
2017-02-05 21:36:44 PL-5 osafimmnd[406]: WA IMMND - Client Node Get Failed for
cli_hdl:1464583980303
2017-02-05 21:36:45 PL-5 osafdtmd[393]: NO Established contact with 'SC-1'
2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA MDS Send Failed
2017-02-05 21:36:49 PL-5 osafimmnd[406]: WA Error code 2 returned for message
type 17 - ignoring
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO IMMD service is UP ...
ScAbsenseAllowed?:900 introduced?:2
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13154 highestReceived:13154
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Epoch set to 29 in ImmModel
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13154 highestReceived:13154
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO ERR_BAD_HANDLE: admin owner id 42
does not exist
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Implementer connected: 149
(OpenSafImmPBE) <0, 2040f>
2017-02-05 21:36:49 PL-5 osafimmnd[406]: NO Re-introduce-me
highestProcessed:13157 highestReceived:13158
2017-02-05 21:36:49 PL-5 osafimmnd[406]: ER Node is in a state that cannot
accept start of sync, will terminate
~~~
IMMND failed to revert back to IMM_SERVER_READY/IMM_NODE_FULLY_AVAILABLE and
crashed.
~~~
#0 0x7f23733bdc37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 406
selftid = 406
#1 0x7f23733c1028 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x152d0009, sa_sigaction
= 0x152d0009}, sa_mask = {__val = {93865551367896, 30, 54, 139790248362720,
139790245522487, 17179869186, 139790248362720, 140726076478512, 0,
139790250985925, 54, 30, 54, 140726076478560, 139790245475049,
140726076478560}}, sa_flags = 0, sa_restorer = 0x2c774d2a0}
sigs = {__val = {32, 0 }}
#2 0x555ec6cac677 in ImmModel::prepareForSync (t
[tickets] [opensaf:tickets] #2290 mds: (TCP) Libraries cause high CPU load when opensaf service stops
---
** [tickets:#2290] mds: (TCP) Libraries cause high CPU load when opensaf
service stops**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 11:03 AM UTC by Hung Nguyen
**Last Updated:** Tue Feb 07, 2017 11:03 AM UTC
**Owner:** nobody
When DBSRsock is closed and it returns from mdtm_process_poll_recv_data_tcp()
~~~
:::c
syslog(LOG_ERR, "MDTM:SOCKET recd_bytes :%zd, conn lost with dh server",
recd_bytes);
close(tcp_cb->DBSRsock);
return;
~~~
the while() loops rapidly because the poll() returns **1** and pfd[0].revents
is **32 (POLLNVAL 0x020)**
~~~
:::c
pfd[0].fd = tcp_cb->DBSRsock;
pfd[1].fd = tcp_cb->tmr_fd;
while (1) {
int pollres;
pfd[0].events = POLLIN;
pfd[1].events = POLLIN;
pfd[0].revents = pfd[1].revents = 0;
pollres = poll(pfd, 2, MDTM_TCP_POLL_TIMEOUT);
...
}
~~~
-
Reproduce steps:
* run immcfg
~~~
root@SC-1:~# immcfg
>
~~~
* stop opensaf service
~~~
root@SC-1:~# service opensafd stop
~~~
* check the CPU
---
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] #2276 imm: Update NO_DANGLING document with information about ATTR_DN
- **status**: accepted --> review --- ** [tickets:#2276] imm: Update NO_DANGLING document with information about ATTR_DN** **Status:** review **Milestone:** 5.0.2 **Created:** Wed Jan 25, 2017 10:45 AM UTC by Hung Nguyen **Last Updated:** Wed Jan 25, 2017 10:45 AM UTC **Owner:** Hung Nguyen >From README.NO_DANGLING: > This flag can only be set for attribute definitions where the attribute data > type is SaNameT and the attribute is a CONFIG attribute. SaStringT API has been introduced in [#643]. We now can also use NO_DANGLING flag with SaStringT attributes that have DN flag. The NO_DANGLING document needs to be updated. --- 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] #2276 imm: Update NO_DANGLING document with information about ATTR_DN
--- ** [tickets:#2276] imm: Update NO_DANGLING document with information about ATTR_DN** **Status:** accepted **Milestone:** 5.0.2 **Created:** Wed Jan 25, 2017 10:45 AM UTC by Hung Nguyen **Last Updated:** Wed Jan 25, 2017 10:45 AM UTC **Owner:** Hung Nguyen >From README.NO_DANGLING: > This flag can only be set for attribute definitions where the attribute data > type is SaNameT and the attribute is a CONFIG attribute. SaStringT API has been introduced in [#643]. We now can also use NO_DANGLING flag with SaStringT attributes that have DN flag. The NO_DANGLING document needs to be updated. --- 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] #2270 imm: Missing check for SaString attributes with ATTR_DN flag
- **status**: review --> fixed
- **Comment**:
default (5.2) [staging:836f2d]
changeset: 8543:836f2d73d8f3
user: Hung Nguyen
date:Wed Jan 25 17:13:09 2017 +0700
summary: imm: Add missing checks for SaStringT attributes with ATTR_DN flag
[#2270]
opensaf-5.1.x [staging:f164ce]
changeset: 8544:f164ce48fcab
user: Hung Nguyen
date:Wed Jan 25 17:13:09 2017 +0700
summary: imm: Add missing checks for SaStringT attributes with ATTR_DN flag
[#2270]
opensaf-5.0.x [staging:d433a2]
changeset: 8545:d433a25db383
user: Hung Nguyen
date:Wed Jan 25 17:13:09 2017 +0700
summary: imm: Add missing checks for SaStringT attributes with ATTR_DN flag
[#2270]
---
** [tickets:#2270] imm: Missing check for SaString attributes with ATTR_DN
flag**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Wed Jan 18, 2017 11:03 AM UTC by Hung Nguyen
**Last Updated:** Mon Jan 23, 2017 08:12 AM UTC
**Owner:** Hung Nguyen
A combination of SA_IMM_ATTR_SASTRINGT and SA_IMM_ATTR_DN should be treated as
SA_IMM_ATTR_SANAMET.
Some places in IMM code miss the check for SaStringT
Example:
~~~
ImmModel::rtObjectCreate()
} else if (attrValues->n.attrValueType == SA_IMM_ATTR_SANAMET
&& !longDnsPermitted) {
...
if(attrValues->n.attrValue.val.x.size >=
SA_MAX_UNEXTENDED_NAME_LENGTH) {
LOG_NO("ERR_NAME_TOO_LONG: Attribute '%s' has long DN. "
"Not allowed by IMM service or extended names are disabled",
attrName.c_str());
err = SA_AIS_ERR_NAME_TOO_LONG;
goto rtObjectCreateExit;
}
~~~
---
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] #2272 imm: Mismatch between continuation ids when resetting sLastContinuationId
- **status**: review --> fixed
- **Comment**:
default (5.2) [staging:dd680f]
changeset: 8540:dd680f61b0b9
user: Hung Nguyen
date:Wed Jan 25 16:59:38 2017 +0700
summary: imm: Fix the mismatch when resetting sLastContinuationId [#2272]
opensaf-5.1.x [staging:8deeef]
changeset: 8541:8deeefa4feb5
user: Hung Nguyen
date:Wed Jan 25 16:59:38 2017 +0700
summary: imm: Fix the mismatch when resetting sLastContinuationId [#2272]
opensaf-5.0.x [staging:6fcf1b]
changeset: 8542:6fcf1b121492
user: Hung Nguyen
date:Wed Jan 25 16:59:38 2017 +0700
summary: imm: Fix the mismatch when resetting sLastContinuationId [#2272]
---
** [tickets:#2272] imm: Mismatch between continuation ids when resetting
sLastContinuationId**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Thu Jan 19, 2017 03:48 AM UTC by Hung Nguyen
**Last Updated:** Thu Jan 19, 2017 11:20 AM UTC
**Owner:** Hung Nguyen
Example from ImmModel::ccbObjectCreate()
~~~
//Increment even if we dont invoke locally
oMut->mContinuationId = (++sLastContinuationId);
if(sLastContinuationId >= 0xfffe)
{sLastContinuationId = 1;}
if(*implConn) {
if(object->mImplementer->mDying) {
LOG_WA("Lost connection with implementer %s in "
"CcbObjectCreate.",
object->mImplementer->mImplementerName.c_str());
*continuationId = 0;
*implConn = 0;
//err = SA_AIS_ERR_FAILED_OPERATION;
//Let the timeout handling take care of it.
//This really needs to be tested! But how ?
} else {
*continuationId = sLastContinuationId;
}
}
~~~
There's mismatch between **oMut->mContinuationId** and **\*continuationId**
when** sLastContinuationId** is reset to 1
---
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] #2271 imm: Unused variables in saImmOmClassCreate_2()
- **status**: review --> fixed - **Comment**: default (5.2) [staging:bd952a] changeset: 8539:bd952a977ef4 user: Hung Nguyen date:Wed Jan 25 16:43:17 2017 +0700 summary: imm: Remove unused variables from saImmOmClassCreate_2() [#2271] --- ** [tickets:#2271] imm: Unused variables in saImmOmClassCreate_2()** **Status:** fixed **Milestone:** 5.2.FC **Created:** Wed Jan 18, 2017 11:17 AM UTC by Hung Nguyen **Last Updated:** Thu Jan 19, 2017 10:39 AM UTC **Owner:** Hung Nguyen These variables always have value of 0. ~~~ int attrClNameExist = 0; int attrAdmNameExist = 0; int attrImplNameExist = 0; ~~~ --- 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] #2265 clm: clmd coredump
Hi, Here's the syslog, trace was not enabled. Attachments: - [systemlogs.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/b86ccaf0/1f0e/attachment/systemlogs.tgz) (240.1 kB; application/x-compressed) --- ** [tickets:#2265] clm: clmd coredump** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Jan 16, 2017 08:51 AM UTC by Hung Nguyen **Last Updated:** Thu Jan 19, 2017 08:49 AM UTC **Owner:** nobody Jan 11 10:36:23 SC-2 osafclmd[14467]: ER Node is NULL,problem with the database. **Jan 11 10:36:23 SC-2 osafclmd[14467]: ../../../../../../../opensaf/osaf/services/saf/clmsv/clms/clms_mbcsv.c:467: ckpt_proc_node_rec: Assertion '0' failed.** Jan 11 10:36:23 SC-2 osafamfnd[14497]: NO 'safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'nodeFailfast' Jan 11 10:36:23 SC-2 osafamfnd[14497]: ER safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery is:nodeFailfast Jan 11 10:36:23 SC-2 osafamfnd[14497]: Rebooting OpenSAF NodeId = 131599 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 131599, SupervisionTime = 60 Jan 11 10:36:23 SC-2 opensaf_reboot: Rebooting local node; timeout=60 --- 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] #2270 imm: Missing check for SaString attributes with ATTR_DN flag
- **status**: accepted --> review
---
** [tickets:#2270] imm: Missing check for SaString attributes with ATTR_DN
flag**
**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Jan 18, 2017 11:03 AM UTC by Hung Nguyen
**Last Updated:** Wed Jan 18, 2017 11:03 AM UTC
**Owner:** Hung Nguyen
A combination of SA_IMM_ATTR_SASTRINGT and SA_IMM_ATTR_DN should be treated as
SA_IMM_ATTR_SANAMET.
Some places in IMM code miss the check for SaStringT
Example:
~~~
ImmModel::rtObjectCreate()
} else if (attrValues->n.attrValueType == SA_IMM_ATTR_SANAMET
&& !longDnsPermitted) {
...
if(attrValues->n.attrValue.val.x.size >=
SA_MAX_UNEXTENDED_NAME_LENGTH) {
LOG_NO("ERR_NAME_TOO_LONG: Attribute '%s' has long DN. "
"Not allowed by IMM service or extended names are disabled",
attrName.c_str());
err = SA_AIS_ERR_NAME_TOO_LONG;
goto rtObjectCreateExit;
}
~~~
---
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] #2272 imm: Mismatch between continuation ids when resetting sLastContinuationId
- **status**: accepted --> review
---
** [tickets:#2272] imm: Mismatch between continuation ids when resetting
sLastContinuationId**
**Status:** review
**Milestone:** 5.0.2
**Created:** Thu Jan 19, 2017 03:48 AM UTC by Hung Nguyen
**Last Updated:** Thu Jan 19, 2017 03:48 AM UTC
**Owner:** Hung Nguyen
Example from ImmModel::ccbObjectCreate()
~~~
//Increment even if we dont invoke locally
oMut->mContinuationId = (++sLastContinuationId);
if(sLastContinuationId >= 0xfffe)
{sLastContinuationId = 1;}
if(*implConn) {
if(object->mImplementer->mDying) {
LOG_WA("Lost connection with implementer %s in "
"CcbObjectCreate.",
object->mImplementer->mImplementerName.c_str());
*continuationId = 0;
*implConn = 0;
//err = SA_AIS_ERR_FAILED_OPERATION;
//Let the timeout handling take care of it.
//This really needs to be tested! But how ?
} else {
*continuationId = sLastContinuationId;
}
}
~~~
There's mismatch between **oMut->mContinuationId** and **\*continuationId**
when** sLastContinuationId** is reset to 1
---
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] #2271 imm: Unused variables in saImmOmClassCreate_2()
- **status**: accepted --> review --- ** [tickets:#2271] imm: Unused variables in saImmOmClassCreate_2()** **Status:** review **Milestone:** 5.2.FC **Created:** Wed Jan 18, 2017 11:17 AM UTC by Hung Nguyen **Last Updated:** Wed Jan 18, 2017 11:17 AM UTC **Owner:** Hung Nguyen These variables always have value of 0. ~~~ int attrClNameExist = 0; int attrAdmNameExist = 0; int attrImplNameExist = 0; ~~~ --- 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] #2273 imm: imm_common is not specified as additional library for SaImmOi
- **status**: accepted --> fixed - **Comment**: default (5.2) [staging:79221e] changeset: 8521:79221e3f8ee7 user: Hung Nguyen date:Thu Jan 19 11:44:23 2017 +0700 summary: imm: Add imm_common to LIBADD list of libSaImmOi [#2273] --- ** [tickets:#2273] imm: imm_common is not specified as additional library for SaImmOi** **Status:** fixed **Milestone:** 5.2.FC **Created:** Thu Jan 19, 2017 04:07 AM UTC by Hung Nguyen **Last Updated:** Thu Jan 19, 2017 04:07 AM UTC **Owner:** Hung Nguyen ~~~ [lib] $ readelf -d libSaImmOi.so Dynamic section at offset 0x22d90 contains 29 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libopensaf_core.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libSaImmOi.so.0] 0x000f (RPATH) Library rpath: [/usr/local/lib/opensaf] ~~~ When linking against libSaImmOi, the compiler complains: ~~~ libSaImmOi.so: undefined reference to `immsv_evt_dec_flat' libSaImmOi.so: undefined reference to `immsv_evt_free_att_val' libSaImmOi.so: undefined reference to `immsv_evt_free_attrNames' libSaImmOi.so: undefined reference to `immsv_free_attrvalues_list' libSaImmOi.so: undefined reference to `immsv_free_attrmods' libSaImmOi.so: undefined reference to `immsv_evt_dec' libSaImmOi.so: undefined reference to `immsv_evt_enc_flat' libSaImmOi.so: undefined reference to `immsv_evt_enc' collect2: error: ld returned 1 exit status ~~~ --- 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] #2273 imm: imm_common is not specified as additional library for SaImmOi
--- ** [tickets:#2273] imm: imm_common is not specified as additional library for SaImmOi** **Status:** accepted **Milestone:** 5.2.FC **Created:** Thu Jan 19, 2017 04:07 AM UTC by Hung Nguyen **Last Updated:** Thu Jan 19, 2017 04:07 AM UTC **Owner:** Hung Nguyen ~~~ [lib] $ readelf -d libSaImmOi.so Dynamic section at offset 0x22d90 contains 29 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libopensaf_core.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libSaImmOi.so.0] 0x000f (RPATH) Library rpath: [/usr/local/lib/opensaf] ~~~ When linking against libSaImmOi, the compiler complains: ~~~ libSaImmOi.so: undefined reference to `immsv_evt_dec_flat' libSaImmOi.so: undefined reference to `immsv_evt_free_att_val' libSaImmOi.so: undefined reference to `immsv_evt_free_attrNames' libSaImmOi.so: undefined reference to `immsv_free_attrvalues_list' libSaImmOi.so: undefined reference to `immsv_free_attrmods' libSaImmOi.so: undefined reference to `immsv_evt_dec' libSaImmOi.so: undefined reference to `immsv_evt_enc_flat' libSaImmOi.so: undefined reference to `immsv_evt_enc' collect2: error: ld returned 1 exit status ~~~ --- 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] #2272 imm: Mismatch between continuation ids when resetting sLastContinuationId
---
** [tickets:#2272] imm: Mismatch between continuation ids when resetting
sLastContinuationId**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Jan 19, 2017 03:48 AM UTC by Hung Nguyen
**Last Updated:** Thu Jan 19, 2017 03:48 AM UTC
**Owner:** Hung Nguyen
Example from ImmModel::ccbObjectCreate()
~~~
//Increment even if we dont invoke locally
oMut->mContinuationId = (++sLastContinuationId);
if(sLastContinuationId >= 0xfffe)
{sLastContinuationId = 1;}
if(*implConn) {
if(object->mImplementer->mDying) {
LOG_WA("Lost connection with implementer %s in "
"CcbObjectCreate.",
object->mImplementer->mImplementerName.c_str());
*continuationId = 0;
*implConn = 0;
//err = SA_AIS_ERR_FAILED_OPERATION;
//Let the timeout handling take care of it.
//This really needs to be tested! But how ?
} else {
*continuationId = sLastContinuationId;
}
}
~~~
There's mismatch between **oMut->mContinuationId** and **\*continuationId**
when** sLastContinuationId** is reset to 1
---
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] #2271 imm: Unused variables in saImmOmClassCreate_2()
--- ** [tickets:#2271] imm: Unused variables in saImmOmClassCreate_2()** **Status:** accepted **Milestone:** 5.2.FC **Created:** Wed Jan 18, 2017 11:17 AM UTC by Hung Nguyen **Last Updated:** Wed Jan 18, 2017 11:17 AM UTC **Owner:** Hung Nguyen These variables always have value of 0. ~~~ int attrClNameExist = 0; int attrAdmNameExist = 0; int attrImplNameExist = 0; ~~~ --- 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] #2270 imm: Missing check for SaString attributes with ATTR_DN flag
---
** [tickets:#2270] imm: Missing check for SaString attributes with ATTR_DN
flag**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Wed Jan 18, 2017 11:03 AM UTC by Hung Nguyen
**Last Updated:** Wed Jan 18, 2017 11:03 AM UTC
**Owner:** Hung Nguyen
A combination of SA_IMM_ATTR_SASTRINGT and SA_IMM_ATTR_DN should be treated as
SA_IMM_ATTR_SANAMET.
Some places in IMM code miss the check for SaStringT
Example:
~~~
ImmModel::rtObjectCreate()
} else if (attrValues->n.attrValueType == SA_IMM_ATTR_SANAMET
&& !longDnsPermitted) {
...
if(attrValues->n.attrValue.val.x.size >=
SA_MAX_UNEXTENDED_NAME_LENGTH) {
LOG_NO("ERR_NAME_TOO_LONG: Attribute '%s' has long DN. "
"Not allowed by IMM service or extended names are disabled",
attrName.c_str());
err = SA_AIS_ERR_NAME_TOO_LONG;
goto rtObjectCreateExit;
}
~~~
---
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] #2265 clm: clmd coredump
--- ** [tickets:#2265] clm: clmd coredump** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Jan 16, 2017 08:51 AM UTC by Hung Nguyen **Last Updated:** Mon Jan 16, 2017 08:51 AM UTC **Owner:** nobody Jan 11 10:36:23 SC-2 osafclmd[14467]: ER Node is NULL,problem with the database. **Jan 11 10:36:23 SC-2 osafclmd[14467]: ../../../../../../../opensaf/osaf/services/saf/clmsv/clms/clms_mbcsv.c:467: ckpt_proc_node_rec: Assertion '0' failed.** Jan 11 10:36:23 SC-2 osafamfnd[14497]: NO 'safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'nodeFailfast' Jan 11 10:36:23 SC-2 osafamfnd[14497]: ER safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery is:nodeFailfast Jan 11 10:36:23 SC-2 osafamfnd[14497]: Rebooting OpenSAF NodeId = 131599 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 131599, SupervisionTime = 60 Jan 11 10:36:23 SC-2 opensaf_reboot: Rebooting local node; timeout=60 --- 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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2238 imm: Memory leak when clearing sDeferredObjUpdatesMap
- **status**: review --> fixed
- **Comment**:
opensaf-5.1.x [staging:8a6ce3]
changeset: 8476:8a6ce3aa83b3
user: Hung Nguyen
date:Wed Dec 21 14:19:09 2016 +0700
summary: imm: Fix memory leak when clearing sDeferredObjUpdatesMap [#2238]
opensaf-5.0.x [staging:07033b]
changeset: 8477:07033beb970a
user: Hung Nguyen
date:Wed Dec 21 14:19:09 2016 +0700
summary: imm: Fix memory leak when clearing sDeferredObjUpdatesMap [#2238]
---
** [tickets:#2238] imm: Memory leak when clearing sDeferredObjUpdatesMap**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Wed Dec 21, 2016 05:54 AM UTC by Hung Nguyen
**Last Updated:** Wed Dec 21, 2016 07:23 AM UTC
**Owner:** Hung Nguyen
~~~
while(!sDeferredObjUpdatesMap.empty()) {
doumIter = sDeferredObjUpdatesMap.begin();
DeferredRtAUpdateList* attrUpdList = doumIter->second;
while(!attrUpdList->empty()) {
DeferredRtAUpdate& dRtAU = attrUpdList->front();
immsv_free_attrmods(dRtAU.attrModsList);
dRtAU.attrModsList = NULL;
attrUpdList->pop_front();
}
sDeferredObjUpdatesMap.erase(doumIter);
}
~~~
attrUpdList should be freed.
This is for 5.0 branch and 5.1 branch. On the default (5.2) branch, the problem
has been fixed in [#2224]
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2238 imm: Memory leak when clearing sDeferredObjUpdatesMap
- Description has changed:
Diff:
--- old
+++ new
@@ -13,3 +13,5 @@
~~~
attrUpdList should be freed.
+
+This is for 5.0 branch and 5.1 branch. On the default (5.2) branch, the
problem has been fixed in [#2224]
- **status**: accepted --> review
---
** [tickets:#2238] imm: Memory leak when clearing sDeferredObjUpdatesMap**
**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Dec 21, 2016 05:54 AM UTC by Hung Nguyen
**Last Updated:** Wed Dec 21, 2016 05:54 AM UTC
**Owner:** Hung Nguyen
~~~
while(!sDeferredObjUpdatesMap.empty()) {
doumIter = sDeferredObjUpdatesMap.begin();
DeferredRtAUpdateList* attrUpdList = doumIter->second;
while(!attrUpdList->empty()) {
DeferredRtAUpdate& dRtAU = attrUpdList->front();
immsv_free_attrmods(dRtAU.attrModsList);
dRtAU.attrModsList = NULL;
attrUpdList->pop_front();
}
sDeferredObjUpdatesMap.erase(doumIter);
}
~~~
attrUpdList should be freed.
This is for 5.0 branch and 5.1 branch. On the default (5.2) branch, the problem
has been fixed in [#2224]
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2238 imm: Memory leak when clearing sDeferredObjUpdatesMap
---
** [tickets:#2238] imm: Memory leak when clearing sDeferredObjUpdatesMap**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Wed Dec 21, 2016 05:54 AM UTC by Hung Nguyen
**Last Updated:** Wed Dec 21, 2016 05:54 AM UTC
**Owner:** Hung Nguyen
~~~
while(!sDeferredObjUpdatesMap.empty()) {
doumIter = sDeferredObjUpdatesMap.begin();
DeferredRtAUpdateList* attrUpdList = doumIter->second;
while(!attrUpdList->empty()) {
DeferredRtAUpdate& dRtAU = attrUpdList->front();
immsv_free_attrmods(dRtAU.attrModsList);
dRtAU.attrModsList = NULL;
attrUpdList->pop_front();
}
sDeferredObjUpdatesMap.erase(doumIter);
}
~~~
attrUpdList should be freed.
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2224 imm: Improve the iteration in ImmModel
- Description has changed:
Diff:
--- old
+++ new
@@ -16,3 +16,4 @@
With C++11, erase(const_iterator) returns an iterator to the next element.
We can avoid resetting the iterator.
+Also some more improvements, see the patches for deatils.
- **status**: review --> fixed
- **Comment**:
default (5.2)
[staging:804ef3]
changeset: 8472:804ef37099d5
user: Hung Nguyen
date:Mon Dec 12 18:02:56 2016 +0700
summary: imm: Use return from map::erase() to avoid resetting iterator to
begin [#2224]
[staging:1ea1ab]
changeset: 8473:1ea1ab0f2a3e
user: Hung Nguyen
date:Mon Dec 12 18:57:55 2016 +0700
summary: imm: Don't reset iterator to begin when clearing a map [#2224]
[staging:747028]
changeset: 8474:747028dc9837
user: Hung Nguyen
date:Mon Dec 12 19:02:07 2016 +0700
summary: imm: Use erase(key_type) to remove all elements with specific key
[#2224]
---
** [tickets:#2224] imm: Improve the iteration in ImmModel**
**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:09 AM UTC by Hung Nguyen
**Last Updated:** Tue Dec 13, 2016 08:10 AM UTC
**Owner:** Hung Nguyen
After removing an element from a map, the iterator is reset to begin.
~~~
for(ci2=sAdmReqContinuationMap.begin();
ci2!=sAdmReqContinuationMap.end();) {
if(ci2->second.mConn == dead) {
TRACE_5("Discarding Adm Req continuation %llu", ci2->first);
sAdmReqContinuationMap.erase(ci2);
ci2=sAdmReqContinuationMap.begin();
} else { ++ci2;}
}
~~~
With C++11, erase(const_iterator) returns an iterator to the next element.
We can avoid resetting the iterator.
Also some more improvements, see the patches for deatils.
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2225 imm: Remove use of SaBoolT
- Description has changed:
Diff:
--- old
+++ new
@@ -14,4 +14,4 @@
~~~
-Use of SaBoolT should be kept in API and message types.
+Use of SaBoolT should be kept in API.
- **status**: review --> fixed
- **Comment**:
default (5.2)
[staging:1acc98]
changeset: 8468:1acc98ef1e62
user: Hung Nguyen
date:Tue Dec 13 09:40:26 2016 +0700
summary: imm: Remove use of SaBoolT from library [#2225]
[staging:aba326]
changeset: 8469:aba3268b5888
user: Hung Nguyen
date:Tue Dec 13 13:13:18 2016 +0700
summary: imm: Remove use of SaBoolT from IMMND [#2225]
[staging:9c8d08]
changeset: 8470:9c8d08de440e
user: Hung Nguyen
date:Tue Dec 13 13:40:11 2016 +0700
summary: imm: Remove use of SaBoolT from IMM tools and tests [#2225]
[staging:02d678]
changeset: 8471:02d678109ee4
user: Hung Nguyen
date:Tue Dec 20 13:18:41 2016 +0700
summary: imm: Remove use of SaBoolT from message type [#2225]
---
** [tickets:#2225] imm: Remove use of SaBoolT**
**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:43 AM UTC by Hung Nguyen
**Last Updated:** Wed Dec 14, 2016 09:00 AM UTC
**Owner:** Hung Nguyen
SaBoolT should be replaced with bool wherever possible.
Example:
~~~
SaBoolT freeMemory = SA_FALSE;
...
if(freeMemory == SA_TRUE) {
free(objectNameStr);
}
~~~
~~~
SaBoolT immnd_syncComplete(IMMND_CB *cb, SaBoolT coordinator, SaUint32T step);
~~~
Use of SaBoolT should be kept in API.
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2229 imm:disable pbe should honor critical ccbs
Here's the problem in details http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICCxgChSVvESyAygLIBi240ciKAkiSQHIAiluNBKACgEICimTKTIBaAMQBzMAFMZCAHwNmLAFxoATKwD6AYV29tqbtwAyATWQAKcQEYAlAB0EAZxkRoCSchcg6AW38AJRlgAHsXKAgwsABPOgQogF4NZGjkABMoXwAjABsZZD5BIWVWCVkMhWL1Vg1UbQB5Oj0DPUaSM34AFX4WbQBVXSFMdGAJaTlFMrVNHX1DYzNLGw0nBBBkMAIMsP9kBdLGcvFK6oFalnqmloX2ztMevsHhzDAcsIAPZDCANxkwMgZuoIAALQoLZDZZAIMIAdyhCAOQTo3ToulQph8EBAEBkQmKEnyAFcZEpjrNUFp+nddB0ur1+kEiNxnLIXOFXIUAGYxZB2ITvL4-f6A4FAxIofxhDKFGCggiSGQuNJhIFMVHaMhBDpauiPQUfb5-AFAinqBJQwIIDLaYBgMIwbRuMCiqz2AA0zjcNp8UEkGzyqrSAP8UA2eKKAmQ9sdypcRxUFRkVRqxDoAHFekESEIQEaRabxWQ+S49oVZCAywgPVH+MhuSAoHkVel2ZyMsHxBpnN0FSgYCBiW5W+CDgZgzlCi4IMSYABrRHI1HozHY3EyZw7H5gosU5CDhAAchQACswuG0mOYHlh3iwEA I think at the moment we recieve response for the CCB that disables PBE (init mode changed to INIT_FROM_FILE), we should commit all the critical CCB (if there's any) without waiting for responses from PBE. Since PBE is stopped in immnd_proc_server() which executes every 1 second, chances are we still get reponses for those critical CCB. In that case, we should ignore those responses because the init mode has changed and PBE should be ignored. --- ** [tickets:#2229] imm:disable pbe should honor critical ccbs** **Status:** review **Milestone:** 5.2.FC **Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy **Last Updated:** Wed Dec 14, 2016 02:19 PM UTC **Owner:** Neelakanta Reddy reproducible steps: 1. Bring up the cluster with PBE configured. 2. enable PBE 3. parallely run multiple ccb operations 4. disable PBE 5. in one of the payload/controller restart the immnd/node 6. sync wil be aboreted with following messages WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE or resart/reload the cluster NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. Aborting this sync attempt 7. The IMMND will never get synced untill cluster restart The problem is observed, when the node is not joining in middleware upgrade, and evetually upgrade fails. --- 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] #2225 imm: Remove use of SaBoolT
- **status**: accepted --> review
---
** [tickets:#2225] imm: Remove use of SaBoolT**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:43 AM UTC by Hung Nguyen
**Last Updated:** Mon Dec 12, 2016 07:43 AM UTC
**Owner:** Hung Nguyen
SaBoolT should be replaced with bool wherever possible.
Example:
~~~
SaBoolT freeMemory = SA_FALSE;
...
if(freeMemory == SA_TRUE) {
free(objectNameStr);
}
~~~
~~~
SaBoolT immnd_syncComplete(IMMND_CB *cb, SaBoolT coordinator, SaUint32T step);
~~~
Use of SaBoolT should be kept in API and message types.
---
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] #2224 imm: Improve the iteration in ImmModel
- **status**: accepted --> review
---
** [tickets:#2224] imm: Improve the iteration in ImmModel**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:09 AM UTC by Hung Nguyen
**Last Updated:** Mon Dec 12, 2016 07:09 AM UTC
**Owner:** Hung Nguyen
After removing an element from a map, the iterator is reset to begin.
~~~
for(ci2=sAdmReqContinuationMap.begin();
ci2!=sAdmReqContinuationMap.end();) {
if(ci2->second.mConn == dead) {
TRACE_5("Discarding Adm Req continuation %llu", ci2->first);
sAdmReqContinuationMap.erase(ci2);
ci2=sAdmReqContinuationMap.begin();
} else { ++ci2;}
}
~~~
With C++11, erase(const_iterator) returns an iterator to the next element.
We can avoid resetting the iterator.
---
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] #2142 imm: Compile the IMM library using the C++ compiler
- **status**: review --> fixed - **Comment**: default (5.2) [staging:3bd4e5] changeset: 8432:3bd4e5b7a96d user: Hung Nguyen date:Wed Nov 02 11:23:40 2016 +0700 summary: imm: Compile the IMM library using the C++ compiler [#2142] [staging:c94117] changeset: 8433:c9411767b601 user: Hung Nguyen date:Thu Dec 08 10:51:46 2016 +0700 summary: imm: Fix "crosses initialization" errors [#2142] [staging:4b9cd9] changeset: 8434:4b9cd9530600 user: Hung Nguyen date:Thu Dec 08 10:57:16 2016 +0700 summary: imm: Fix "invalid conversion" errors. [#2142] [staging:b0317b] changeset: 8435:b0317ba353eb user:Hung Nguyen date:Thu Dec 08 10:57:39 2016 +0700 summary: imm: Fix "comparison between signed and unsigned integer" errors [#2142] [staging:b358f6] changeset: 8436:b358f65db262 user:Hung Nguyen date:Thu Dec 08 10:59:06 2016 +0700 summary: imm: Fix linkage errors [#2142] --- ** [tickets:#2142] imm: Compile the IMM library using the C++ compiler** **Status:** fixed **Milestone:** 5.2.FC **Created:** Thu Oct 27, 2016 04:31 AM UTC by Hung Nguyen **Last Updated:** Thu Nov 03, 2016 11:02 AM UTC **Owner:** Hung Nguyen Compile the IMM library using the C++ compiler and fix all errors that C++ compiler complains. --- 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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2225 imm: Remove use of SaBoolT
---
** [tickets:#2225] imm: Remove use of SaBoolT**
**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:43 AM UTC by Hung Nguyen
**Last Updated:** Mon Dec 12, 2016 07:43 AM UTC
**Owner:** Hung Nguyen
SaBoolT should be replaced with bool wherever possible.
Example:
~~~
SaBoolT freeMemory = SA_FALSE;
...
if(freeMemory == SA_TRUE) {
free(objectNameStr);
}
~~~
~~~
SaBoolT immnd_syncComplete(IMMND_CB *cb, SaBoolT coordinator, SaUint32T step);
~~~
Use of SaBoolT should be kept in API and message types.
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2224 imm: Improve the iteration in ImmModel
---
** [tickets:#2224] imm: Improve the iteration in ImmModel**
**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Mon Dec 12, 2016 07:09 AM UTC by Hung Nguyen
**Last Updated:** Mon Dec 12, 2016 07:09 AM UTC
**Owner:** Hung Nguyen
After removing an element from a map, the iterator is reset to begin.
~~~
for(ci2=sAdmReqContinuationMap.begin();
ci2!=sAdmReqContinuationMap.end();) {
if(ci2->second.mConn == dead) {
TRACE_5("Discarding Adm Req continuation %llu", ci2->first);
sAdmReqContinuationMap.erase(ci2);
ci2=sAdmReqContinuationMap.begin();
} else { ++ci2;}
}
~~~
With C++11, erase(const_iterator) returns an iterator to the next element.
We can avoid resetting the iterator.
---
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.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2205 imm: IMMND crashes when receiving D2ND_ABORT_CCB
- **status**: review --> fixed - **Comment**: default (5.2) [staging:5cf3d4] changeset: 8379:5cf3d4f77d98 parent: 8376:c047cfa3b941 user: Hung Nguyen date:Fri Nov 25 11:08:49 2016 +0700 summary: imm: Correct nodeId assertion in ImmModel::ccbAbort() [#2205] opensaf-5.1.x [staging:185196] changeset: 8380:185196ebe26f user: Hung Nguyen date:Fri Nov 25 11:08:49 2016 +0700 summary: imm: Correct nodeId assertion in ImmModel::ccbAbort() [#2205] opensaf-5.0.x [staging:6064a2] changeset: 8381:6064a2b4e69c user: Hung Nguyen date:Fri Nov 25 11:08:49 2016 +0700 summary: imm: Correct nodeId assertion in ImmModel::ccbAbort() [#2205] --- ** [tickets:#2205] imm: IMMND crashes when receiving D2ND_ABORT_CCB** **Status:** fixed **Milestone:** 5.0.2 **Created:** Thu Nov 24, 2016 07:23 AM UTC by Hung Nguyen **Last Updated:** Mon Nov 28, 2016 08:16 AM UTC **Owner:** Hung Nguyen **Attachments:** - [osafNode.immnd.bz2](https://sourceforge.net/p/opensaf/tickets/2205/attachment/osafNode.immnd.bz2) (18.9 MB; application/octet-stream) ~~~ Nov 16 10:06:17 SC-2-1 osafimmnd[5608]: ../../../../../../../opensaf/osaf/services/saf/immsv/immnd/ImmModel.cc:6169: ccbAbort: Assertion '*nodeId == ccb->mAugCcbParent->mOriginatingNode' failed. ~~~ ~~~ Nov 16 10:06:17.260296 osafimmnd [5608:immsv_evt.c:5473] T8 Received: IMMND_EVT_A2ND_OI_CCB_AUG_INIT (91) from 0 Nov 16 10:06:17.260303 osafimmnd [5608:immnd_evt.c:10304] >> immnd_evt_ccb_augment_init Nov 16 10:06:17.260310 osafimmnd [5608:ImmModel.cc:6502] >> ccbAugmentInit Nov 16 10:06:17.260323 osafimmnd [5608:ImmModel.cc:6555] TR Augment CCB in state MODIFY_OP Nov 16 10:06:17.260329 osafimmnd [5608:ImmModel.cc:6592] TR omuti->second:0x14051f0 Nov 16 10:06:17.260359 osafimmnd [5608:ImmModel.cc:6593] TR omuti->second->mContinuationId:24 == rsp->inv:24 Nov 16 10:06:17.260366 osafimmnd [5608:ImmModel.cc:6600] TR obj:0x1405460 Nov 16 10:06:17.260371 osafimmnd [5608:ImmModel.cc:6658] << ccbAugmentInit Nov 16 10:06:17.261479 osafimmnd [5608:immsv_evt.c:5473] T8 Received: IMMND_EVT_D2ND_ABORT_CCB (62) from 0 Nov 16 10:06:17.261486 osafimmnd [5608:immnd_evt.c:7684] >> immnd_evt_proc_ccb_finalize Nov 16 10:06:17.261490 osafimmnd [5608:immnd_evt.c:6921] >> immnd_evt_ccb_abort Nov 16 10:06:17.261495 osafimmnd [5608:immnd_evt.c:6925] TR We expect there to be a PBE Nov 16 10:06:17.261501 osafimmnd [5608:ImmModel.cc:6079] >> ccbAbort Nov 16 10:06:17.261506 osafimmnd [5608:ImmModel.cc:6088] T5 ABORT CCB 79 Nov 16 10:06:17.261539 osafimmnd [5608:ImmModel.cc:6151] NO Ccb 79 ABORTED (immcfg_SC-2-1_9735) ~~~ When IMMND received A2ND_OI_CCB_AUG_INIT the ccbstate was changed to CCB_READY. Then when D2ND_ABORT_CCB message came, in ImmModel::ccbAbort() \*nodeId is not updated and later it failed to assert ~~~ osafassert(*nodeId == ccb->mAugCcbParent->mOriginatingNode); ~~~ Attached is IMMND traces. --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
