[tickets] [opensaf:tickets] #2530 amfd: amfd coredump after SC absence
- **status**: review --> fixed - **Comment**: commits: release: [1bca53315b2a1ce0441268679a336a038f4a68be] develop: [3aa79bfedf17dd9fe1d98708750b76db085d6568] --- ** [tickets:#2530] amfd: amfd coredump after SC absence** **Status:** fixed **Milestone:** 5.17.10 **Labels:** assignment failover during stop of both SC **Created:** Wed Jul 19, 2017 03:00 AM UTC by Minh Hon Chau **Last Updated:** Fri Jul 28, 2017 08:20 AM UTC **Owner:** Minh Hon Chau amfd coredump happens in the same sceario of ticket #2477 In #2477, amfd prevents to create 2 active assignments for same 2N SI, but amfd has missed a case of 2 standby assignments, which leads to the coredump in this ticket backtrace: ~~~ #0 0x7f4092cdb0c7 in raise () from /lib64/libc.so.6 #1 0x7f4092cdc478 in abort () from /lib64/libc.so.6 #2 0x7f4093b3be2e in __osafassert_fail (__file=, __line=, __func=, __assertion=) at ../../opensaf/src/base/sysf_def.c:286 #3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0, stby_susi=stby_susi@entry=0x7ffe4e89ae80, cb=0x7f4094d2ce80 <_control_block>) at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596 #4 0x7f4094aa1b8f in avd_sg_2n_su_chose_asgn (cb=cb@entry=0x7f4094d2ce80 <_control_block>, sg=0x7f4096ba41f0) at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:649 #5 0x7f4094aa70de in SG_2N::node_fail (this=0x7f4096ba41f0, cb=0x7f4094d2ce80 <_control_block>, su=0x7f4096bb6dd0) at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:3583 #6 0x7f4094a97c8a in AVD_SG::failover_absent_assignment (this=0x7f4096ba41f0) at ../../opensaf/src/amf/amfd/sg.cc:2310 #7 0x7f4094a4e155 in avd_cluster_tmr_init_evh (cb=0x7f4094d2ce80 <_control_block>, evt=) at ../../opensaf/src/amf/amfd/cluster.cc:103 #8 0x7f4094a7689c in process_event (cb_now=0x7f4094d2ce80 <_control_block>, evt=0x7f4084000c20) at ../../opensaf/src/amf/amfd/main.cc:775 #9 0x7f4094a3082e in main_loop () at ../../opensaf/src/amf/amfd/main.cc:691 #10 main (argc=, argv=) at ../../opensaf/src/amf/amfd/main.cc:848 (gdb) f 3 #3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0, stby_susi=stby_susi@entry=0x7ffe4e89ae80, cb=0x7f4094d2ce80 <_control_block>) at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596 596 ../../opensaf/src/amf/amfd/sg_2n_fsm.cc: No such file or directory. (gdb) p a_susi_1->si->list_of_sisu->su->name $1 = {static npos = , _M_dataplus = {> = {<__gnu_cxx::new_allocator> = {}, }, _M_p = 0x7f4096bb84d8 "safSu=SC-2,safSg=2N,safApp=ABC"}} (gdb) p a_susi_1->si->list_of_sisu->state $2 = SA_AMF_HA_STANDBY (gdb) p a_susi_1->si->list_of_sisu->fsm $3 = AVD_SU_SI_STATE_ABSENT (gdb) p a_susi_1->si->list_of_sisu->si_next->su->name $4 = {static npos = , _M_dataplus = {> = {<__gnu_cxx::new_allocator> = {}, }, _M_p = 0x7f4096bb39d8 "safSu=db68a05892,safSg=2N,safApp=ABC"}} (gdb) p a_susi_1->si->list_of_sisu->si_next->fsm $5 = AVD_SU_SI_STATE_ASGND (gdb) p a_susi_1->si->list_of_sisu->si_next->state $6 = SA_AMF_HA_STANDBY (gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->su->name $7 = {static npos = , _M_dataplus = {> = {<__gnu_cxx::new_allocator> = {}, }, _M_p = 0x7f4096bbb6e8 "safSu=PL-4,safSg=2N,safApp=ABC"}} (gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->fsm $8 = AVD_SU_SI_STATE_ASGND (gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->state $9 = SA_AMF_HA_ACTIVE (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] #2543 base: Use timeradd(), timersub() and timercmp()
--- ** [tickets:#2543] base: Use timeradd(), timersub() and timercmp()** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Wed Aug 02, 2017 11:38 AM UTC by Anders Widell **Last Updated:** Wed Aug 02, 2017 11:38 AM UTC **Owner:** nobody The system header file sys/time.h defines macros timeradd(), timersub() and timercmp() with similar functionality as some of the OpenSAF time support functions. The macros from the system header files could be used instead of the OpenSAF ones. --- 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] #2429 clm: support for a clm utility to perform tracking and for getting node info.
- **status**: review --> fixed - **Comment**: commit 77346df31fa7061496b22f91611e120477e907b5 Author: Praveen Date: Wed Aug 2 16:58:16 2017 +0530 clm: add clm tool for tracking and for getting node info [#2429] Add a utility/application which enables user to: -perform tracking using saClmClusterTrack_4(). -get node info by calling saClmClusterNodeGet_4(). -get node info asynchronously by calling saClmClusterNodeGetAsync(). --- ** [tickets:#2429] clm: support for a clm utility to perform tracking and for getting node info.** **Status:** fixed **Milestone:** 5.17.10 **Created:** Mon Apr 17, 2017 06:38 AM UTC by Praveen **Last Updated:** Fri Jul 14, 2017 09:04 AM UTC **Owner:** Praveen Ticket #2394 implements tool commands for handling CLM objects and performing admin operation. This ticket is to add a utility or application which enable user to: \-perform tracking using saClmClusterTrack_4(). \-get node info by calling saClmClusterNodeGet_4(). \-get node info asynchronously by calling saClmClusterNodeGetAsync(). --- 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] #2542 osaf: Divide the safe reboot into two phases
- **status**: accepted --> review --- ** [tickets:#2542] osaf: Divide the safe reboot into two phases** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Aug 02, 2017 11:00 AM UTC by Anders Widell **Last Updated:** Wed Aug 02, 2017 11:00 AM UTC **Owner:** Anders Widell As a simple solution to the problem described in [#2451], we can divide the safe reboot in the opensaf_reboot script into two phases: in the first phase we stop important OpenSAF services (especially IMM), and in the second phase we reboot the nodes. The full solution described in [#2451] can be implemented later as part of the enhanced cluster management. --- 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] #2542 osaf: Divide the safe reboot into two phases
--- ** [tickets:#2542] osaf: Divide the safe reboot into two phases** **Status:** accepted **Milestone:** 5.17.10 **Created:** Wed Aug 02, 2017 11:00 AM UTC by Anders Widell **Last Updated:** Wed Aug 02, 2017 11:00 AM UTC **Owner:** Anders Widell As a simple solution to the problem described in [#2451], we can divide the safe reboot in the opensaf_reboot script into two phases: in the first phase we stop important OpenSAF services (especially IMM), and in the second phase we reboot the nodes. The full solution described in [#2451] can be implemented later as part of the enhanced cluster management. --- 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] #2488 rde: Avoid sending messages to nodes that are down
- **status**: accepted --> review --- ** [tickets:#2488] rde: Avoid sending messages to nodes that are down** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Jun 07, 2017 11:59 AM UTC by Anders Widell **Last Updated:** Wed Aug 02, 2017 10:37 AM UTC **Owner:** Anders Widell RDE sometimes fails to send MDS messages because the receiving RDE service is already down. RDE should be optimised to keep track of service down events, and avoid sending messages to peers that are not up. --- 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] #2488 rde: Avoid sending messages to nodes that are down
- **status**: assigned --> accepted --- ** [tickets:#2488] rde: Avoid sending messages to nodes that are down** **Status:** accepted **Milestone:** 5.17.10 **Created:** Wed Jun 07, 2017 11:59 AM UTC by Anders Widell **Last Updated:** Sat Jul 01, 2017 04:15 PM UTC **Owner:** Anders Widell RDE sometimes fails to send MDS messages because the receiving RDE service is already down. RDE should be optimised to keep track of service down events, and avoid sending messages to peers that are not up. --- 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] #2541 nid: order of system log print out is not correct
--- ** [tickets:#2541] nid: order of system log print out is not correct** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Aug 02, 2017 07:52 AM UTC by Rafael Odzakow **Last Updated:** Wed Aug 02, 2017 07:52 AM UTC **Owner:** Rafael Odzakow using echo -n in opensafd causes delay write to log in a systemd environment causing unconsistent order of the logs. "Starting opensaf" will end up after "Startup finished" in the system log. --- 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] #2540 amfa: Incorrect return code from saAmfComponentErrorClear_4() for non-exisiting component
- **status**: assigned --> review --- ** [tickets:#2540] amfa: Incorrect return code from saAmfComponentErrorClear_4() for non-exisiting component** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Aug 02, 2017 05:30 AM UTC by Nguyen TK Luu **Last Updated:** Wed Aug 02, 2017 05:30 AM UTC **Owner:** Nguyen TK Luu When saAmfComponentErrorClear_4() is called with a non-existing component name, it returns SA_AIS_ERR_BAD_OPERATION instead SA_AIS_ERR_NOT_EXIST, which is not correct according to AMF-B.04.01 spec. Reproduce: 1. Call saAmfInitialize_4(). 2. Call saAmfComponentErrorClear_4() with a non-existing component name. 3. Call saAmfFinalize to finalize the handle obtained in 1st step. --- 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