[tickets] [opensaf:tickets] #2863 amfd: reduce load on IMM
- **Component**: unknown --> amf --- ** [tickets:#2863] amfd: reduce load on IMM** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue May 22, 2018 11:36 PM UTC by Gary Lee **Last Updated:** Sat Sep 29, 2018 11:00 PM UTC **Owner:** Gary Lee When amfd creates an object and IMM returns try again, this job will be queued. However, amfd may continue trying to modify attributes of this object from avd_saImmOiRtObjectUpdate_sync, resulting in ERR_NOT_EXIST and unnecessary load on IMM. We should also place these updates into a queue, if we know IMM is 'busy'. --- 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
[tickets] [opensaf:tickets] #2863 amfd: reduce load on IMM
- **Component**: amf --> unknown --- ** [tickets:#2863] amfd: reduce load on IMM** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue May 22, 2018 11:36 PM UTC by Gary Lee **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Gary Lee When amfd creates an object and IMM returns try again, this job will be queued. However, amfd may continue trying to modify attributes of this object from avd_saImmOiRtObjectUpdate_sync, resulting in ERR_NOT_EXIST and unnecessary load on IMM. We should also place these updates into a queue, if we know IMM is 'busy'. --- 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
[tickets] [opensaf:tickets] #2880 amf: Payload is out of control from active AMFD
- **Component**: unknown --> amf --- ** [tickets:#2880] amf: Payload is out of control from active AMFD** **Status:** fixed **Milestone:** 5.18.09 **Created:** Mon Jun 18, 2018 06:13 AM UTC by Thuan **Last Updated:** Sat Sep 29, 2018 10:59 PM UTC **Owner:** Thuan During SC failover, new active by somehow got PL-16 left cluster, but PL-16 still see Active AMFD. From that, any message from PL-16 will be invalid since msg_id reset to 0. May 3 12:59:54 SC-1 tipclog[5917]: Lost link <1.1.1:eth1-1.1.16:eth1> on network plane A May 3 12:59:54 SC-1 tipclog[5917]: Established link <1.1.1:eth1-1.1.16:eth1> on network plane A ... May 3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active May 3 13:05:51 SC-1 osafimmd[17537]: NO Old active NOT present => send discard node payload 2100f May 3 13:05:51 SC-1 osafamfnd[17765]: NO AVD NEW_ACTIVE, adest:1 May 3 13:05:51 SC-1 osafamfd[17733]: NO Node 'SC-2' left the cluster May 3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active DONE! May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_data_update_req_evh: node 2100f, receive msg_id(4389) in invalid node state 0 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4390, msg type 8, from 2100f should be 4389 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4391, msg type 8, from 2100f should be 4389 May 3 13:05:51 SC-1 osafamfd[17733]: NO Node 'PL-16' left the cluster May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4394, msg type 8, from 2100f should be 1 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4395, msg type 8, from 2100f should be 1 … May 3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 5043, msg type 8, from 2100f should be 1 May 3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 5044, msg type 8, from 2100f should be 1 PL-16 operational state become disable but it’s still available. The problem is not reproducible but customer claim that OPENSAF cannot recover it automatically. Customer has to reboot manually to recover PL-16. --- 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
[tickets] [opensaf:tickets] #2880 amf: Payload is out of control from active AMFD
- **Component**: amf --> unknown --- ** [tickets:#2880] amf: Payload is out of control from active AMFD** **Status:** fixed **Milestone:** 5.18.09 **Created:** Mon Jun 18, 2018 06:13 AM UTC by Thuan **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Thuan During SC failover, new active by somehow got PL-16 left cluster, but PL-16 still see Active AMFD. From that, any message from PL-16 will be invalid since msg_id reset to 0. May 3 12:59:54 SC-1 tipclog[5917]: Lost link <1.1.1:eth1-1.1.16:eth1> on network plane A May 3 12:59:54 SC-1 tipclog[5917]: Established link <1.1.1:eth1-1.1.16:eth1> on network plane A ... May 3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active May 3 13:05:51 SC-1 osafimmd[17537]: NO Old active NOT present => send discard node payload 2100f May 3 13:05:51 SC-1 osafamfnd[17765]: NO AVD NEW_ACTIVE, adest:1 May 3 13:05:51 SC-1 osafamfd[17733]: NO Node 'SC-2' left the cluster May 3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active DONE! May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_data_update_req_evh: node 2100f, receive msg_id(4389) in invalid node state 0 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4390, msg type 8, from 2100f should be 4389 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4391, msg type 8, from 2100f should be 4389 May 3 13:05:51 SC-1 osafamfd[17733]: NO Node 'PL-16' left the cluster May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4394, msg type 8, from 2100f should be 1 May 3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 4395, msg type 8, from 2100f should be 1 … May 3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 5043, msg type 8, from 2100f should be 1 May 3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 5044, msg type 8, from 2100f should be 1 PL-16 operational state become disable but it’s still available. The problem is not reproducible but customer claim that OPENSAF cannot recover it automatically. Customer has to reboot manually to recover PL-16. --- 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
[tickets] [opensaf:tickets] #2889 imm: avoid BAD_HANDLE result on requests after timeout on CCB apply
- **Component**: unknown --> imm --- ** [tickets:#2889] imm: avoid BAD_HANDLE result on requests after timeout on CCB apply** **Status:** fixed **Milestone:** 5.18.09 **Created:** Wed Jul 04, 2018 07:58 AM UTC by Vu Minh Nguyen **Last Updated:** Sat Sep 29, 2018 10:58 PM UTC **Owner:** nobody **Attachments:** - [ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt](https://sourceforge.net/p/opensaf/tickets/2889/attachment/ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt) (30.3 kB; text/plain) If CCB apply (IMMND_EVT_A2ND_CCB_APPLY) gets TIMEOUT (e.g: PBE is hung during that time), here is what will be happening at IMMND and IMMA: IMMND purges that synchronous request by doing following main jobs: 1) Attemp to abort CCB even the CCB state is in critical. 2) Remove client node from client dabase. At IMMA, inside `saImmOmCcbApply()` call, `imma_proc_recover_ccb_result()` is invoked to get CCB result by sending `IMMND_EVT_A2ND_RECOVER_CCB_OUTCOME` to the IMMND. After the CCB is commited, `imma_proc_recover_ccb_result()` returns SA_AIS_OK to `saImmOmCcbApply()` and then SA_AIS_OK to user. Later on, when user performs any IMM call on that IMM OM handle such as `saImmOmFinalize()` will result in `BAD_HANDLE` as the client node has already removed in #2 above. See syslog and imma trace from the attachment. --- 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
[tickets] [opensaf:tickets] #2889 imm: avoid BAD_HANDLE result on requests after timeout on CCB apply
- **Component**: imm --> unknown --- ** [tickets:#2889] imm: avoid BAD_HANDLE result on requests after timeout on CCB apply** **Status:** fixed **Milestone:** 5.18.09 **Created:** Wed Jul 04, 2018 07:58 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody **Attachments:** - [ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt](https://sourceforge.net/p/opensaf/tickets/2889/attachment/ccb_apply_get_TIMEOUT_result_in_BAD_HANDLE.txt) (30.3 kB; text/plain) If CCB apply (IMMND_EVT_A2ND_CCB_APPLY) gets TIMEOUT (e.g: PBE is hung during that time), here is what will be happening at IMMND and IMMA: IMMND purges that synchronous request by doing following main jobs: 1) Attemp to abort CCB even the CCB state is in critical. 2) Remove client node from client dabase. At IMMA, inside `saImmOmCcbApply()` call, `imma_proc_recover_ccb_result()` is invoked to get CCB result by sending `IMMND_EVT_A2ND_RECOVER_CCB_OUTCOME` to the IMMND. After the CCB is commited, `imma_proc_recover_ccb_result()` returns SA_AIS_OK to `saImmOmCcbApply()` and then SA_AIS_OK to user. Later on, when user performs any IMM call on that IMM OM handle such as `saImmOmFinalize()` will result in `BAD_HANDLE` as the client node has already removed in #2 above. See syslog and imma trace from the attachment. --- 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
[tickets] [opensaf:tickets] #2905 rded: perform KV store operations outside main thread
- **Component**: unknown --> rde --- ** [tickets:#2905] rded: perform KV store operations outside main thread** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue Jul 31, 2018 06:12 AM UTC by Gary Lee **Last Updated:** Sat Sep 29, 2018 10:57 PM UTC **Owner:** Gary Lee When split brain prevention is enabled, sometimes the KV store may be very slow to respond, and causes RDE to timeout. We should move any KV store operations (through Consensus service) away from the main thread. 2018-07-29 21:53:00.299 SC-9 osafrded[193]: NO Received takeover request ''. Our network size is 9 2018-07-29 21:53:00.299 SC-9 osafrded[193]: NO Empty takeover request from watch command. Read it again. 2018-07-29 21:53:11.000 SC-9 osafamfnd[273]: ER safComp=RDE,safSu=SC-9,safSg=2N,safApp=OpenSAF Faulted due to:csiSetcallbackTimeout Recovery is:nodeFailfast 2018-07-29 21:53:11.002 SC-9 osafamfnd[273]: Rebooting OpenSAF NodeId = 133391 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 133391, SupervisionTime = 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2905 rded: perform KV store operations outside main thread
- **Component**: rde --> unknown --- ** [tickets:#2905] rded: perform KV store operations outside main thread** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue Jul 31, 2018 06:12 AM UTC by Gary Lee **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Gary Lee When split brain prevention is enabled, sometimes the KV store may be very slow to respond, and causes RDE to timeout. We should move any KV store operations (through Consensus service) away from the main thread. 2018-07-29 21:53:00.299 SC-9 osafrded[193]: NO Received takeover request ''. Our network size is 9 2018-07-29 21:53:00.299 SC-9 osafrded[193]: NO Empty takeover request from watch command. Read it again. 2018-07-29 21:53:11.000 SC-9 osafamfnd[273]: ER safComp=RDE,safSu=SC-9,safSg=2N,safApp=OpenSAF Faulted due to:csiSetcallbackTimeout Recovery is:nodeFailfast 2018-07-29 21:53:11.002 SC-9 osafamfnd[273]: Rebooting OpenSAF NodeId = 133391 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 133391, SupervisionTime = 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2897 imm: ignore searching for system attribute(s) in class definition
- **Component**: imm --> plm --- ** [tickets:#2897] imm: ignore searching for system attribute(s) in class definition** **Status:** fixed **Milestone:** 5.18.09 **Created:** Fri Jul 13, 2018 07:54 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody **Attachments:** - [model.xml](https://sourceforge.net/p/opensaf/tickets/2897/attachment/model.xml) (1.3 kB; text/xml) IMM fails to load model file which has system attribute(s) in object tags but not in its class element. In case of importing, it always fails to import the file having system attributes in object tags. To produce this issue, loading/importing attached model file. :::bash $ immcfg -f model.xml NO CORRESPONDING ATTRIBUTE ▒▒2|▒U in class Checking about whether the attribute name does exist in class element or not should be ignored if the processing attribute name in object tags is one of system attributes. --- 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
[tickets] [opensaf:tickets] #2897 imm: ignore searching for system attribute(s) in class definition
- **Component**: plm --> imm --- ** [tickets:#2897] imm: ignore searching for system attribute(s) in class definition** **Status:** fixed **Milestone:** 5.18.09 **Created:** Fri Jul 13, 2018 07:54 AM UTC by Vu Minh Nguyen **Last Updated:** Sat Sep 29, 2018 10:55 PM UTC **Owner:** nobody **Attachments:** - [model.xml](https://sourceforge.net/p/opensaf/tickets/2897/attachment/model.xml) (1.3 kB; text/xml) IMM fails to load model file which has system attribute(s) in object tags but not in its class element. In case of importing, it always fails to import the file having system attributes in object tags. To produce this issue, loading/importing attached model file. :::bash $ immcfg -f model.xml NO CORRESPONDING ATTRIBUTE ▒▒2|▒U in class Checking about whether the attribute name does exist in class element or not should be ignored if the processing attribute name in object tags is one of system attributes. --- 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
[tickets] [opensaf:tickets] #2898 imm: syslog number of recent fevs messages when immnd down
- **Component**: plm --> imm --- ** [tickets:#2898] imm: syslog number of recent fevs messages when immnd down** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue Jul 17, 2018 05:22 AM UTC by Vu Minh Nguyen **Last Updated:** Sat Sep 29, 2018 01:17 PM UTC **Owner:** Danh Vo We has encountered "OUT OF ORDER" error sometimes, and it is not easy to find out which message has been lost. It would help if imm is able to syslog a number of recent fevs (e.g. 05) when detecting immnd down for any reason, showing recent sequence numbers and message ids. --- 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
[tickets] [opensaf:tickets] #2898 imm: syslog number of recent fevs messages when immnd down
- **Component**: imm --> plm --- ** [tickets:#2898] imm: syslog number of recent fevs messages when immnd down** **Status:** fixed **Milestone:** 5.18.09 **Created:** Tue Jul 17, 2018 05:22 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Danh Vo We has encountered "OUT OF ORDER" error sometimes, and it is not easy to find out which message has been lost. It would help if imm is able to syslog a number of recent fevs (e.g. 05) when detecting immnd down for any reason, showing recent sequence numbers and message ids. --- 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
[tickets] [opensaf:tickets] #2824 evt: Cannot handle immnd restart when oi handle is not resurrected
- **Milestone**: 5.18.04 --> future --- ** [tickets:#2824] evt: Cannot handle immnd restart when oi handle is not resurrected** **Status:** unassigned **Milestone:** future **Created:** Thu Mar 29, 2018 01:44 PM UTC by elunlen **Last Updated:** Thu Mar 29, 2018 01:44 PM UTC **Owner:** nobody If immnd is restarted and resurrection of oi handle fails (BAD HANDLE) this service will crash and cause a node restart. Reproduce problem: - Disable io resurrection in imma_oi_api.cc (has to be hacked) - Restart osafimmnd ($ pkill -SIGKILL osafimmnd) --- 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
[tickets] [opensaf:tickets] #2804 base: possible memleak in daemonize()
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2804] base: possible memleak in daemonize()** **Status:** assigned **Milestone:** 5.18.12 **Created:** Fri Mar 09, 2018 04:21 AM UTC by Minh Hon Chau **Last Updated:** Thu Mar 15, 2018 06:52 AM UTC **Owner:** Minh Hon Chau - start opensaf, running amfd with valgrind - stop opensaf Got memleak report as below Looks like from strdup() ==1042== Memcheck, a memory error detector ==1042== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==1042== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==1042== Command: /usr/local/lib/opensaf/osafamfd --tracemask=0x ==1042== Parent PID: 1037 ==1042== ==1042== ==1042== HEAP SUMMARY: ==1042== in use at exit: 72,757 bytes in 2 blocks ==1042== total heap usage: 59 allocs, 57 frees, 78,574 bytes allocated ==1042== ==1042== 53 bytes in 1 blocks are definitely lost in loss record 1 of 2 ==1042==at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==1042==by 0x58C31CE: daemonize (daemon.c:292) ==1042==by 0x127C58: main (main.cc:823) ==1042== ==1042== LEAK SUMMARY: ==1042==definitely lost: 53 bytes in 1 blocks ==1042==indirectly lost: 0 bytes in 0 blocks ==1042== possibly lost: 0 bytes in 0 blocks ==1042==still reachable: 72,704 bytes in 1 blocks ==1042== suppressed: 0 bytes in 0 blocks --- 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
[tickets] [opensaf:tickets] #2813 lck: lcknd healthcheck times out
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2813] lck: lcknd healthcheck times out** **Status:** assigned **Milestone:** 5.18.12 **Created:** Mon Mar 19, 2018 02:08 PM UTC by Alex Jones **Last Updated:** Mon Mar 19, 2018 02:08 PM UTC **Owner:** Alex Jones lcknd processes mbx events in a loop. Therefore, if local events are sent continuously this will become an infinite loop, and AMF health check will get starved out. --- 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
[tickets] [opensaf:tickets] #2798 mds: mdstest 5 1, 5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
- **Milestone**: 5.18.04 --> 5.18.12
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** review
**Milestone:** 5.18.12
**Created:** Wed Mar 07, 2018 04:19 AM UTC by Hoa Le
**Last Updated:** Mon Mar 26, 2018 05:01 AM UTC
**Owner:** Hoa Le
**Attachments:**
-
[mdstest_5_1.tar.gz](https://sourceforge.net/p/opensaf/tickets/2798/attachment/mdstest_5_1.tar.gz)
(8.4 MB; application/gzip)
Opensaf commit 5629f554686a498f328e0c79fc946379cbcf6967
mdstest 5 1
~~~
LOG_NO("\nAction: Retrieve only ONE event\n");
if (mds_service_subscribe(gl_tet_adest.mds_pwe1_hdl, 500,
NCSMDS_SCOPE_INTRACHASSIS, 2,
svcids) != NCSCC_RC_SUCCESS) {
LOG_NO("\nFail\n");
FAIL = 1;
} else {
LOG_NO("\nAction: Retrieve only ONE event\n");
if (mds_service_retrieve(gl_tet_adest.mds_pwe1_hdl, 500,
SA_DISPATCH_ONE) != NCSCC_RC_SUCCESS) {
LOG_NO("Fail, retrieve ONE\n");
FAIL = 1;
} else
LOG_NO("\nSuccess\n");
~~~
After the subscription request being successful, mdstest would expectedly
receive two 2 MDS_UP events of services 600 and 700. These info will be
retrieved in the next step of the test case (mds_service_retrieve).
The problem here is, these MDS_UP events are processed in a separate (parallel)
thread (mds core thread) from the test case's main thread. In a bad scenario,
if the mds core thread cannot be processed before the RETRIEVE operations in
the main thread, the RETRIEVE request with "SA_DISPATCH_ONE" flag will return
"error", and the test case will fail.
<143>1 2018-03-07T01:10:29.936907+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="155"] << mds_mcm_svc_subscribe*** // MDS SUBSCRIBE request***
...
<142>1 2018-03-07T01:10:29.937631+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="162"] MDS_SND_RCV: info->info.retrieve_msg.i_dispatchFlags ==
SA_DISPATCH_ONE*** // MDS RETRIEVE request with SA DISPATCH ONE flag came
before MDS UP events being processed***
<139>1 2018-03-07T01:10:29.937729+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="163"] MDS_SND_RCV: msgelem == NULL
<142>1 2018-03-07T01:10:29.937953+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="164"] MDTM: Processing pollin events
<142>1 2018-03-07T01:10:29.938333+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="165"] MDTM: Received SVC event
<143>1 2018-03-07T01:10:29.93838+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="166"] >> mds_mcm_svc_up
<143>1 2018-03-07T01:10:29.938418+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="167"] MCM:API: LOCAL SVC INFO : svc_id = INTERNAL(500) | PWE id =
1 | VDEST id = 65535 |
<143>1 2018-03-07T01:10:29.938439+07:00 SC-1 mdstest 473 mds.log [meta
sequenceId="168"] MCM:API: REMOTE SVC INFO : svc_id = EXTERNAL(600) | PWE id =
1 | VDEST id = 65535 | POLICY = 1 | SCOPE = 3 | ROLE = 1 | MY_PCON = 0 |
2018-03-07 01:10:29.941 SC-1 mdstest: NO #012Action: Retrieve only ONE event
2018-03-07 01:10:29.941 SC-1 mdstest: NO #012Request to ncsmds_api: MDS
RETRIEVE has FAILED
2018-03-07 01:10:29.942 SC-1 mdstest: NO Fail, retrieve ONE
The same issue was observed in mdstest 5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6.
---
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
[tickets] [opensaf:tickets] #2791 mds: o_rsp is NULL when send operation is OK
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2791] mds: o_rsp is NULL when send operation is OK** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Feb 28, 2018 12:17 AM UTC by Gary Lee **Last Updated:** Mon Mar 19, 2018 11:33 PM UTC **Owner:** nobody **Attachments:** - [bt_20180221_01:44:44_230](https://sourceforge.net/p/opensaf/tickets/2791/attachment/bt_20180221_01%3A44%3A44_230) (548 Bytes; application/octet-stream) - [bt_core.1519173886.osafntfd.230.SC-2](https://sourceforge.net/p/opensaf/tickets/2791/attachment/bt_core.1519173886.osafntfd.230.SC-2) (11.9 kB; application/octet-stream) - [mds.log](https://sourceforge.net/p/opensaf/tickets/2791/attachment/mds.log) (319.4 kB; text/x-log) osafntfd coredump during node shutdown. It is crashing in the AMF agent library. But the root cause seems to be in MDS. A MDS_SENDTYPE_SNDRSP operation returns OK but o_rsp is NULL. ~~~ Core was generated by `/usr/local/lib/opensaf/osafntfd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f407eba6737 in AmfAgent::HealthcheckStart (hdl=4288675841, comp_name=0x55d5d37fd1fc <_ntfs_cb+28>, hc_key=hc_key@entry=0x7ffe694190e0, inv=inv@entry=SA_AMF_HEALTHCHECK_AMF_INVOKED, rec_rcvr=rec_rcvr@entry=SA_AMF_COMPONENT_FAILOVER) at src/amf/agent/amf_agent.cc:822 [Current thread is 1 (Thread 0x7f407f3f4740 (LWP 230))] ~~~ --- 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
[tickets] [opensaf:tickets] #2767 pyosaf: Fix invoke_admin_operation() method of ImmOmAgent
- **Milestone**: 5.18.04 --> 5.18.12
---
** [tickets:#2767] pyosaf: Fix invoke_admin_operation() method of ImmOmAgent**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Mon Jan 22, 2018 10:04 AM UTC by Danh Vo
**Last Updated:** Fri Feb 02, 2018 12:18 PM UTC
**Owner:** nobody
An error occurs when using the invoke_admin_operation() method to perform an
admin operation which resturns operation_rc that is not SA_AIS_OK.
line: 292
log_err("Administrative operation(%s) on %s FAILED - %s" %
(op_id, object_dn, eSaAisErrorT.whatis(operation_rc)))
---
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
[tickets] [opensaf:tickets] #2777 dtm: Handle TCP connection failures gracefully
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2777] dtm: Handle TCP connection failures gracefully** **Status:** assigned **Milestone:** 5.18.12 **Created:** Wed Jan 31, 2018 01:56 PM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:18 PM UTC **Owner:** Anders Widell When TCP connect() fails, DTM tries to add a -1 file descriptor to epoll(), which fails and results in the DTM process exiting.: ~~~ rootfs/var/PL-3/log/messages:Jan 31 14:18:40 PL-3 local0.err osafdtmd[425]: ER DTM :Connect failed (connect()) err :Connection refused rootfs/var/PL-3/log/messages:Jan 31 14:18:40 PL-3 local0.err osafdtmd[425]: ER DTM: epoll_ctl(7, EPOLL_CTL_ADD, -1) 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2770 imm: data size mismatches in pbe code
- **Milestone**: 5.18.04 --> 5.18.12
---
** [tickets:#2770] imm: data size mismatches in pbe code**
**Status:** review
**Milestone:** 5.18.12
**Created:** Wed Jan 24, 2018 03:42 PM UTC by Vu Minh Nguyen
**Last Updated:** Fri Feb 02, 2018 12:18 PM UTC
**Owner:** Vu Minh Nguyen
Object ID and Class ID are `unsigned int` data type, but they are not used
consistently through the codes (local variables and function parameters) - few
places use `int`.
If the values of these IDs reach over MAX_INT, we may have problem when doing
sqlite queries.
::: C++
static void valuesToPBE(const SaImmAttrValuesT_2 *p, SaImmAttrFlagsT
attrFlags, int objId, void *db_handle) {}
void objectModifyDiscardMatchingValuesOfAttrToPBE(
void *db_handle, std::string objName, const SaImmAttrValuesT_2 *attrValue,
SaUint64T ccb_id) {
int object_id;
int class_id;
}
---
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
[tickets] [opensaf:tickets] #2765 base: try_again_decorator is wrong for initialize API
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2765] base: try_again_decorator is wrong for initialize API** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Jan 22, 2018 07:49 AM UTC by Canh Truong **Last Updated:** Fri Feb 02, 2018 12:18 PM UTC **Owner:** nobody When doing try-again for Initialize api, the version is updated by previous failed initialize and used for next re-try initialize. The version should always be original input version --- 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
[tickets] [opensaf:tickets] #2733 ntf: NTFD has unexpectedly crashed due to ntfimcnd exit
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2733] ntf: NTFD has unexpectedly crashed due to ntfimcnd exit** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Dec 07, 2017 11:38 AM UTC by Canh Truong **Last Updated:** Fri Feb 02, 2018 12:18 PM UTC **Owner:** nobody When the cluster is started, NTFD has unexpectedly crashed. The issue happen because the ntfimcnd exit when saImmOiDispatch() fails with BAD_HANDLE error syslog: 017-12-07 17:42:39.278 SC-1 osafckptnd[531]: Started 2017-12-07 17:42:39.355 SC-1 osafsmfnd[573]: Started 2017-12-07 17:42:39.356 SC-1 osafsmfnd[573]: NO MDS initialize_smfnd: smfnd_mds_init() 2017-12-07 17:42:39.356 SC-1 osafsmfnd[573]: NO MDS smfnd_mds_init: mds_get_handle() 2017-12-07 17:42:39.357 SC-1 osafsmfnd[573]: NO MDS mds_get_handle: Done 2017-12-07 17:42:39.357 SC-1 osafsmfnd[573]: NO MDS smfnd_mds_init: mds_register() 2017-12-07 17:42:39.358 SC-1 osafsmfnd[573]: NO MDS smfnd_mds_init: Done 2017-12-07 17:42:39.394 SC-1 osafamfnd[501]: NO 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' Presence State INSTANTIATING => INSTANTIATED 2017-12-07 17:42:39.425 SC-1 osafsmfd[615]: Started 2017-12-07 17:42:39.472 SC-1 osafamfnd[501]: NO Assigning 'safSi=NoRed1,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' 2017-12-07 17:42:39.473 SC-1 osafamfnd[501]: NO Assigned 'safSi=NoRed1,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' 2017-12-07 17:42:39.663 SC-1 osafimmnd[443]: NO Implementer connected: 19 (safCheckPointService) <265, 2010f> 2017-12-07 17:42:39.665 SC-1 osafimmnd[443]: NO Implementer disconnected 19 <265, 2010f> (safCheckPointService) 2017-12-07 17:42:49.558 SC-1 osafamfd[487]: NO Received node_up from 2030f: msg_id 1 2017-12-07 17:42:49.659 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=NTF,safSu=SC-1,safSg=2N,safApp=OpenSAF' failed 2017-12-07 17:42:49.659 SC-1 osafamfnd[501]: NO Reason: component registration timer expired 2017-12-07 17:42:54.695 SC-1 osafimmnd[443]: NO Implementer locally disconnected. Marking it as doomed 16 <15, 2010f> (@OpenSafImmReplicatorA) 2017-12-07 17:42:54.695 SC-1 osafimmnd[443]: NO Implementer disconnected 16 <15, 2010f> (@OpenSafImmReplicatorA) 2017-12-07 17:42:54.696 SC-1 opensafd[384]: ER Service NTFD has unexpectedly crashed. Unable to continue, exiting 2017-12-07 17:42:54.712 SC-1 osafntfd[672]: mkfifo already exists: /var/lib/opensaf/osafntfd.fifo File exists 2017-12-07 17:42:54.712 SC-1 osafntfd[672]: Started 2017-12-07 17:42:54.714 SC-1 osafamfnd[501]: NO 'safSu=SC-1,safSg=2N,safApp=OpenSAF' Presence State INSTANTIATING => INSTANTIATED 2017-12-07 17:42:54.717 SC-1 2017-12-07 17:42:54.725 SC-1 osafntfimcnd[677]: logtrace: trace enabled to file 'osafntfimcn', mask=0x 2017-12-07 17:42:54.728 SC-1 osafimmnd[443]: NO Implementer (applier) connected: 20 (@OpenSafImmReplicatorA) <267, 2010f> 2017-12-07 17:42:54.731 SC-1 osafntfimcnd[677]: NO Started 2017-12-07 17:42:59.564 SC-1 osafamfd[487]: exiting for shutdown 2017-12-07 17:42:59.565 SC-1 osafamfnd[501]: ER AMFD has unexpectedly crashed. Rebooting node 2017-12-07 17:42:59.565 SC-1 osafamfnd[501]: Rebooting OpenSAF NodeId = 131343 EE Name = , Reason: AMFD has unexpectedly crashed. Rebooting node, OwnNodeId = 131343, SupervisionTime = 60 2017-12-07 17:42:59.573 SC-1 opensaf_reboot: Rebooting local node; timeout=60 2017-12-07 17:42:59.624 SC-1 upstart-socket-bridge[353]: Disconnected from Upstart ntfimcnd: <143>1 2017-12-07T17:43:21.529917+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="136"] 477:imm/agent/imma_mds.cc:402 T3 IMMND DOWN <143>1 2017-12-07T17:43:21.529922+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="137"] 477:imm/agent/imma_db.cc:680 >> imma_mark_clients_stale <143>1 2017-12-07T17:43:21.529926+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="138"] 477:imm/agent/imma_db.cc:741 TR Stale marked client cl:16 node:2010f <143>1 2017-12-07T17:43:21.52993+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="139"] 477:imm/agent/imma_db.cc:824 >> isExposed <143>1 2017-12-07T17:43:21.529934+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="140"] 477:imm/agent/imma_db.cc:853 TR OM CLIENT <143>1 2017-12-07T17:43:21.529937+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="141"] 477:imm/agent/imma_db.cc:886 TR isExposed Returning Exposed:0 <143>1 2017-12-07T17:43:21.529941+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="142"] 477:imm/agent/imma_db.cc:887 << isExposed <143>1 2017-12-07T17:43:21.529945+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="143"] 477:imm/agent/imma_db.cc:755 << imma_mark_clients_stale <143>1 2017-12-07T17:43:21.52995+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="144"] 477:mds/mds_dt_trans.c:755 >> mdtm_process_poll_recv_data_tcp <143>1 2017-12-07T17:43:21.529956+07:00 SC-1 osafntfimcnd 474 osafntfimcn [meta sequenceId="145"] 477:imm/agent/imma_mds.cc:402 T3 IMMND DOWN <143>1
[tickets] [opensaf:tickets] #2726 smf: Smfnd does not protect global variables used in more than one thread
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2726] smf: Smfnd does not protect global variables used in more than one thread** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Dec 04, 2017 11:29 AM UTC by elunlen **Last Updated:** Fri Sep 14, 2018 10:36 AM UTC **Owner:** elunlen Several global variables (cb structure) are handled both in the main thread and in the mds thread but no mutex is used for protection. Make handling of global variables thread safe --- 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
[tickets] [opensaf:tickets] #2727 smf: Smfnd incorrect handling of client list. Possible memory leek
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2727] smf: Smfnd incorrect handling of client list. Possible memory leek** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Dec 04, 2017 11:37 AM UTC by elunlen **Last Updated:** Fri Sep 14, 2018 10:35 AM UTC **Owner:** nobody >From TBD in smf node director smfnd_mds.c mds_svc_event() Need to clean up the cb->cbk_list, otherwise there will be memory leak. For the time being we are storing only count of agents, not the adest of agents and hence it is not possible to clean up cbk_list. --- 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
[tickets] [opensaf:tickets] #2697 clm: Use base::Process to execute scripts from admin-ops
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2697] clm: Use base::Process to execute scripts from admin-ops** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 21, 2017 05:15 PM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:18 PM UTC **Owner:** nobody Refer to this mailing list post: [opensaf-devel](https://sourceforge.net/p/opensaf/mailman/message/36092893/) Instead of executing the custom script by calling system(), we should use the functionality provided in base/process.h. This is preferred because it executes the script with a well defined environment (only the PATH environment variable is set, with a fixed value). Otherwise, all environment variables from clmna will leak into the script. Any change in environment variables in clmna could then be a non-backwards compatible change, if the user defined script depends on the value of that variable. Another benefit of the base/process.h code is that it lets us specify a time-out. We ought to have a time-out for the script execution, and execute the script in a separate thread to avoid blocking the main thread in clmna. This could be implemented in a similar way as for executing the scale-out script in CLM. --- 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
[tickets] [opensaf:tickets] #2671 base: agent log is streamed to incorrect location
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2671] base: agent log is streamed to incorrect location** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 07, 2017 09:11 AM UTC by Vu Minh Nguyen **Last Updated:** Tue Feb 06, 2018 10:41 AM UTC **Owner:** nobody Agent trace log now is always located at `$PKGLOGDIR` when enabled. Location of agent trace log does not point to the one which is given by the enviroment such as `IMMA_TRACE_PATHNAME` for IMMA. --- 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
[tickets] [opensaf:tickets] #2656 imm: valgrind reports invalid read in imm agent
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2656] imm: valgrind reports invalid read in imm agent** **Status:** assigned **Milestone:** 5.18.12 **Created:** Thu Oct 26, 2017 04:15 AM UTC by Vu Minh Nguyen **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** Vu Minh Nguyen Here is valgrind report: > ==740== Thread 4: > ==740== Invalid read of size 1 > ==740==at 0x4C2E7A0: __strncpy_sse2_unaligned (in > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > ==740==by 0x5055CF2: strncpy (string3.h:120) > ==740==by 0x5055CF2: imma_proc_ccbaug_setup(imma_client_node*, > imma_callback_info*) (imma_proc.cc:2058) > ==740==by 0x505C507: imma_hdl_callbk_dispatch_one(imma_cb*, unsigned long > long) (imma_proc.cc:1745) > ==740==by 0x5050D33: saImmOiDispatch (imma_oi_api.cc:638) > ==740==by 0x120AD1: oi_thread (test_saImmOiSaStringT.c:287) > ==740==by 0x5725183: start_thread (pthread_create.c:312) > ==740==by 0x5A3537C: clone (clone.S:111 --- 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
[tickets] [opensaf:tickets] #2644 base: Inconsistent LogMessage::String constructors
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2644] base: Inconsistent LogMessage::String constructors** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 11:14 AM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody The base::LogMessage::String class has two constructors, one taking a "size" parameter and a another taking a "max_size" parameter. For former constructor seems to be unused, and can be removed. --- 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
[tickets] [opensaf:tickets] #2633 smf: refactor smfd folders
- **Milestone**: 5.18.04 --> future --- ** [tickets:#2633] smf: refactor smfd folders** **Status:** unassigned **Milestone:** future **Created:** Tue Oct 17, 2017 11:52 AM UTC by Rafael Odzakow **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody --- 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
[tickets] [opensaf:tickets] #2612 amfd: return SA_AIS_ERR_NO_RESOURCES for CSI CCB if SG is unstable
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2612] amfd: return SA_AIS_ERR_NO_RESOURCES for CSI CCB if SG is unstable** **Status:** assigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 03:23 PM UTC by Alex Jones **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** Alex Jones Return SA_AIS_ERR_NO_RESOURCES if CSI ccb apply fails due to SG being unstable. This is similar to ticket #2184, but for CSIs. --- 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
[tickets] [opensaf:tickets] #2568 amfnd: invalid read in cbq.cc
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2568] amfnd: invalid read in cbq.cc** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Fri Sep 01, 2017 05:31 AM UTC by Gary Lee **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody Noticed when running valgrind. ==195== Invalid read of size 8 ==195==at 0x118F70: avnd_evt_tmr_cbk_resp_evh(avnd_cb_tag*, avnd_evt_tag*) (cbq.cc:636) ==195==by 0x142DEA: avnd_evt_process (main.cc:658) ==195==by 0x142DEA: avnd_main_process() (main.cc:610) ==195==by 0x116B81: main (main.cc:203) ==195== Address 0x800b1c0 is 64 bytes inside a block of size 112 free'd ==195==at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==195==by 0x118CBE: avnd_comp_cbq_rec_pop_and_del(avnd_cb_tag*, avnd_comp_tag*, avnd_cbk_tag*, bool) (cbq.cc:930) ==195==by 0x118F6F: avnd_evt_tmr_cbk_resp_evh(avnd_cb_tag*, avnd_evt_tag*) (cbq.cc:636) ==195==by 0x142DEA: avnd_evt_process (main.cc:658) ==195==by 0x142DEA: avnd_main_process() (main.cc:610) ==195==by 0x116B81: main (main.cc:203) ==195== Block was alloc'd at ==195==at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==195==by 0x11AD18: avnd_comp_cbq_rec_add(avnd_cb_tag*, avnd_comp_tag*, avsv_amf_cbk_info_tag*, unsigned long*, long long) (cbq.cc:955) ==195==by 0x11AE85: avnd_comp_cbq_send(avnd_cb_tag*, avnd_comp_tag*, unsigned long*, unsigned long long, avsv_amf_cbk_info_tag*, long long) (cbq.cc:715) ==195==by 0x128162: avnd_comp_cbk_send(avnd_cb_tag*, avnd_comp_tag*, avsv_amf_cbk_type, avnd_hc_rec_tag*, avnd_comp_csi_rec*) (comp.cc:2164) ==195==by 0x123558: avnd_comp_clc_inst_restart_hdler(avnd_cb_tag*, avnd_comp_tag*) (clc.cc:2218) ==195==by 0x124B5C: avnd_comp_clc_fsm_run(avnd_cb_tag*, avnd_comp_tag*, avnd_comp_clc_pres_fsm_ev) (clc.cc:861) ==195==by 0x12C1BF: comp_restart_initiate(avnd_comp_tag*) (comp.cc:2767) ==195==by 0x12C4EB: avnd_evt_comp_admin_op_req(avnd_cb_tag*, avnd_evt_tag*) (comp.cc:2822) ==195==by 0x1361AA: avnd_evt_avd_admin_op_req_evh(avnd_cb_tag*, avnd_evt_tag*) (di.cc:1583) ==195==by 0x142DEA: avnd_evt_process (main.cc:658) ==195==by 0x142DEA: avnd_main_process() (main.cc:610) ==195==by 0x116B81: main (main.cc:203) --- 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
[tickets] [opensaf:tickets] #2541 nid: order of system log print out is not correct
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2541] nid: order of system log print out is not correct** **Status:** review **Milestone:** 5.18.12 **Created:** Wed Aug 02, 2017 07:52 AM UTC by Rafael Odzakow **Last Updated:** Fri Feb 02, 2018 12:17 PM 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2532 mds: TCP SVC_UP event is not received after subscribing
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2532] mds: TCP SVC_UP event is not received after subscribing** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Fri Jul 21, 2017 05:59 AM UTC by Hung Nguyen **Last Updated:** Fri Feb 02, 2018 12:17 PM 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2518 smf: Incorrect handling of version when initializing OpenSAF APIs
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2518] smf: Incorrect handling of version when initializing OpenSAF APIs** **Status:** accepted **Milestone:** 5.18.12 **Created:** Fri Jun 30, 2017 12:53 PM UTC by elunlen **Last Updated:** Mon Apr 09, 2018 11:45 AM UTC **Owner:** syam prasad talluri A general problem when initializing OpenSAF APIs is found. This problem applies to all OpenSAF services and all other code using OpenSAF APIs, including test code, shell tools etc. The version used when initializing the API is in many cases stored in a global variable and this global variable is used every time the API is initialized. The version is given as a pointer to this variable. The problem is that this variable is defined as an [in/out] parameter that gives the version to use when initializing [in] but the value shall be changed by the agent to the highest version supported by the initialized service [out]. This means that the next time the API is initialized it may be initialized with a higher version. A higher version may not be backwards compatible with the intended version. Even if this is not causing any problems now it may in the future when new features are added. An example is IMM that has a highest version A, 2, 18. If this version is used IMM will handle CLM nodes in a different way than if initialized with a lower version. For example, new return codes have to be handled. --- 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
[tickets] [opensaf:tickets] #2526 amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is escalated (>= 2SIs)** **Status:** unassigned **Milestone:** 5.18.12 **Labels:** nodegroup timeout **Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau **Last Updated:** Mon Mar 05, 2018 01:30 AM UTC **Owner:** nobody **Attachments:** - [app3_twon3su3si.xml](https://sourceforge.net/p/opensaf/tickets/2526/attachment/app3_twon3su3si.xml) (14.6 kB; text/xml) - Configuration: 2N app, 3SI (model is attached), SU4/SU5 are hosted on PL4/PL5 respectively - Steps: . Create nodegroup consists of PL4/PL5 . Unlock ng . SU4 is assigned ACTIVE . While component of SU5 is being assigned STANDBY, kill a component of SU4 to escalate to a SuFailover . SU4 is now getting STANDBY assignment, SU5 is getting ACTIVE assignment . But the command unlock ng is being hold until TIMEOUT Note: Repeat the same test with only **1 SI**, the command unlock ng returns OK --- 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
[tickets] [opensaf:tickets] #2503 osaf: Store lock files under /var/lock to comply with FHS
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2503] osaf: Store lock files under /var/lock to comply with FHS** **Status:** accepted **Milestone:** 5.18.12 **Created:** Tue Jun 20, 2017 08:19 AM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** Anders Widell OpenSAF currently creates lock files under /var/lock/subsys, but this is non-standard. [FHS](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html) only specifies /var/lock, and some Linux distributions like [Ubuntu](http://manpages.ubuntu.com/manpages/zesty/en/man7/hier.7.html) don't have a /var/lock/subsys directory. Alternatively, get rid of the lock files altogether and rely only on PID files stored under /run. A PID file should be enough to avoid running more than one instance of the service concurrently. We can consider making opensafd (NID) a permanent service that manages all other OpenSAF services which shall be up and running for as long as OpenSAF is running. --- 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
[tickets] [opensaf:tickets] #2501 plm: Build error when using GCC 7.1.1 and -O3 optimization
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2501] plm: Build error when using GCC 7.1.1 and -O3 optimization** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Jun 19, 2017 01:22 PM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody The following compilation error is seen when using GCC 7.1.1 and -O3 optimization level: ~~~ CC src/plm/plmd/bin_osafplmd-plms_plmc.o src/plm/plmd/plms_mbcsv.c: In function ‘plms_edu_enc_trk_step_info_data’: src/plm/plmd/plms_mbcsv.c:1013:2: error: ‘msg_hdr.data_len’ may be used uninitialized in this function [-Werror=maybe-uninitialized] ncs_encode_32bit(, header.data_len); ^ src/plm/plmd/plms_mbcsv.c:1061:20: note: ‘msg_hdr.data_len’ was declared here PLMS_MBCSV_HEADER msg_hdr; ^~~ src/plm/plmd/plms_mbcsv.c:1011:2: error: ‘msg_hdr’ may be used uninitialized in this function [-Werror=maybe-uninitialized] ncs_encode_32bit(, header.msg_type); ^ src/plm/plmd/plms_mbcsv.c:1061:20: note: ‘msg_hdr’ was declared here PLMS_MBCSV_HEADER msg_hdr; ^~~ CC src/plm/plmd/bin_osafplmd-plms_proc.o src/plm/plmd/plms_mbcsv.c: In function ‘plms_edu_enc_entity_grp_info_data’: src/plm/plmd/plms_mbcsv.c:1013:2: error: ‘msg_hdr.data_len’ may be used uninitialized in this function [-Werror=maybe-uninitialized] ncs_encode_32bit(, header.data_len); ^ src/plm/plmd/plms_mbcsv.c:1294:20: note: ‘msg_hdr.data_len’ was declared here PLMS_MBCSV_HEADER msg_hdr; ^~~ src/plm/plmd/plms_mbcsv.c: In function ‘plms_edu_enc_client_info_data’: src/plm/plmd/plms_mbcsv.c:1013:2: error: ‘msg_hdr.data_len’ may be used uninitialized in this function [-Werror=maybe-uninitialized] ncs_encode_32bit(, header.data_len); ^ src/plm/plmd/plms_mbcsv.c:1400:20: note: ‘msg_hdr.data_len’ was declared here PLMS_MBCSV_HEADER msg_hdr; ^~~ cc1: all warnings being treated as errors make[2]: *** [Makefile:15601: src/plm/plmd/bin_osafplmd-plms_mbcsv.o] Error 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2468 amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2468] amf: amfd asserts while decrementing opensaf NoRed SI assignment counter during fail-over.** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu May 25, 2017 08:46 AM UTC by Praveen **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody Ticket is based on a issue reported via user list mail dated: 22-May-17, subject "[users] osafamfd coredump issue. Here is syslog when the issue occurred: 2017-05-01T07:52:57.714906-04:00 scm2 kernel: tipc: Resetting link <1.1.16:eth2-1.1.5:bond0>, peer not responding 2017-05-01T07:52:57.714935-04:00 scm2 kernel: tipc: Lost link <1.1.16:eth2-1.1.5:bond0> on network plane A 2017-05-01T07:52:57.714939-04:00 scm2 kernel: tipc: Lost contact with <1.1.5> 2017-05-01T07:52:57.716788-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 25 (change:4, dest:287038266327043) 2017-05-01T07:52:57.717304-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. Not sending track callback for agents on that node 2017-05-01T07:52:57.719178-04:00 scm2 osafimmnd[3020]: NO Global discard node received for nodeId:1050f pid:15395 2017-05-01T07:52:57.719233-04:00 scm2 osafimmnd[3020]: NO Implementer disconnected 104 <0, 1050f(down)> (MsgQueueService66831) 2017-05-01T07:52:57.721345-04:00 scm2 osafamfd[4277]: NO Node 'PLD0105' left the cluster 2017-05-01T07:52:57.722778-04:00 scm2 log_demo[6160]: [0.I.Proc]: FYI state change notification from NTF, entity PLD0105 now has new state DISABLED (Oper state safAmfNode=PLD0105,safAmfCluster=myAmfCluster changed) 2017-05-01T07:52:57.732796-04:00 scm2 osafamfd[4277]: su.cc:2006: dec_curr_act_si: Assertion 'saAmfSUNumCurrActiveSIs > 0' failed. 2017-05-01T07:52:57.778777-04:00 scm2 kernel: tipc: Resetting link <1.1.16:eth2-1.1.6:bond0>, peer not responding 2017-05-01T07:52:57.778827-04:00 scm2 kernel: tipc: Lost link <1.1.16:eth2-1.1.6:bond0> on network plane A 2017-05-01T07:52:57.778833-04:00 scm2 kernel: tipc: Lost contact with <1.1.6> 2017-05-01T07:52:57.777979-04:00 scm2 osafimmd[3009]: NO MDS event from svc_id 25 (change:4, dest:288139774320643) 2017-05-01T07:52:57.717343-04:00 scm2 osafclmd[4259]: NO Node 66831 went down. Not sending track callback for agents on that node 2017-05-01T07:52:57.779373-04:00 scm2 osafclmd[4259]: NO Node 67087 went down. Not sending track callback for agents on that node 2017-05-01T07:52:57.780552-04:00 scm2 osafimmnd[3020]: NO Global discard node received for nodeId:1060f pid:17439 2017-05-01T07:52:57.780607-04:00 scm2 osafimmnd[3020]: NO Implementer disconnected 106 <0, 1060f(down)> (MsgQueueService67087) 2017-05-01T07:52:57.810785-04:00 scm2 osafamfnd[5281]: WA AMF director unexpectedly crashed 2017-05-01T07:52:57.810839-04:00 scm2 osafamfnd[5281]: Rebooting OpenSAF NodeId = 69647 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, OwnNodeId = 69647, SupervisionTime = 0 2017-05-01T07:52:57.810978-04:00 scm2 osafimmnd[3020]: NO Implementer locally disconnected. Marking it as doomed 105 <29, 1100f> (safAmfService) 2017-05-01T07:52:57.812582-04:00 scm2 osafimmnd[3020]: NO Implementer disconnected 105 <29, 1100f> (safAmfService) 2017-05-01T07:52:57.950567-04:00 scm2 opensaf_reboot: Rebooting local node; timeout=0 2017-05-01T07:52:58.084968-04:00 scm2 atwdog[28335]: rebooting (-f) local node --- 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
[tickets] [opensaf:tickets] #2500 build: Schema files (.xsd) are missing from distribution tarballs
- **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2500] build: Schema files (.xsd) are missing from distribution tarballs** **Status:** accepted **Milestone:** 5.18.12 **Created:** Fri Jun 16, 2017 10:45 AM UTC by Anders Widell **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** Anders Widell The XML schema (xsd) files are missing in the release tarballs, at least for IMM and probably also for SMF. --- 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
[tickets] [opensaf:tickets] #2456 mds: NCSMDS_DOWN is sent with adest
- **Priority**: minor --> major - **Milestone**: 5.18.04 --> 5.18.12 --- ** [tickets:#2456] mds: NCSMDS_DOWN is sent with adest** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue May 09, 2017 04:38 AM UTC by Long H Buu Nguyen **Last Updated:** Fri Feb 02, 2018 12:17 PM UTC **Owner:** nobody **Attachments:** - [PL-4.zip](https://sourceforge.net/p/opensaf/tickets/2456/attachment/PL-4.zip) (64.7 kB; application/x-zip-compressed) - Description: When SCs are rebooted repeatedly, there is a case that NCSMDS_DOWN is sent to PLs with only adest. This causes amfnd can not detect both SCs down to get into headless state. As observed in logs: At 10:48:00, SC1 was off , SC2 was still alive 2017-03-09 10:47:58 SC-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="273" x-info="http://www.rsyslog.com;] exiting on signal 15. 2017-03-09 10:48:06 SC-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="268" x-info="http://www.rsyslog.com;] start SC2 was going down at 10:48:02 2017-03-09 10:48:02 SC-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="239" x-info="http://www.rsyslog.com;] exiting on signal 15. 2017-03-09 10:48:03 SC-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="270" x-info="http://www.rsyslog.com;] start So after 10:48:04, the cluster actually went into headless. But NCSMDS_DOWN events received at amfnd was ADEST, so it was ignored. That resulted in @is_avd_down still FALSE Mar 9 10:48:00.930820 osafamfnd [422:src/amf/amfnd/di.cc:0602] >> avnd_evt_mds_avd_dn_evh Mar 9 10:48:00.930826 osafamfnd [422:src/amf/amfnd/di.cc:0609] << avnd_evt_mds_avd_dn_evh ... Mar 9 10:48:04.517247 osafamfnd [422:src/amf/amfnd/di.cc:0602] >> avnd_evt_mds_avd_dn_evh Mar 9 10:48:04.517254 osafamfnd [422:src/amf/amfnd/di.cc:0609] << avnd_evt_mds_avd_dn_evh The next SC restart, amfnd received NCSMDS_NEW_ACTIVE. Mar 9 10:48:10.187820 osafamfnd [422:src/amf/amfnd/mds.cc:0540] NO AVD NEW_ACTIVE, adest:1 But with @is_avd_down as FALSE, amfnd did not send sync state info because amfnd thought that the cluster were NOT going into headless. Compare to previous SC restart in the same test, one of NCSMDS_DOWN events must be vdest Mar 9 10:47:50.565629 osafamfnd [422:src/amf/amfnd/di.cc:0602] >> avnd_evt_mds_avd_dn_evh Mar 9 10:47:50.565685 osafamfnd [422:src/amf/amfnd/di.cc:0617] WA AMF director unexpectedly crashed ... Mar 9 10:47:50.565874 osafamfnd [422:src/amf/amfnd/di.cc:0602] >> avnd_evt_mds_avd_dn_evh Mar 9 10:47:50.565879 osafamfnd [422:src/amf/amfnd/di.cc:0609] << avnd_evt_mds_avd_dn_evh --- 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
[tickets] [opensaf:tickets] #2826 imm: potential leak of memory pointed to by ao_node in OM API
- **Milestone**: 5.18.04 --> future
---
** [tickets:#2826] imm: potential leak of memory pointed to by ao_node in OM
API**
**Status:** accepted
**Milestone:** future
**Created:** Wed Apr 04, 2018 03:32 AM UTC by Vu Minh Nguyen
**Last Updated:** Wed Apr 04, 2018 03:32 AM UTC
**Owner:** Vu Minh Nguyen
The allocated memory `ao_node` should be freed before going to `lock_fail` in
below code:
::: C++
/* Allocate the IMMA_ADMIN_OWNER_NODE & Populate */
ao_node = calloc(1, sizeof(IMMA_ADMIN_OWNER_NODE));
...
mds_send_fail:
if (m_NCS_LOCK(>cb_lock, NCS_LOCK_WRITE) != NCSCC_RC_SUCCESS) {
rc = SA_AIS_ERR_LIBRARY;
**goto lock_fail;**
}
locked = true;
admin_owner_node_free:
if (ao_node != NULL) {
free(ao_node);
ao_node = NULL;
}
lock_fail:
if (out_evt) free(out_evt);
return rc;
}
---
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
[tickets] [opensaf:tickets] #2881 base: Load/reload service config file
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2881] base: Load/reload service config file** **Status:** wontfix **Milestone:** future **Created:** Thu Jun 21, 2018 09:12 AM UTC by Minh Hon Chau **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Currently we are using SIGUSR2 to enable/disable daemon tracing. Since new log/trace facilities are being added/introduced in #2306 and #456, and the features need to be disabled/enabled at runtime too. This ticket aims to use SIGUSR2 to load/reload the service config file, so that the log/trace facilities can be on/off at runtime. --- 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
[tickets] [opensaf:tickets] #2597 clm: Dynamically assign node id when node joins the cluster
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2597] clm: Dynamically assign node id when node joins the cluster** **Status:** accepted **Milestone:** 5.18.12 **Created:** Tue Sep 26, 2017 10:21 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell Related to ticket [#2157]. CLM should be able to dynamically assign a free node id to a node when it joins the cluster. The use-case for this is a dynamic environment (e.g. cloud) where it is difficult or impossible for the node itself to choose a unique node id - since it cannot know the node id's of the other nodes in the cluster before joining. The CLM server on the other hand knows what node ids of all the current cluster members, and can therefore safely assign a free node id to the node when it joins the cluster. --- 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
[tickets] [opensaf:tickets] #2598 clm: Automatically detect the node address when using TIPC
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2598] clm: Automatically detect the node address when using TIPC** **Status:** assigned **Milestone:** 5.18.12 **Created:** Tue Sep 26, 2017 10:25 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell As a follow-up to ticket [#2489], the CLM node agent could determine its own IP address automatically when using TIPC and the user hasn't configured any preferred address in /etc/opensaf/clmna.conf. If the node has multiple IP addresses, we should make a reasonable choice - perhaps by picking an IP address from one of the TIPC bearer interfaces. --- 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
[tickets] [opensaf:tickets] #2606 dtm: Remove configuration of TCP send and receive buffer size
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2606] dtm: Remove configuration of TCP send and receive buffer size** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 10:59 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody There is a configuration option DTM_SOCK_SND_RCV_BUF_SIZE for configuring the TCP send and receive buffer size. This option ought to be removed, since the kernel usually does a better job at setting the apropriate buffer size automatically. --- 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
[tickets] [opensaf:tickets] #2583 log: refactor lgs_imm code
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2583] log: refactor lgs_imm code** **Status:** assigned **Milestone:** future **Created:** Thu Sep 14, 2017 09:33 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Vu Minh Nguyen This ticket is for refactoring lgs_imm.cc file. Will add detailed informatoin later. --- 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
[tickets] [opensaf:tickets] #2564 dtm: Remove DTM_UDP_BCAST_SND_PORT configuration option
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2564] dtm: Remove DTM_UDP_BCAST_SND_PORT configuration option** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Aug 21, 2017 02:05 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The DTM_UDP_BCAST_SND_PORT configuration option seems to be unused and can be removed. --- 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
[tickets] [opensaf:tickets] #2556 split-brain should be reported by a ER or CR in syslog
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2556] split-brain should be reported by a ER or CR in syslog** **Status:** review **Milestone:** 5.18.12 **Created:** Wed Aug 16, 2017 11:57 AM UTC by Per Rodenvall **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Vo Minh Hoang This was seen in syslog: 2017-06-27 13:49:32 SC-1 osafrded[176]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: Split-brain detected, OwnNodeId = 131343, SupervisionTime = 60 In our testing we look for ER and CR after each test. We really like split-brain to be a ER or CR --- 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
[tickets] [opensaf:tickets] #2562 dtm: Remove special receive logic during initial discovery phase
- **Milestone**: 5.18.09 --> 5.18.12
---
** [tickets:#2562] dtm: Remove special receive logic during initial discovery
phase**
**Status:** unassigned
**Milestone:** 5.18.12
**Created:** Fri Aug 18, 2017 08:22 AM UTC by Anders Widell
**Last Updated:** Thu Aug 30, 2018 12:45 PM UTC
**Owner:** nobody
DTM used to have a special *initial discovery phase*. However, as a result of
ticket [#2522], the nodes will keep sending broadcast messages indefinitely, so
there is no longer any special "discovery phase" - discovery can happen at any
time. Therefore, the special logic used only during the initial discovery phase
shall be removed. Otherwise, the special logic can hide bugs that actually can
happen at any time, albeit with lower probability:
~~~
if (initial_discovery_phase == true) {
if (node.node_id < dtms_cb->node_id) {
TRACE(
"DTM: received node_id is less than local node_id dropping
message cluster_id: %d node_id: %u",
node.cluster_id, node.node_id);
return sock_desc;
}
}
~~~
---
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
[tickets] [opensaf:tickets] #2561 dtm: Re-factor the intra-node poll loop
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2561] dtm: Re-factor the intra-node poll loop** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Fri Aug 18, 2017 07:51 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Re-factor the intra-node poll loop in a similar was as was done with the inter-node poll loop in ticket [#2240] (remove the fixed-size poll vector with epoll). The DTM_INTRANODE_MAX_PROCESSES configuration will no longer be needed as a result of this change, and shall be removed. --- 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
[tickets] [opensaf:tickets] #2557 dtm: Use edge-triggered epoll
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2557] dtm: Use edge-triggered epoll** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Aug 16, 2017 12:26 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody To improve performance, DTM should use edge-triggered epoll. Some mechanism to guarantee fairness is probably needed for this to work well, and should be implemented at the same time. --- 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
[tickets] [opensaf:tickets] #2560 dtm: Use SOCK_SEQPACKET for intra-node communication
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2560] dtm: Use SOCK_SEQPACKET for intra-node communication** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Aug 17, 2017 01:29 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody DTM currently uses SOCK_STREAM for intra-node communication, which means that it needs logic to be able to receive partial messages. By using SOCK_SEQPACKET, we can remove this logic since only full messages can be sent and received. Also investigate the possibility to use base::UnixSocket. --- 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
[tickets] [opensaf:tickets] #2479 clm: Provide all current addresses of a CLM node
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2479] clm: Provide all current addresses of a CLM node** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Fri Jun 02, 2017 08:33 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The CLM node object has two runtime attributes, saClmNodeCurrAddress and saClmNodeCurrAddressFamily, that provide the current address of the CLM node. However, these attributes are single-value and a node can have multiple addresess. In particular, if OpenSAF is using TIPC as transport, a user might be interested in knowing the IP address of the node as well. A node can of course also have several IP addresses. One possible solution is to make the existing saClmNodeCurrAddress and saClmNodeCurrAddressFamily attributes mult-value. Another possibility is to add two new multi-value attributes for storing all the addresses. -- As pointed out by Zoran, multi-value attributes are unordered so it is not possible to correlate which address family value corresponds to which address. So the list of addresses must be stored in one single multi-value attribute, or maybe one single string containing a comma-separated list of addresses. --- 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
[tickets] [opensaf:tickets] #2511 pysaf: Use str.format() instead of printf-style string formatting
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2511] pysaf: Use str.format() instead of printf-style string formatting** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Jun 26, 2017 11:07 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody [Printf-style string formatting](https://docs.python.org/3/library/stdtypes.html#old-string-formatting) have a number of problems and the recommended way to format strings is to instead use the [str.format()](https://docs.python.org/3/library/stdtypes.html#str.format) method. This ticket proposes to convert existing uses of printf-style string formatting with str.format(). --- 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
[tickets] [opensaf:tickets] #2537 base: Provide a stable boot time stamp using a cache
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2537] base: Provide a stable boot time stamp using a cache** **Status:** assigned **Milestone:** 5.18.12 **Created:** Mon Jul 31, 2017 09:59 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell As an improvement to ticket [#2535], cache the boot time stamp under /var/lib/opensaf and use the cached value when available. This will ensure that the boot time stamp will remain stable, even in the presentce of measurement inaccuracy and system clock drift. --- 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
[tickets] [opensaf:tickets] #2473 base: Add pidfile handling support functions
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2473] base: Add pidfile handling support functions** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue May 30, 2017 10:27 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell As a follow-up to ticket [#2432], create support functions similar in functionality to the BSD pidfile_open(), pidfile_write() and pidfile_close(). See https://www.freebsd.org/cgi/man.cgi?query=pidfile_open=3=0=FreeBSD+12-current --- 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
[tickets] [opensaf:tickets] #2471 pyosaf: Generate the AIS Python bindings from the C header files
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2471] pyosaf: Generate the AIS Python bindings from the C header files** **Status:** accepted **Milestone:** 5.18.12 **Created:** Tue May 30, 2017 10:21 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell The existing Python bindings have been created by hand. This causes several problems: * The python bindings have not (always) been updated when the C header files have been modified, for example when adding a new OpenSAF extension. It is also difficult to know if the python bindings are complete or if some function is missing * There is a risk for typos and copy-paste bugs when manually translating the C header files to Python * Because of the risk for typos, all API functions and structure definitions must be tested individually * Due to the manual effort, there is a risk for inconsistencies in how different C functions are mapped to Python - especially over time if different people are working with the bindings To solve the above mentioned probelms, the suggestion is to instead translate the C header files to Python automatically at build time. --- 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
[tickets] [opensaf:tickets] #2454 amfnd: Clean up variable of active amfd status
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2454] amfnd: Clean up variable of active amfd status** **Status:** review **Milestone:** 5.18.12 **Created:** Thu May 04, 2017 12:34 PM UTC by Minh Hon Chau **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Minh Hon Chau In amfnd, we have variable cb->is_avd_down and set of macros: m_AVND_CB_IS_AVD_UP, m_AVND_CB_AVD_UP_SET, m_AVND_CB_AVD_UP_RESET which is using flag AVND_CB_FLAG_AVD_UP, they are all indicating active amfd down/up. Amfnd should only use variable @is_avd_down or the macros, not both of them. --- 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
[tickets] [opensaf:tickets] #2451 clm: Make the cluster reset admin op safe
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2451] clm: Make the cluster reset admin op safe** **Status:** review **Milestone:** 5.18.12 **Created:** Wed May 03, 2017 10:51 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Hans Nordebäck The cluster reset admin operation that was implemented in ticket [#2053] is not safe: if a node reboots very fast it can come up again and join the old cluster before other nodes have rebooted. See mail discussion: https://sourceforge.net/p/opensaf/mailman/message/35398725/ This can be solved by implementing a two-phase cluster reset or by introducing a cluster generation number which is increased at each cluster reset (maybe both ordered an spontaneous cluster resets). A node will not be allowed to join the cluster with a different cluster genration without first rebooting. --- 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
[tickets] [opensaf:tickets] #2448 osaf: Provide shared libraries for uninstalled OpenSAF services
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2448] osaf: Provide shared libraries for uninstalled OpenSAF services** **Status:** assigned **Milestone:** 5.18.12 **Created:** Wed May 03, 2017 10:27 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell Make it possible for OpenSAF services as well as applications to detect if an OpenSAF RPM for a particular OpenSAF service is not installed, by providing a thin library that returns e.g. SA_AIS_ERR_NOT_SUPPORTED from all API functions. This would make it possible to start an OpenSAF service or application which is linked dynamically against an AIS service which isn't installed on the system. --- 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
[tickets] [opensaf:tickets] #2449 osaf: Avoid conditional compilation when possible
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2449] osaf: Avoid conditional compilation when possible** **Status:** assigned **Milestone:** 5.18.12 **Created:** Wed May 03, 2017 10:35 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell Related to ticket [#2448]. OpenSAF currently has a number of C preprocessor macros that control conditional compilation using #ifdef in the source code. This has a number of problems: * It makes testing more complex - we need to create one OpenSAF build for each possible combination of enabled/disabled macros and test each build. * ifdefs can confuse static code analysis tools - and humans as well. * This can make it impossible to choose at installation time which OpenSAF RPMs to install on the system, see ticket [#2448]. This ticket suggests that conditional compilation shall be removed when possible. One possible exception could be an OSAF_ENABLE_DEBUG macro that can create a separate debug build of OpenSAF. A debug build has some benefits for testing and trouble shooting but shouldn't be installed on a production system. --- 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
[tickets] [opensaf:tickets] #2149 log: refactor handling IMM in log service
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2149] log: refactor handling IMM in log service ** **Status:** accepted **Milestone:** 5.18.12 **Created:** Fri Oct 28, 2016 12:25 PM UTC by elunlen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Vu Minh Nguyen This ticket intends to do refactor stuffs related to IMM handling in log service. More details will come later. With first look, we see many places using IMM APIs, and refering to IMM OI handler. It would be very good if we could move this into one or several files that are purely dedicated to IMM handling, with a well-defined 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2445 log: reorganize headers and implementation
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2445] log: reorganize headers and implementation** **Status:** review **Milestone:** 5.18.12 **Created:** Fri Apr 28, 2017 08:28 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Canh Truong This ticket intends to do some enhancements: 1) Put public interfaces and its implementations in proper places (e.g: lgs_amf_init() interface could be put into lgs_amf.h file) 2) Fix all cppcheck messages 3) Fix all cpplint messages 4) Replace NULL by nullptr Will divide the fix to several increaments. The purpose is to make the review patch small and avoid code rebasing. The work could be fixing all above items for few files, then send it out for review. --- 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
[tickets] [opensaf:tickets] #1632 log: not handle AIS error codes properly
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#1632] log: not handle AIS error codes properly ** **Status:** assigned **Milestone:** 5.18.12 **Created:** Thu Dec 10, 2015 04:12 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Ratnamala Talari OpenSAF LOG in some places does not handle AIS codes properly. For example, there is a case calling to saLogStreamOpen_2() will get `SA_AIS_ERR_NOT_SUPPORTED` error code, but in AIS A.02.01, that error code is not in the list of possible returned error codes of the API. More information, refer to the ticket [#1607] --- 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
[tickets] [opensaf:tickets] #592 LOG: saLogStreamPathName is not writable in stream config class
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#592] LOG: saLogStreamPathName is not writable in stream config class** **Status:** accepted **Milestone:** 5.18.12 **Created:** Thu Oct 10, 2013 01:40 PM UTC by elunlen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Ratnamala Talari In IMM model attribute saLogStreamPathName in class SaLogStreamConfig is SA_CONFIG but not SA_WRITABLE. This means that this attribute cannot be modified or error handled in the log service 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #333 amf: saAmfHealthcheckStart returns SA_AIS_ERR_NOT_EXIST when SA_AMF_COMPONENT_NAME is not exported.
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#333] amf: saAmfHealthcheckStart returns SA_AIS_ERR_NOT_EXIST when SA_AMF_COMPONENT_NAME is not exported.** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon May 27, 2013 04:48 AM UTC by Praveen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2113. Unless SA_AMF_COMPONENT_NAME is not exported, health check is not started for unregistered process. As APPENDIX B on page 442 specifies that saAmfHealthcheckStart can be called in the context of any process , whether it is not registered or not --- 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
[tickets] [opensaf:tickets] #2607 dtm: Separate CLC-CLI of osaftransportd and osafdtmd
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2607] dtm: Separate CLC-CLI of osaftransportd and osafdtmd** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:37 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Currently, the opensaf-transport CLC-CLI script calls the opensaf-dtm CLC-CLI script. This mess should be cleaned up so that osaf-dtm is called directly from NID. --- 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
[tickets] [opensaf:tickets] #2611 dtm: Allow the list of peer IP addresses to change in runtime
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2611] dtm: Allow the list of peer IP addresses to change in runtime** **Status:** assigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:55 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell When using unicast, the list of peer IP addresses is retrieved from a file or by using a DNS query at startup. We can use e.g. inotify to detect when the file has been updated, and re-read the file when this happens. For the DNS case, we can make new DNS queries periodically. --- 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
[tickets] [opensaf:tickets] #2692 dtm: Implement health check between osafdtmd and osaftransportd
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2692] dtm: Implement health check between osafdtmd and osaftransportd** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 21, 2017 01:24 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Use the new command interface implemented in ticket [#2646] to send health check messages from osafdtmd to osaftransportd, say once per minute. If osafdtmd has not received any reply from osaftransportd within another minute, it shall be considered hung. osaftransportd can also use the same health check messages to detect a hanging osafdtmd process; if no health check message has been received from osafdtmd within two minutes, osafdtmd shall be considered hung. --- 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
[tickets] [opensaf:tickets] #2691 dtm: Use a separate thread in osaftransportd for monitoring osafdtmd
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2691] dtm: Use a separate thread in osaftransportd for monitoring osafdtmd** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 21, 2017 01:20 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Use a separate thread in osaftransportd dedicated to monitoring osfdtms, instead of using the main thread for this task. The reason is that the main thread can be busy handling log events - especially when tracing is enabled. Also, file system operations may hang in certain situations, for example when using NFS. --- 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
[tickets] [opensaf:tickets] #2690 base: Add thread class similar to std::thread
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2690] base: Add thread class similar to std::thread** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 21, 2017 01:11 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Add a base::thread class similar to the one found in the C++ standard library. One reason for adding our own variant is that Google C++ style guide forbids inclusion of the header file with the following message: ~~~ is an unapproved C++11 header. [build/c++11] [5] ~~~ Another reason is that we can add our own functionality and eventually replace the old ncssysf_tsk.h interface. --- 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
[tickets] [opensaf:tickets] #2689 rde: Use base::UnixSocket for communication between server and agent
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2689] rde: Use base::UnixSocket for communication between server and agent** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Tue Nov 21, 2017 01:02 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Use the UnixSocket class in base for communication between the RDE server and the RDE agent. The UnixSocket class may need some adaptation in order to support the functionality needed by RDE (detection of connection loss). --- 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
[tickets] [opensaf:tickets] #2645 dtm: Use validation functions from base::LogMessage to valida log stream MSGID
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2645] dtm: Use validation functions from base::LogMessage to valida log stream MSGID** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 11:16 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody the base::LogMessage class already has functions for validating the MSGID field of log messages. This could be re-used, with the addition that we should reject slashes as well to prevent directory traversal (for security reasons). --- 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
[tickets] [opensaf:tickets] #2643 base: Validate the name of the trace log stream
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2643] base: Validate the name of the trace log stream** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 11:06 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Validate the name of the trace log file (sent in the MSGID field of the log record). If the name is invalid or too long, use the OpenSAF has function to generate a substitute MSGID. --- 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
[tickets] [opensaf:tickets] #2672 amfnd: refactor sc absence checks
- **status**: accepted --> unassigned - **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2672] amfnd: refactor sc absence checks** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Nov 08, 2017 12:36 AM UTC by Gary Lee **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Gary Lee Write a function that returns a state (eg SC_ABSENT, SC_SYNCING, SC_SYNCED), instead of directly checking these variables: cb->is_avd_down == true || cb->amfd_sync_required == true cb->is_avd_down == true && cb->amfd_sync_required == true --- 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
[tickets] [opensaf:tickets] #2640 base: Use large unix socket send and receive buffers when tracing
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2640] base: Use large unix socket send and receive buffers when tracing** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 10:43 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody When tracing is enabled, consider increasing the size of the unix socket send buffer in tracelog, and the size of the receive buffer in the internal log server. This would allow tracelog to handle larger bursts of trace messages without blocking or dropping trace messages. --- 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
[tickets] [opensaf:tickets] #2641 base: Deallocate TraceLog instance when trace is turned off
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2641] base: Deallocate TraceLog instance when trace is turned off** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 10:45 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Consider deallocating the TraceLog instance when trace is turned off (using SIGUSR2), to save resources and return the service to the same state as before trace was enabled. --- 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
[tickets] [opensaf:tickets] #2642 dtm: Close unused log streams
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2642] dtm: Close unused log streams** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 10:46 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Consider closing and freeing resources for log streams (except mds.log) that have not been used for a while (probably because trace was disabled using SIGUSR2). --- 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
[tickets] [opensaf:tickets] #2639 base: Use common code for MDS log and tracelog
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2639] base: Use common code for MDS log and tracelog** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 19, 2017 10:40 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The MDS log and the tracelog should be consolidated to use common code, since much of the code is the same in both implementations. --- 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
[tickets] [opensaf:tickets] #2618 clm: Verify full-mesh connectivity
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2618] clm: Verify full-mesh connectivity** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:45 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody With the introduction of DTM unicast support in ticket [#991], there is an increased risk that we form a cluster where not alll pairs of nodes are able to communicate with each other. To protect against this, CLM could verify connectivity with all existing member nodes before allowing a new node to join the cluster. --- 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
[tickets] [opensaf:tickets] #2621 AMF: Start SU failover earlier in node shutting down phase
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2621] AMF: Start SU failover earlier in node shutting down phase** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon Oct 09, 2017 03:55 AM UTC by Minh Hon Chau **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody In node shutting down phase, AMF director currently waits for a node being fully down (via MDSNCS_DOWN) before AMF director initiates the failover assignment to SUs on the other nodes. If there are many applications installed on a node, one of them takes significant time in assignment removal, or being unresponsive to csi_remove callback with a long timeout callback setting, that is currently causing a big delay of failover to other SUs who have finished their assignment removal. This ticket adds a support which AMF can initiate an earlier failover right after the SU completes the assignment removal in shutting down node. --- 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
[tickets] [opensaf:tickets] #2617 dtm: Make it possible to run the DTM service also when using TIPC
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2617] dtm: Make it possible to run the DTM service also when using TIPC** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:43 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Make it possible to start the DTM service even when OpenSAF has been configured to use TIPC communication. This can be useful for setting up broadcastless TIPC communication using the mechanism described in ticket [#2616]. --- 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
[tickets] [opensaf:tickets] #2615 dtm: Re-factor dtm IPv4 vs IPv6 vs IPv6 link local handling
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2615] dtm: Re-factor dtm IPv4 vs IPv6 vs IPv6 link local handling** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:22 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody DTM treats IPv4, IPv6 and IPv6 link-local addresses as separate cases, and has different code patch to handle each case. In addition, there seems to be an excess of translations between IP addresses in text format and binary format. All of this should be cleaned 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2614 dtm: Remove the IP address of a node that has been scaled in
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2614] dtm: Remove the IP address of a node that has been scaled in ** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:11 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The IP address of a node that has been scaled in should be removed from the list of DTM peer node IP addresses. This can be done by detecting that the CLM node is removed from the IMM database during scale-in. --- 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
[tickets] [opensaf:tickets] #2616 dtm: Add a user-configurable script for (un)configuring IP addresses
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2616] dtm: Add a user-configurable script for (un)configuring IP addresses** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:41 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Add a user-configurable script that will be called when an IP address is added or removed from the list of DTM peer IP addresses. DTM will not try to communicate with the node before this script returns successfully. The use cases include opening and closing firewalls, and setting up broadcastless TIPC communication with the node. --- 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
[tickets] [opensaf:tickets] #2613 dtm: Protect against inter-cluster communication
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2613] dtm: Protect against inter-cluster communication** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:07 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody With the unicast support, there is a possibility that nodes belonging to two separate clusters will connect with each other. We can add protection against this by including the DNS domain name in the node discovery message, and reply with a NACK to the sender if the domain names do not match. When the sender receives the NACK message, it will remove that IP address from its list of peers. --- 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
[tickets] [opensaf:tickets] #2608 dtm: Add a configuration file for osaftransportd
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2608] dtm: Add a configuration file for osaftransportd** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:39 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody osaftransport currently doesn't have any configuration file in /etc/opensaf/. We should add one. --- 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
[tickets] [opensaf:tickets] #2610 dtm: Propagate peer IP addresses dynamically
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2610] dtm: Propagate peer IP addresses dynamically** **Status:** assigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:53 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell When using unicast, the initial list of IP addresses may be become out of date when new peers are added. We can dynamically update the list of peer IP addresses using several mechanisms. The newly detected addresses should at least be stored in RAM inside osafdtmd, but can possibly also be written down to disk on persistent storage so that they are remembered after a restart of OpenSAF or even after a complete node reboot. The mechanism to detect new addresses include: * Look at the source IP address of incoming TCP connections and check if it is a known or unknown (new) source * Use some form of protocol (e.g. a gossip protocol) to exchange peer IP addresses between nodes that are connected with each other. We probably also need some mechanism to purge the list of peers, when an auto-detected IP has not been in used for a period of time. --- 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
[tickets] [opensaf:tickets] #2609 dtm: Handle unicast sender congestion
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2609] dtm: Handle unicast sender congestion** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:44 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody When using unicast instead of broadcast or multicast, we have the possibility to get congestion when sending the unicast messages to all peer nodes, resulting in success for some nodes and failure for other nodes. We should keep track of which nodes that have failed, and use e.g. EPOLLOUT to get notified when sending is possible 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2861 osaf: Faulty constructs in opensaf detected when compiling with gcc 8.1
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2861] osaf: Faulty constructs in opensaf detected when compiling with gcc 8.1** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Mon May 21, 2018 02:25 PM UTC by Hans Nordebäck **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Compiling with gcc 8.1 with -Wno-format-truncation -Wno-stringop-overflow -Wno-format-overflow makes the compilation succeed, but these -Wno- should not be used, the faulty constructs should instead be corrected. --- 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
[tickets] [opensaf:tickets] #2856 imm: create test cases to verify the ticket 2422
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2856] imm: create test cases to verify the ticket 2422** **Status:** assigned **Milestone:** 5.18.12 **Created:** Thu May 17, 2018 06:29 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Vu Minh Nguyen Create test cases for the ticket [#2422]. --- 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
[tickets] [opensaf:tickets] #2855 mds: Improve tipc receive logic
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2855] mds: Improve tipc receive logic** **Status:** accepted **Milestone:** 5.18.12 **Created:** Wed May 16, 2018 12:29 PM UTC by Hans Nordebäck **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Minh Hon Chau The tipc receive buffer is 2MB, should not be extended as that will affect e.g. available kernel memory. The receive thread normally runs as a realtime thread, RR and with the gl_mds_library_mutex taken in contention with other MDS, time sharing threads. In several cases TIPC_OVERLOAD has happened as consuming messages are not fast enough and TIPC drops these message at receive buffer full. This ticket will change the receive thread from a realtime thread to the standard round-robin time-sharing policy and a new realtime thread will be created to only receive messages and adding these to a larger buffer using a lock-free algorithm. The old receive thread will run as the standard time sharing thread and will consume messages from this shared buffer. The recvmsg in recvfrom_connectionless will be changed to read from the shared buffer. --- 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
[tickets] [opensaf:tickets] #2808 osaf: remove consensus lock on graceful shutdown
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2808] osaf: remove consensus lock on graceful shutdown** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Mar 14, 2018 09:04 AM UTC by Gary Lee **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The lock used in split-brain prevention is only removed by the new active controller, or during an SI swap. We should also look at removing it at graceful shutdown of an active controller. --- 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
[tickets] [opensaf:tickets] #2778 pyosaf: add more attrDefaultValue into get_class_description()
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2778] pyosaf: add more attrDefaultValue into get_class_description()** **Status:** unassigned **Milestone:** future **Created:** Fri Feb 02, 2018 03:42 AM UTC by Hieu Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody When use get_class_description() to get definitions of class attributes, alway got attrDefaultValue=None. So we need to add attribute default value to attributes returned list. --- 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
[tickets] [opensaf:tickets] #2768 nid: Use host name when node_name is missing or empty
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2768] nid: Use host name when node_name is missing or empty** **Status:** assigned **Milestone:** 5.18.12 **Created:** Mon Jan 22, 2018 01:00 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** Anders Widell In the case /etc/opensaf/node_name is missing or empty, we can use the hostname of the machine we are running on. This would reduce the amount of needed per-node configuration if hostname and node_name are the same. Also, make /etc/opensaf/node_name empty as default when installing OpenSAF. --- 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
[tickets] [opensaf:tickets] #2790 pyosaf: Add saImmOmCcbObjectRead API function
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2790] pyosaf: Add saImmOmCcbObjectRead API function** **Status:** unassigned **Milestone:** future **Created:** Tue Feb 27, 2018 08:28 AM UTC by Danh Vo **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody The API function saImmOmCcbObjectRead has not existed in saImmOm.py so we need to add it. --- 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
[tickets] [opensaf:tickets] #2739 dtm: Update osaflog.cc to combine a selected number of different logs, (mds, syslog, trace) and merge them into one html file.
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2739] dtm: Update osaflog.cc to combine a selected number of different logs, (mds, syslog, trace) and merge them into one html file.** **Status:** unassigned **Milestone:** future **Created:** Mon Dec 18, 2017 10:06 AM UTC by Hans Nordebäck **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Update osaflog.cc to combine a selected number of different logs, (mds, syslog, trace) and merge them into one html file according to the time stamps. Example below: Dec 8 08:57:41 SC-1 local0.notice osafimmd[486]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 0 new epoch:2 Dec 8 08:57:41 SC-1 local0.notice osafimmnd[497]: NO implementer for class 'SaLogStreamConfig' is safLogService => class extent is safe. Dec 8 08:57:41 SC-1 local0.notice osafimmnd[497]: NO Implementer (applier) connected: 2 (@safLogService_appl) <11, 2010f> Dec 8 08:57:41 SC-2 local0.notice opensafd[396]: NO Monitoring of NTFD started 2017-12-08T08:57:41.387746+01:00 SC-1 osaflogd 510 mds.log [meta sequenceId="12"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id = IMMA_OM(26) pwe_id=1 Adest = _node[2]:dest_tipc_id_ref[2340343956] Dec 8 08:57:42 SC-1 local0.notice opensafd[397]: NO Monitoring of LOGD started 2017-12-18T10:50:07.729093+01:00 SC-1 osafamfnd 556 osafamfnd [meta sequenceId="14"] 556:amf/amfnd/main.cc:237 >> avnd_create Dec 8 08:57:42 SC-2 local0.notice osafclmd[524]: Started Dec 8 08:57:42 SC-1 local0.notice osafntfd[522]: Started Dec 8 08:57:42 SC-2 local0.notice opensafd[396]: NO Monitoring of CLMD started ~~~ Dec 8 08:57:41 SC-1 local0.notice osafimmd[486]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 0 new epoch:2 Dec 8 08:57:41 SC-1 local0.notice osafimmnd[497]: NO implementer for class 'SaLogStreamConfig' is safLogService => class extent is safe. Dec 8 08:57:41 SC-1 local0.notice osafimmnd[497]: NO Implementer (applier) connected: 2 (@safLogService_appl) <11, 2010f> Dec 8 08:57:41 SC-2 local0.notice opensafd[396]: NO Monitoring of NTFD started 2017-12-08T08:57:41.387746+01:00 SC-1 osaflogd 510 mds.log [meta sequenceId="12"] MDTM: svc up event for svc_id = IMMND(25), subscri. by svc_id = IMMA_OM(26) pwe_id=1 Adest = _node[2]:dest_tipc_id_ref[2340343956] Dec 8 08:57:42 SC-1 local0.notice opensafd[397]: NO Monitoring of LOGD started 2017-12-18T10:50:07.729093+01:00 SC-1 osafamfnd 556 osafamfnd [meta sequenceId="14"] 556:amf/amfnd/main.cc:237 >> avnd_create Dec 8 08:57:42 SC-2 local0.notice osafclmd[524]: Started Dec 8 08:57:42 SC-1 local0.notice osafntfd[522]: Started Dec 8 08:57:42 SC-2 local0.notice opensafd[396]: NO Monitoring of CLMD started ~~~ --- 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
[tickets] [opensaf:tickets] #2725 fm: log Hexadecimal number for node id instead of Decimal
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2725] fm: log Hexadecimal number for node id instead of Decimal** **Status:** unassigned **Milestone:** future **Created:** Mon Dec 04, 2017 10:43 AM UTC by Vu Minh Nguyen **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Here is the syslog: > osaffmd[1861]: Rebooting OpenSAF **NodeId = 132111** EE Name = , Reason: > Received Node Down for Active peer, **OwnNodeId = 132623**, SupervisionTime = > 60 In AMF, IMM or CLM service, they use hex output format for node ID. So, it could be better to output `2040f` or `2060f` instead of `132111` or `132623` to keep nodeid format logged consistency and easier for tracing/debugging. --- 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
[tickets] [opensaf:tickets] #2736 dtm: Add option to osaflog for specifying log directory
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2736] dtm: Add option to osaflog for specifying log directory** **Status:** unassigned **Milestone:** future **Created:** Mon Dec 11, 2017 02:02 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Add an option --logdir that makes it possible to specify the directory where the command shall search for log files. This makes it possible to use the command offline. Since the option is supposed to be used offline, the --flush option shall not be impled when using the --logdir option. Also, add a --help option for printing command help. --- 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
[tickets] [opensaf:tickets] #2720 base: Add LogMessage parsing support
- **Milestone**: 5.18.09 --> future --- ** [tickets:#2720] base: Add LogMessage parsing support** **Status:** unassigned **Milestone:** future **Created:** Fri Dec 01, 2017 01:57 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody Add support in LogMessage for parsing a formatted text string to retrieve the fields of the message. This can be useful in the osaflog command. --- 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
