[tickets] [opensaf:tickets] #2762 smf: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class
- **summary**: imm: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class --> smf: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class --- ** [tickets:#2762] smf: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class ** **Status:** review **Milestone:** 5.18.01 **Created:** Wed Jan 17, 2018 06:17 AM UTC by Ravi Sekhar Reddy **Last Updated:** Fri Jan 19, 2018 09:08 AM UTC **Owner:** Srinivas Siva Mangipudy imm.xml generated using utilities immxml-configure is appeinding string "OpenSafSmfConfig" after flag attribute smfNodeRebootCmd SA_STRING_T SA_CONFIG SA_WRITABLEOpenSafSmfConfig<= --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2762 imm: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class
- **status**: assigned --> review --- ** [tickets:#2762] imm: imm.xml generation appends str OpenSafSmfConfig to flag attr in SafSmfConfig Class ** **Status:** review **Milestone:** 5.18.01 **Created:** Wed Jan 17, 2018 06:17 AM UTC by Ravi Sekhar Reddy **Last Updated:** Thu Jan 18, 2018 06:23 AM UTC **Owner:** Srinivas Siva Mangipudy imm.xml generated using utilities immxml-configure is appeinding string "OpenSafSmfConfig" after flag attribute smfNodeRebootCmd SA_STRING_T SA_CONFIG SA_WRITABLEOpenSafSmfConfig<= --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2359 imm: incorrect error code when more than 10000 objects are set in saImmOmAdminOwnerSet
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#2359] imm: incorrect error code when more than 1 objects are set in saImmOmAdminOwnerSet** **Status:** assigned **Milestone:** future **Created:** Thu Mar 09, 2017 01:34 PM UTC by Zoran Milinkovic **Last Updated:** Thu Mar 09, 2017 02:41 PM UTC **Owner:** Srinivas Siva Mangipudy When more than 1 objects are stored in saImmOmAdminOwnerSet/Release/Clear, SA_AIS_ERR_LIBRARY is returned. The correct returned error code should be SA_AIS_ERR_NO_RESOURCES. IMM has a limitation of setting 1 objects per admin owner set/release/clear calls. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2711 LOG: Add retry logic for RT object creation call.
There is a ticket in place, intend to create a dedicated thread for handling IMM related requests. Ticket#1531 will handle this. --- ** [tickets:#2711] LOG: Add retry logic for RT object creation call.** **Status:** duplicate **Milestone:** 5.18.01 **Created:** Wed Nov 29, 2017 09:35 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Dec 13, 2017 11:08 AM UTC **Owner:** Srinivas Siva Mangipudy Retry logic is missing while creating RT object from logd. Steps to recreate the issue: 1. Keep only SC-1 up. 2. Trigger to suspend immnd(e.i, use SIGSTOP) in the time log client processing saLogStreamOpen_2() to create runtime stream. 3.. Continue immnd(e.i, SIGCONT) , we will get the error "saImmOiRtObjectCreate_2 returned 5" in syslog. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2711 LOG: Add retry logic for RT object creation call.
- **status**: review --> duplicate --- ** [tickets:#2711] LOG: Add retry logic for RT object creation call.** **Status:** duplicate **Milestone:** 5.18.01 **Created:** Wed Nov 29, 2017 09:35 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Mon Dec 04, 2017 09:35 AM UTC **Owner:** Srinivas Siva Mangipudy Retry logic is missing while creating RT object from logd. Steps to recreate the issue: 1. Keep only SC-1 up. 2. Trigger to suspend immnd(e.i, use SIGSTOP) in the time log client processing saLogStreamOpen_2() to create runtime stream. 3.. Continue immnd(e.i, SIGCONT) , we will get the error "saImmOiRtObjectCreate_2 returned 5" in syslog. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #682 LOG: New Active reboots when coordinator IMMND is killed in the middle of switchover
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#682] LOG: New Active reboots when coordinator IMMND is killed in the middle of switchover** **Status:** assigned **Milestone:** future **Created:** Fri Dec 20, 2013 05:27 AM UTC by Sirisha Alla **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Srinivas Siva Mangipudy **Attachments:** - [logs.tar.bz2](https://sourceforge.net/p/opensaf/tickets/682/attachment/logs.tar.bz2) (4.3 MB; application/x-bzip) - [tic682.tgz](https://sourceforge.net/p/opensaf/tickets/682/attachment/tic682.tgz) (208.3 kB; application/x-compressed-tar) The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE enabled loaded with 25k objects. SC-2(SLES-64BIT-SLOT2) is Active and IMMND coordinator is hosted on SC-1(SLES-64BIT-SLOT1). Controller Switchover is initiated and immnd is killed on SC-1. SC-1 went for reboot because of the csi set callback timeout of logd. /var/log/messages of SC-1 and SC-2 corresponding to the above mentioned steps : SC-2: Dec 19 17:21:36 SLES-64BIT-SLOT2 osafamfd[3609]: NO safSi=SC-2N,safApp=OpenSAF Swap initiated Dec 19 17:21:36 SLES-64BIT-SLOT2 osafamfnd[3619]: NO Assigning 'safSi=SC-2N,safApp=OpenSAF' QUIESCED to 'safSu=SC-2,safSg=2N,safApp=OpenSAF' Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 18 <320, 2020f> (safMsgGrpService) Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 'SaSmfCampaign' is released => class extent is UNSAFE Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 22 <319, 2020f> (safEvtService) Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 23 <3, 2020f> (safLogService) Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 'OpenSafSmfConfig' is released => class extent is UNSAFE Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO implementer for class 'SaSmfSwBundle' is released => class extent is UNSAFE Dec 19 17:21:36 SLES-64BIT-SLOT2 osafimmnd[3554]: NO Implementer disconnected 24 <298, 2020f> (safSmfService) Dec 19 17:21:37 SLES-64BIT-SLOT2 osafimmnd[3554]: NO IDec 19 17:21:38 SC-1: SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 18 <0, 2020f> (safMsgGrpService) Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 'SaSmfCampaign' is released => class extent is UNSAFE Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 22 <0, 2020f> (safEvtService) Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 23 <0, 2020f> (safLogService) Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 'OpenSafSmfConfig' is released => class extent is UNSAFE Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO implementer for class 'SaSmfSwBundle' is released => class extent is UNSAFE Dec 19 17:21:38 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 24 <0, 2020f> (safSmfService) Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 20 <0, 2020f> (safLckService) Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 19 <0, 2020f> (safCheckPointService) Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmnd[3498]: NO Implementer disconnected 21 <0, 2020f> (safClmService) Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting Dec 19 17:21:39 SLES-64BIT-SLOT1 osafamfnd[3578]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' Dec 19 17:21:39 SLES-64BIT-SLOT1 osafntfimcnd[3829]: ER saImmOiDispatch() Fail SA_AIS_ERR_BAD_HANDLE (9) Dec 19 17:21:39 SLES-64BIT-SLOT1 osafamfd[3565]: NO Re-initializing with IMM Dec 19 17:21:39 SLES-64BIT-SLOT1 osafimmd[3488]: NO IMMND coord at 2020f mplementer disconnected 20 <303, 2020f> (safLckService) .. Dec 19 17:21:49 SLES-64BIT-SLOT1 osafimmnd[3953]: NO Implementer connected: 40 (OpenSafImmPBE) <0, 2020f> Dec 19 17:21:49 SLES-64BIT-SLOT1 osafamfd[3565]: NO Finished re-initializing with IMM Dec 19 17:21:50 SLES-64BIT-SLOT1 osafimmnd[3953]: NO PBE-OI established on other SC. Dumping incrementally to file imm.db Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: NO 'safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'csiSetcallbackTimeout' : Recovery is 'nodeFailfast' Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: ER safComp=LOG,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:csiSetcallbackTimeout Recovery is:nodeFailfast Dec 19 17:23:40 SLES-64BIT-SLOT1 osafamfnd[3578]: Rebooting OpenSAF NodeId = 131343 EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 131343, SupervisionTime = 60 Dec 19 17:23:40 SLES-64BIT-SLOT1 opensaf_reboot: Rebooting local node;
[tickets] [opensaf:tickets] #2659 log: saflogger possible use of invalid pointer
- **status**: review --> invalid - **Comment**: Since there is no invalid pointer, closing this issue. --- ** [tickets:#2659] log: saflogger possible use of invalid pointer** **Status:** invalid **Milestone:** 5.18.01 **Created:** Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind **Last Updated:** Mon Dec 11, 2017 04:01 AM UTC **Owner:** Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] Re: #2659 log: saflogger possible use of invalid pointer
Hi Canh, Thank you. I will close the issue as invalid. Best Regards Srinivas From: Canh Truong via Opensaf-tickets [mailto:opensaf-tickets@lists.sourceforge.net] Sent: Monday, December 11, 2017 9:32 AM To: opensaf-tickets@lists.sourceforge.net Cc: Canh TruongSubject: [tickets] [opensaf:tickets] #2659 log: saflogger possible use of invalid pointer Hi The maxinum charaters of file name in log 255 characters, but maximum characters of stream name is greater than 255 characters. In case, we use stream name with size > 255 characters and file name < 255 characters (with option -f ) is still valid. (Test case logtest 13 5) For the local tmpDNn variable, I think you are right. Should we close this ticket as invalid ? _ HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_opensaf_tickets_2659_=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=gLdujLZJ0eeWXKFNffrP8FGXrah9MbBUEHAiEJvEV_o=x7iNCtHd3W7G8CdtW4LYurokV1Z5EQ1lrnmHao9u0WY="[tickets:#2659] log: saflogger possible use of invalid pointer Status: review Milestone: 5.18.01 Created: Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind Last Updated: Fri Dec 08, 2017 10:51 AM UTC Owner: Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. _ Sent from sourceforge.net because HYPERLINK "mailto:opensaf-tickets@lists.sourceforge.net"opensaf-tickets@lists.sourceforge.net is subscribed to HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_opensaf_tickets_=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=gLdujLZJ0eeWXKFNffrP8FGXrah9MbBUEHAiEJvEV_o=OSMTDLh9SppLP880p-47Z6KNjMKNjW9UEVPk7s2Ngug="https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_opensaf_admin_tickets_options.=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=gLdujLZJ0eeWXKFNffrP8FGXrah9MbBUEHAiEJvEV_o=jYWy8s01ozMqvXpbWakxpwkjMyhB34xmk3gyHRzS4kQ="https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --- ** [tickets:#2659] log: saflogger possible use of invalid pointer** **Status:** review **Milestone:** 5.18.01 **Created:** Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind **Last Updated:** Mon Dec 11, 2017 04:01 AM UTC **Owner:** Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] Re: #2659 log: saflogger possible use of invalid pointer
Hi Canh, The function lgs_is_valid_filelength is being called and it is returning SA_AIS_ERR_INVALID_PARAM when the length of the filename is greater then 255 characters. Though tmpDNn is defined local, we are doing a copy of the values and not the pointer. Hence the pointer will not be invalid. Please let me know if I am missing anything here. Thank you Srinivas From: Canh Truong [mailto:canh...@users.sf.net] Sent: Friday, December 8, 2017 4:21 PM To: [opensaf:tickets] <2...@tickets.opensaf.p.re.sf.net> Subject: [opensaf:tickets] #2659 log: saflogger possible use of invalid pointer Hi Srinivas, 1/ For longDN, file name may be greater 255 characters 2/ variable 'tmpDn' is defined in local and "saAisNameLend(tmpDn, );" make put the local pointer to "logStreamName". So when saflogger use "logStreamName", The pointer that was contained in "logStreamName" may be invalid _ HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_opensaf_tickets_2659_=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=QsKpZBXeQCVqfZYa0ImtdbpodqYBFbwllHpFr3Dxui0=3nPvg2F_gUC1qivzDxEFE_Sx32XdKPiy-EmCqdeR1EA="[tickets:#2659] log: saflogger possible use of invalid pointer Status: review Milestone: 5.18.01 Created: Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind Last Updated: Fri Dec 08, 2017 10:29 AM UTC Owner: Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. _ Sent from sourceforge.net because you indicated interest in HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_opensaf_tickets_2659_=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=QsKpZBXeQCVqfZYa0ImtdbpodqYBFbwllHpFr3Dxui0=3nPvg2F_gUC1qivzDxEFE_Sx32XdKPiy-EmCqdeR1EA="https://sourceforge.net/p/opensaf/tickets/2659/ To unsubscribe from further messages, please visit HYPERLINK "https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_auth_subscriptions_=DwMCAg=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=rU6x356sikQZSi7Ttc2DuiqAgbc0QIeANg72N5AllVc=QsKpZBXeQCVqfZYa0ImtdbpodqYBFbwllHpFr3Dxui0=fRM3BQMYtjU-WnIIN6AUj5eqT79Ft4B3teqYr8jootI="https://sourceforge.net/auth/subscriptions/ --- ** [tickets:#2659] log: saflogger possible use of invalid pointer** **Status:** review **Milestone:** 5.18.01 **Created:** Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind **Last Updated:** Fri Dec 08, 2017 10:51 AM UTC **Owner:** Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2659 log: saflogger possible use of invalid pointer
- **status**: assigned --> review - **Comment**: The max file size allowed in 255 characters, so when the log file names reaches size greater then 255 characters, error will be returned, which is expected. I didnot see any use of invalid pointer. Please let us know if there are specific use case or requirement for this? --- ** [tickets:#2659] log: saflogger possible use of invalid pointer** **Status:** review **Milestone:** 5.18.01 **Created:** Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind **Last Updated:** Wed Dec 06, 2017 09:20 AM UTC **Owner:** Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2312 logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2
- **status**: assigned --> invalid - **Comment**: Unable to recreate the issue, hence closing it. --- ** [tickets:#2312] logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2 ** **Status:** invalid **Milestone:** future **Created:** Fri Feb 17, 2017 06:41 AM UTC by A V Mahesh (AVM) **Last Updated:** Tue Sep 26, 2017 11:33 AM UTC **Owner:** Srinivas Siva Mangipudy configure diffrent name for Systmen controlers (/usr/share/opensaf/immxml/nodes.cfg ) and created imm.xml and run logtest = /usr/share/opensaf/immxml # cat /usr/share/opensaf/immxml/nodes.cfg SC fm1 SC-1 SC fm2 PL-1 PL PL-3 PL-3 PL PL-4 PL-4 SC-1:~ # /usr/bin/logtest 4 Suite 4: LOG OI tests, stream objects 1 PASSED CCB Object Modify saLogStreamFileName; 2 PASSED CCB Object Modify saLogStreamPathName, ERR not allowed; 3 PASSED CCB Object Modify saLogStreamMaxLogFileSize; . 20 PASSED Log Service Administration API, change sev filter, ERR invalid param name; 21 PASSED Log Service Administration API, no change in sev filter, ERR NO OP; 22 PASSED Log Service Administration API, invalid opId; Segmentation fault SC-1:~ # / 14 PASSED CCB Object Modify saLogStreamSeverityFilter; Detaching after fork from child process 22461. 15 PASSED saImmOiRtAttrUpdateCallback; Detaching after fork from child process 22465. 16 PASSED Log Service Administration API, change sev filter for app stream OK; Detaching after fork from child process 22469. 17 PASSED Log Service Administration API, change sev filter, ERR invalid stream; Detaching after fork from child process 22473. 18 PASSED Log Service Administration API, change sev filter, ERR invalid arg type; Detaching after fork from child process 22477. 19 PASSED Log Service Administration API, change sev filter, ERR invalid severity; Detaching after fork from child process 22481. 20 PASSED Log Service Administration API, change sev filter, ERR invalid param name; Detaching after fork from child process 22485. Detaching after fork from child process 22489. 21 PASSED Log Service Administration API, no change in sev filter, ERR NO OP; Detaching after fork from child process 22493. 22 PASSED Log Service Administration API, invalid opId; Program received signal SIGSEGV, Segmentation fault. 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 312 src/log/apitest/logtest.c: No such file or directory. in src/log/apitest/logtest.c (gdb) bt /#0 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 /#1 0x55562ddc in saLogOi_116 () at src/log/apitest/tet_LogOiOps.c:582 /#2 0x55570855 in run_test_case () /#3 0x55570cf4 in test_run () /#4 0xbcad in main () at src/log/apitest/logtest.c:569 (gdb) dir /avm/staging-publish/ Source directories searched: /avm/staging-publish:$cdir:$cwd (gdb) bt /#0 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 /#1 0x55562ddc in saLogOi_116 () at src/log/apitest/tet_LogOiOps.c:582 /#2 0x55570855 in run_test_case () /#3 0x55570cf4 in test_run () /#4 0xbcad in main () at src/log/apitest/logtest.c:569 (gdb) src/log/apitest # grep -r "SC-" * logtest.c: * @return 1 SC-1, 2 SC-2 logtest.c: SaConstStringT objname = "safSu=SC-1,safSg=2N,safApp=OpenSAF"; logtest.c: /* Checking SC-1 */ logtestfr.c: * @return 1 SC-1, 2 SC-2 logtestfr.c:SaNameT objectName1 = { /* Read object for SC-1 */ logtestfr.c:.value = "safSu=SC-1,safSg=2N,safApp=OpenSAF", logtestfr.c:.length = strlen("safSu=SC-1,safSg=2N,safApp=OpenSAF") + 1 logtestfr.c:/* Checking SC-1 */ --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2659 log: saflogger possible use of invalid pointer
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy --- ** [tickets:#2659] log: saflogger possible use of invalid pointer** **Status:** assigned **Milestone:** 5.18.01 **Created:** Sun Oct 29, 2017 01:04 PM UTC by Johnny Lind **Last Updated:** Fri Nov 03, 2017 09:50 PM UTC **Owner:** Srinivas Siva Mangipudy In case the option -a is given to saflogger with a application name longer than 256 characters and extended names are used, saAisNameLend takes a local stack allocated char array "tmpDn" as argument and will store a pointer to the local variable in the SaNameT argument making the SaNameT having invalid pointer after the scope ends as tmpDn will be freed. The SaNameT variable is then later used to open a log stream. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2711 LOG: Add retry logic for RT object creation call.
- **status**: assigned --> review --- ** [tickets:#2711] LOG: Add retry logic for RT object creation call.** **Status:** review **Milestone:** 5.18.01 **Created:** Wed Nov 29, 2017 09:35 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Nov 29, 2017 09:35 AM UTC **Owner:** Srinivas Siva Mangipudy Retry logic is missing while creating RT object from logd. Steps to recreate the issue: 1. Keep only SC-1 up. 2. Trigger to suspend immnd(e.i, use SIGSTOP) in the time log client processing saLogStreamOpen_2() to create runtime stream. 3.. Continue immnd(e.i, SIGCONT) , we will get the error "saImmOiRtObjectCreate_2 returned 5" in syslog. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2711 LOG: Add retry logic for RT object creation call.
--- ** [tickets:#2711] LOG: Add retry logic for RT object creation call.** **Status:** assigned **Milestone:** 5.18.01 **Created:** Wed Nov 29, 2017 09:35 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Nov 29, 2017 09:35 AM UTC **Owner:** Srinivas Siva Mangipudy Retry logic is missing while creating RT object from logd. Steps to recreate the issue: 1. Keep only SC-1 up. 2. Trigger to suspend immnd(e.i, use SIGSTOP) in the time log client processing saLogStreamOpen_2() to create runtime stream. 3.. Continue immnd(e.i, SIGCONT) , we will get the error "saImmOiRtObjectCreate_2 returned 5" in syslog. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2439 log : make log dir Cppcheck warning free
- **status**: assigned --> review --- ** [tickets:#2439] log : make log dir Cppcheck warning free** **Status:** review **Milestone:** future **Created:** Thu Apr 27, 2017 06:36 AM UTC by A V Mahesh (AVM) **Last Updated:** Tue Oct 10, 2017 06:48 AM UTC **Owner:** Srinivas Siva Mangipudy [log/agent/lga_state.c:94]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/agent/lga_state.c:183]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtest.c:106] -> [log/apitest/logtest.c:118]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:144] -> [log/apitest/logtest.c:154]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:406] -> [log/apitest/logtest.c:409]: (style) Variable 'value' is reassigned a value before the old one has been used. [log/apitest/logtest.c:110]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtest.c:473]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtest.c:493]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtestfr.c:189] -> [log/apitest/logtestfr.c:200]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtestfr.c:193]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtestfr.c:750]: (style) The scope of the variable 'opt_val' can be reduced. [log/apitest/logtestfr.c:252]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:292]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:371]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:671]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:75]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:91]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:109]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:130]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:149]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:166]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:185]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:190]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 2) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:309]: (style) The scope of the variable 'sz' can be reduced. [log/apitest/saflogtest.c:359]: (style) The scope of the variable 'c' can be reduced. [log/apitest/saflogtest.c:219]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:593]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/tet_LogOiOps.c:1487]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:1493]: (warning) %d in format string (no. 1) requires 'int' but the argument type is 'unsigned int'. [log/apitest/tet_LogOiOps.c:4254]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4365]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4494]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4604]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:555] ->
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
commit 310ac5cdf625681c692ab2621d08c42dab80be0e Author: vijayroyDate: Tue Nov 14 12:07:54 2017 +0530 ntfd: fix to avoid ntfimcnd from dumping core dump during massive add/delete ops [#2647] --- ** [tickets:#2647] ntfd: ntfimcnd crashed on handling for Object creation callback** **Status:** fixed **Milestone:** 5.18.01 **Created:** Thu Oct 19, 2017 12:45 PM UTC by Srinivas Siva Mangipudy **Last Updated:** Tue Nov 14, 2017 06:57 AM UTC **Owner:** Srinivas Siva Mangipudy 1. Problem = = NTFimcnd crashed while 200k objects was created and the deleted in IMM, the classes associated with these objects were also removed. 2. Analysis = = A huge number of objects, about 200k objects, were created in IMM with PBE disabled. Then these objects were deleted in one CCB (by deleting the root object). After deleting the objects, the classes were also removed. Then the crash happened. ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. When NTFimcnd created notifications, some information had to be looked up in IMM. NTFimcnd only asked for class information in case of object creation: static SaAisErrorT saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId, const SaImmClassNameT className, const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … dn_ptr = get_created_dn(className, parentName, attr); … } static void saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) { … switch (ccbUtilOperationData->operationType) { case CCBUTIL_CREATE: rdn_attr_name = get_rdn_attr_name( ccbUtilOperationData- >param.create.className); internal_rc = ntfimcn_send_object_create_notification( ccbUtilOperationData, rdn_attr_name, ccbLast); … } In this case, NTF was still handling notifications for a big number of created objects. Usually, NTFimcnd cached the class information. But because these objects belong to many classes, it had to ask IMM for class information. But the class was already removed in IMM. IMM was much faster to create and delete the objects and class (with PBE disabled), while NTF was still processing the objects, so the information was not there in IMM anymore, and the crashed happened. 3. Reproduction = = Can be reproduced like below: - Disable PBE 1. Create a huge amount of objects with one parent object. 2. In my case, I created 2 root objects of two different classes with about 100k child objects each Delete first root object, then delete the class associated with this object. 3. Delete second root object, delete the class associated with this object. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
- **status**: assigned --> fixed --- ** [tickets:#2647] ntfd: ntfimcnd crashed on handling for Object creation callback** **Status:** fixed **Milestone:** 5.18.01 **Created:** Thu Oct 19, 2017 12:45 PM UTC by Srinivas Siva Mangipudy **Last Updated:** Mon Nov 06, 2017 09:07 AM UTC **Owner:** Srinivas Siva Mangipudy 1. Problem = = NTFimcnd crashed while 200k objects was created and the deleted in IMM, the classes associated with these objects were also removed. 2. Analysis = = A huge number of objects, about 200k objects, were created in IMM with PBE disabled. Then these objects were deleted in one CCB (by deleting the root object). After deleting the objects, the classes were also removed. Then the crash happened. ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. When NTFimcnd created notifications, some information had to be looked up in IMM. NTFimcnd only asked for class information in case of object creation: static SaAisErrorT saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId, const SaImmClassNameT className, const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … dn_ptr = get_created_dn(className, parentName, attr); … } static void saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) { … switch (ccbUtilOperationData->operationType) { case CCBUTIL_CREATE: rdn_attr_name = get_rdn_attr_name( ccbUtilOperationData- >param.create.className); internal_rc = ntfimcn_send_object_create_notification( ccbUtilOperationData, rdn_attr_name, ccbLast); … } In this case, NTF was still handling notifications for a big number of created objects. Usually, NTFimcnd cached the class information. But because these objects belong to many classes, it had to ask IMM for class information. But the class was already removed in IMM. IMM was much faster to create and delete the objects and class (with PBE disabled), while NTF was still processing the objects, so the information was not there in IMM anymore, and the crashed happened. 3. Reproduction = = Can be reproduced like below: - Disable PBE 1. Create a huge amount of objects with one parent object. 2. In my case, I created 2 root objects of two different classes with about 100k child objects each Delete first root object, then delete the class associated with this object. 3. Delete second root object, delete the class associated with this object. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
Hi Srinivas If something that prevents ntfimcn to send notifications happen ntfimcn shall be restarted so that a possible missed notification message is sent. If this may happen in “normal” situations ntfimcn shall just exit without any coredump. Possibly a notification (LOG_NO) should be written to the syslog. If the problem is “not normal”, something that should never happen (an error that must be analyzed and maybe fixed) an abort is better since it gives us a back-trace of what has happened. Before any abort is done an error message shall be written to syslog (LOG_ER). This error message should contain information about what has happened and where it has happened (__FUNCTION__, __LINE__) in order to have at least some information if a coredump is lost, could not be genereated, no back-trace was created etc. So, the question is, is this something that could happen in a “real” system and is it of any interest to get a core-dump to analyze the problem? In any case ntfimcn will recover. If the answer is that this event triggering the core-dump is not a fail to analyze and that it is something ntfimcn should just gracefully recover from then change to LOG_NO + _Exit. Regards Lennart From: Srinivas Mangipudy [mailto:srinivas.mangip...@oracle.com] Sent: den 2 november 2017 16:42 To: Lennart Lund; Minh Hon Chau Cc: Ravi Sekhar Reddy Konda Subject: RE: OSAF : ntfimcnd core dump issue -- 2647. Hi Lennart, Thanks a lot for the explanation. It was really helpful. Do you think it is better to log the error and then call _exit ( we will have a graceful restart) then calling abort and allowing the process to dump core in this case? Please let me know your thoughts about this. Thanks and best regards Srinivas From: Lennart Lund [mailto:lennart.l...@ericsson.com] Sent: Thursday, November 2, 2017 6:26 PM To: Minh Hon Chau ; Srinivas Mangipudy Cc: Ravi Sekhar Reddy Konda ; Lennart Lund Subject: RE: OSAF : ntfimcnd core dump issue -- 2647. Hi Ntfimcn implements a so called “special applier”. This is an IMM applier that receives IMM callbacks in the same way as an object implementer or an ordinary applier. The difference is that a special applier is not requesting to become applier for any special objects or classes. Instead a configuration attribute in an object can be given a flag, ATTR_NOTIFY. The general error handling in ntfimcn is to exit. This will be detected by the osafntfd process that then restarts osfafntfimcnd. To notify that this has happened (ntfimcn may have “missed” some IMM modifications while it was down) ntfimcn always sends a special notification (may have lost notifications notification) when it is started. This notification is used by com-sa to request com to do a (re)synchronization. The “normal” way for ntfimcn to exit is by calling _Exit. When something happens that should never happen abort() is used instead (a coredump will be created). If something not normal and really bad is done in the system an abort is motivated. This means that ntfimcn shall not be made to “defensively” avoid to abort (coredump) if the cluster system and IMM is abused. Instead if we want to test something like this it shall be accepted that a coredump is created, this is not a Fail! However if something like that ntfimcn is not restarted or that no “may have lost notification notification” is sent it is to be considered as a Fail. Note: If ntfimcn exist (or abort) the node or ntf as such is not affected. It is only the ntfimcn process that is restarted. Ticket #2647 should probably not be fixed instead it should be set to invalid. /Lennart From: Minh Hon Chau [mailto:minh.c...@dektech.com.au] Sent: den 2 november 2017 05:45 To: Srinivas Mangipudy Cc: Ravi Sekhar Reddy Konda ; Lennart Lund Subject: Re: OSAF : ntfimcnd core dump issue -- 2647. Hi Srinivas, + Lennart. If I understand correctly, the test creates a huge amount of objects (are they RT or Config?), and while the callbacks are coming, the test deletes the class. The latter callbacks can't find class name so it aborts. I think we can defensively avoid coredump and not sending notification as your suggestion, but I'm wondering the integrity from IMM, as IMM user receives a callback but the associated class is not existed. Thanks, Minh On 01/11/17 22:04, Srinivas Mangipudy wrote: Hi Minh, This is regarding Notification issue https://sourceforge.net/p/opensaf/tickets/2647/. This issue is occurring since IMM deleted the objects and ntfimcnd was not able to fetch the object, so it returned back “SA_AIS_ERR_NOT_EXIST” error. Since “SA_AIS_ERR_NOT_EXIST” was returned, ntfimcnd aborted, leading to core dump. I have
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
- Description has changed: Diff: --- old +++ new @@ -3,7 +3,7 @@ 2. Analysis = = A huge number of objects, about 200k objects, were created in IMM with PBE disabled. Then these objects were deleted in one CCB (by deleting the root object). After deleting the objects, the classes were also removed. Then the crash happened. -Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:10 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:20 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED (immcfg_SC-2- 1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 15 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 20 Oct 19 19:47:25 SC-2-1 osafimmnd[22799]: NO Ccb 218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. + ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. When NTFimcnd created notifications, some information had to be looked up in IMM. NTFimcnd only asked for class information in case of object creation: @@ -13,9 +13,6 @@ In this case, NTF was still handling notifications for a big number of created objects. Usually, NTFimcnd cached the class information. But because these objects belong to many classes, it had to ask IMM for class information. But the class was already removed in IMM. IMM was much faster to create and delete the objects and class (with PBE disabled), while NTF was still processing the objects, so the information was not there in IMM anymore, and the crashed happened. -Oct 19 19:47:25.344370 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] TR ccb-object-create make the callback Oct 19 19:47:25.344385 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426] >> saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194] >> get_created_dn Oct 19 19:47:25.344392 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105] >> get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066] TR ClassName: TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083] TR ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121] TR Alloc attrdefs array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5327] << saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344619 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5335] >> saImmOmClassDescriptionMemoryFree_2 -Oct 19 19:47:25.344625 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5379] << saImmOmClassDescriptionMemoryFree_2 Oct 19 19:47:25.344628 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0164] << get_rdn_attr_name Oct 19 19:47:25.344633 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0228] << get_created_dn Oct 19 19:47:25.344639 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0473] << saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344643 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2496] TR ccb-object-create callback returned RC:1 Oct 19 19:47:25.344648 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:3171] << imma_process_callback_info Oct 19 19:47:25.344653 osafntfimcnd
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
- Description has changed: Diff: --- old +++ new @@ -1,4 +1,21 @@ -1. Problem = = NTFimcnd crashed while 200k objects was created and the deleted in IMM, the classes associated with these objects were also removed. 2. Analysis = = A huge number of objects, about 200k objects, were created in IMM with PBE disabled. Then these objects were deleted in one CCB (by deleting the root object). After deleting the objects, the classes were also removed. Then the crash happened. Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:10 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:20 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED (immcfg_SC-2- 1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 15 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 20 Oct 19 19:47:25 SC-2-1 osafimmnd[22799]: NO Ccb 218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. When NTFimcnd created notifications, some information had to be looked up in IMM. NTFimcnd only asked for class information in case of object creation: static SaAisErrorT saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId, const SaImmClassNameT className, const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … dn_ptr = get_created_dn(className, parentName, attr); … } static void saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) { … switch (ccbUtilOperationData->operationType) { case CCBUTIL_CREATE: rdn_attr_name = get_rdn_attr_name( ccbUtilOperationData- >param.create.className); -internal_rc = ntfimcn_send_object_create_notification( ccbUtilOperationData, rdn_attr_name, ccbLast); … } In this case, NTF was still handling notifications for a big number of created objects. Usually, NTFimcnd cached the class information. But because these objects belong to many classes, it had to ask IMM for class information. But the class was already removed in IMM. IMM was much faster to create and delete the objects and class (with PBE disabled), while NTF was still processing the objects, so the information was not there in IMM anymore, and the crashed happened. Oct 19 19:47:25.344370 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] TR ccb-object-create make the callback Oct 19 19:47:25.344385 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426] >> saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194] >> get_created_dn Oct 19 19:47:25.344392 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105] >> get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066] TR ClassName: TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083] TR ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121] TR Alloc attrdefs array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5327] << saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344619 osafntfimcnd
[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback
--- ** [tickets:#2647] ntfd: ntfimcnd crashed on handling for Object creation callback** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Thu Oct 19, 2017 12:45 PM UTC by Srinivas Siva Mangipudy **Last Updated:** Thu Oct 19, 2017 12:45 PM UTC **Owner:** nobody 1. Problem = = NTFimcnd crashed while 200k objects was created and the deleted in IMM, the classes associated with these objects were also removed. 2. Analysis = = A huge number of objects, about 200k objects, were created in IMM with PBE disabled. Then these objects were deleted in one CCB (by deleting the root object). After deleting the objects, the classes were also removed. Then the crash happened. Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:10 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:20 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED (immcfg_SC-2- 1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 15 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner release 20 Oct 19 19:47:25 SC-2-1 osafimmnd[22799]: NO Ccb 218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]: ../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167: get_rdn_attr_name: Assertion '0' failed. When NTFimcnd created notifications, some information had to be looked up in IMM. NTFimcnd only asked for class information in case of object creation: static SaAisErrorT saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId, const SaImmClassNameT className, const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … dn_ptr = get_created_dn(className, parentName, attr); … } static void saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) { … switch (ccbUtilOperationData->operationType) { case CCBUTIL_CREATE: rdn_attr_name = get_rdn_attr_name( ccbUtilOperationData- >param.create.className); internal_rc = ntfimcn_send_object_create_notification( ccbUtilOperationData, rdn_attr_name, ccbLast); … } In this case, NTF was still handling notifications for a big number of created objects. Usually, NTFimcnd cached the class information. But because these objects belong to many classes, it had to ask IMM for class information. But the class was already removed in IMM. IMM was much faster to create and delete the objects and class (with PBE disabled), while NTF was still processing the objects, so the information was not there in IMM anymore, and the crashed happened. Oct 19 19:47:25.344370 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] TR ccb-object-create make the callback Oct 19 19:47:25.344385 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426] >> saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194] >> get_created_dn Oct 19 19:47:25.344392 osafntfimcnd [27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105] >> get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996] >> saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066] TR ClassName: TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083] TR ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd [27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121] TR Alloc attrdefs array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd
[tickets] [opensaf:tickets] #1443 log: service is crashed if creating and deleting conf obj class continuously
- **status**: assigned --> invalid --- ** [tickets:#1443] log: service is crashed if creating and deleting conf obj class continuously** **Status:** invalid **Milestone:** future **Created:** Tue Aug 11, 2015 07:37 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Oct 09, 2017 10:13 AM UTC **Owner:** Srinivas Siva Mangipudy When creating application object class and deleting it continuously, log service could be crashed. To reproduce this case, perform following command. > for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do immcfg -c > SaLogStreamConfig safLgStrCfg=TestLog -a saLogStreamPathName=. -a > saLogStreamFileName=TestLog; echo "create ($i) - $?"; immcfg -d > safLgStrCfg=TestLog; echo "Delete ($i) - $?"; done Output something likes: > create (1) - 0 > Delete (1) - 0 > create (2) - 0 > error - saImmOmCcbObjectDelete for 'safLgStrCfg= TestLog' FAILED: > SA_AIS_ERR_FAILED_OPERATION (21) > error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) > Delete (2) - 1 > error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) > create (3) - 1 > reboot: Restarting system Here is the analysis: 1. When creating obj class is done by IMM, but logsv have not finished the `apply callback` job yet. In this case, it needs to update a run-time attribute ` saLogStreamCreationTimestamp`. This is done in main thread. 2. If deleting this obj class comes before `apply callback` job finishes, IMM will mark that obj class as `IMM_DELETE_LOCK` and call respective callbacks to logsv and *wait for response*, but logsv is busy in doing `apply callback` in (1). When the request `update runtime attribute` to IMM by logsv, IMM will returns TRY_AGAIN. IMM waits for logsv response to release “IMM_DELETE_LOCK”, while logsv still get stuck in `update rt attribute` as getting TRY_AGAIN. Consequently, logsv might be terminated if number of try-again is reached or delete action gets failed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2439 log : make log dir Cppcheck warning free
Will be fixing issues in apitest and tools dir in this ticket, since /agent and /logd dir's are handled in other tickets, mentioned above. --- ** [tickets:#2439] log : make log dir Cppcheck warning free** **Status:** assigned **Milestone:** future **Created:** Thu Apr 27, 2017 06:36 AM UTC by A V Mahesh (AVM) **Last Updated:** Tue Oct 10, 2017 06:46 AM UTC **Owner:** Srinivas Siva Mangipudy [log/agent/lga_state.c:94]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/agent/lga_state.c:183]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtest.c:106] -> [log/apitest/logtest.c:118]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:144] -> [log/apitest/logtest.c:154]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:406] -> [log/apitest/logtest.c:409]: (style) Variable 'value' is reassigned a value before the old one has been used. [log/apitest/logtest.c:110]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtest.c:473]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtest.c:493]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtestfr.c:189] -> [log/apitest/logtestfr.c:200]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtestfr.c:193]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtestfr.c:750]: (style) The scope of the variable 'opt_val' can be reduced. [log/apitest/logtestfr.c:252]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:292]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:371]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:671]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:75]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:91]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:109]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:130]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:149]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:166]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:185]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:190]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 2) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:309]: (style) The scope of the variable 'sz' can be reduced. [log/apitest/saflogtest.c:359]: (style) The scope of the variable 'c' can be reduced. [log/apitest/saflogtest.c:219]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:593]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/tet_LogOiOps.c:1487]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:1493]: (warning) %d in format string (no. 1) requires 'int' but the argument type is 'unsigned int'. [log/apitest/tet_LogOiOps.c:4254]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4365]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4494]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4604]: (warning) %u in format string (no. 1)
[tickets] [opensaf:tickets] #2439 log : make log dir Cppcheck warning free
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy --- ** [tickets:#2439] log : make log dir Cppcheck warning free** **Status:** assigned **Milestone:** future **Created:** Thu Apr 27, 2017 06:36 AM UTC by A V Mahesh (AVM) **Last Updated:** Fri Apr 28, 2017 08:33 AM UTC **Owner:** Srinivas Siva Mangipudy [log/agent/lga_state.c:94]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/agent/lga_state.c:183]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtest.c:106] -> [log/apitest/logtest.c:118]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:144] -> [log/apitest/logtest.c:154]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtest.c:406] -> [log/apitest/logtest.c:409]: (style) Variable 'value' is reassigned a value before the old one has been used. [log/apitest/logtest.c:110]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtest.c:473]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtest.c:493]: (portability) Non reentrant function 'strtok' called. For threadsafe applications it is recommended to use the reentrant replacement function 'strtok_r'. [log/apitest/logtestfr.c:189] -> [log/apitest/logtestfr.c:200]: (style) Variable 'ais_rc' is reassigned a value before the old one has been used. [log/apitest/logtestfr.c:193]: (style) The scope of the variable 'value' can be reduced. [log/apitest/logtestfr.c:750]: (style) The scope of the variable 'opt_val' can be reduced. [log/apitest/logtestfr.c:252]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:292]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:371]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logtestfr.c:671]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:75]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:91]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:109]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:130]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:149]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/logutil.c:166]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:185]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:190]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'int'. [log/apitest/saflogtest.c:225]: (warning) %u in format string (no. 2) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/saflogtest.c:309]: (style) The scope of the variable 'sz' can be reduced. [log/apitest/saflogtest.c:359]: (style) The scope of the variable 'c' can be reduced. [log/apitest/saflogtest.c:219]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/saflogtest.c:593]: (style) Obsolescent function 'usleep' called. It is recommended to use 'nanosleep' or 'setitimer' instead. [log/apitest/tet_LogOiOps.c:1487]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:1493]: (warning) %d in format string (no. 1) requires 'int' but the argument type is 'unsigned int'. [log/apitest/tet_LogOiOps.c:4254]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4365]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4494]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'. [log/apitest/tet_LogOiOps.c:4604]: (warning) %u in format string (no. 1) requires 'unsigned int' but the argument type is 'signed int'.
[tickets] [opensaf:tickets] #1443 log: service is crashed if creating and deleting conf obj class continuously
Executed the below script: for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do immcfg -c SaLogStreamConfig safLgStrCfg=TestLog -a saLogStreamPathName=. -a saLogStreamFileName=TestLog; echo "create ($i) - $?"; immcfg -d safLgStrCfg=TestLog; echo "Delete ($i) - $?"; done done But was not able to recreate the issue. Below is the o/p. ps -ef | grep -i log syslog 698 1 0 02:22 ?00:00:00 /usr/sbin/rsyslogd -n root 768 1 0 02:22 ?00:00:00 /lib/systemd/systemd-logind srinivas 1857 1416 0 02:22 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog root 2428 2382 0 15:39 pts/600:00:00 grep --color=auto -i log root 2509 1 0 02:23 ?00:00:03 /usr/local/lib/opensaf/osafimmd --tracemask=0x --loglevel=info root 2521 1 0 02:23 ?00:00:08 /usr/local/lib/opensaf/osafimmnd --loglevel=info root 2565 1 0 02:23 ?00:00:04 /usr/local/lib/opensaf/osaflogd --tracemask=0x root 2585 1 0 02:23 ?00:00:00 /usr/local/lib/opensaf/osafntfd --loglevel=info root 2823 1 0 02:23 ?00:00:00 /usr/local/lib/opensaf/osafckptd --loglevel=info Delete (1) - 0 create (2) - 0 Delete (2) - 0 create (3) - 0 Delete (3) - 0 create (4) - 0 Delete (4) - 0 create (5) - 0 Delete (5) - 0 create (6) - 0 Delete (6) - 0 create (7) - 0 Delete (7) - 0 create (8) - 0 Delete (8) - 0 create (9) - 0 Delete (9) - 0 create (10) - 0 Delete (10) - 0 create (11) - 0 Delete (11) - 0 create (12) - 0 Delete (12) - 0 create (13) - 0 Delete (13) - 0 create (14) - 0 Delete (14) - 0 create (15) - 0 Delete (15) - 0 create (16) - 0 Delete (16) - 0 create (17) - 0 Delete (17) - 0 create (18) - 0 Delete (18) - 0 create (19) - 0 Delete (19) - 0 create (20) - 0 Delete (20) - 0 : : ps -ef | grep -i log syslog 698 1 0 02:22 ?00:00:00 /usr/sbin/rsyslogd -n root 768 1 0 02:22 ?00:00:00 /lib/systemd/systemd-logind srinivas 1857 1416 0 02:22 ?00:00:00 /usr/bin/pulseaudio --start --log-target=syslog root 2509 1 0 02:23 ?00:00:04 /usr/local/lib/opensaf/osafimmd --tracemask=0x --loglevel=info root 2521 1 0 02:23 ?00:00:09 /usr/local/lib/opensaf/osafimmnd --loglevel=info root 2565 1 0 02:23 ?00:00:06 /usr/local/lib/opensaf/osaflogd --tracemask=0x root 2585 1 0 02:23 ?00:00:00 /usr/local/lib/opensaf/osafntfd --loglevel=info root 2823 1 0 02:23 ?00:00:00 /usr/local/lib/opensaf/osafckptd --loglevel=info root 4931 2382 0 15:40 pts/600:00:00 grep --color=auto -i log --- ** [tickets:#1443] log: service is crashed if creating and deleting conf obj class continuously** **Status:** assigned **Milestone:** future **Created:** Tue Aug 11, 2015 07:37 AM UTC by Vu Minh Nguyen **Last Updated:** Wed Sep 27, 2017 06:51 AM UTC **Owner:** Srinivas Siva Mangipudy When creating application object class and deleting it continuously, log service could be crashed. To reproduce this case, perform following command. > for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do immcfg -c > SaLogStreamConfig safLgStrCfg=TestLog -a saLogStreamPathName=. -a > saLogStreamFileName=TestLog; echo "create ($i) - $?"; immcfg -d > safLgStrCfg=TestLog; echo "Delete ($i) - $?"; done Output something likes: > create (1) - 0 > Delete (1) - 0 > create (2) - 0 > error - saImmOmCcbObjectDelete for 'safLgStrCfg= TestLog' FAILED: > SA_AIS_ERR_FAILED_OPERATION (21) > error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) > Delete (2) - 1 > error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) > create (3) - 1 > reboot: Restarting system Here is the analysis: 1. When creating obj class is done by IMM, but logsv have not finished the `apply callback` job yet. In this case, it needs to update a run-time attribute ` saLogStreamCreationTimestamp`. This is done in main thread. 2. If deleting this obj class comes before `apply callback` job finishes, IMM will mark that obj class as `IMM_DELETE_LOCK` and call respective callbacks to logsv and *wait for response*, but logsv is busy in doing `apply callback` in (1). When the request `update runtime attribute` to IMM by logsv, IMM will returns TRY_AGAIN. IMM waits for logsv response to release “IMM_DELETE_LOCK”, while logsv still get stuck in `update rt attribute` as getting TRY_AGAIN. Consequently, logsv might be terminated if number of try-again is reached or delete action gets failed. --- 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
[tickets] [opensaf:tickets] #2121 log: parsing command logtest with option -e is not correct
- **status**: review --> fixed --- ** [tickets:#2121] log: parsing command logtest with option -e is not correct** **Status:** fixed **Milestone:** future **Created:** Mon Oct 17, 2016 06:56 AM UTC by Canh Truong **Last Updated:** Wed Oct 04, 2017 10:06 AM UTC **Owner:** Srinivas Siva Mangipudy Parsing command logtest with option -e is wrong. For example: Running command logtest -e 14 2 All test cases in test suite 14 will be executed while we just expect that test case 2 of test suite 14 is executed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2121 log: parsing command logtest with option -e is not correct
commit 8c725cd2d873aebd420e1857ece516ba8d0eab5b Author: SrinivasDate: Wed Oct 4 15:35:14 2017 +0530 log: corrected parsing of command logtest with option -e [#2121] Instead of using strtok to parse the input args, reading the args using index. --- ** [tickets:#2121] log: parsing command logtest with option -e is not correct** **Status:** review **Milestone:** future **Created:** Mon Oct 17, 2016 06:56 AM UTC by Canh Truong **Last Updated:** Thu Sep 21, 2017 10:46 AM UTC **Owner:** Srinivas Siva Mangipudy Parsing command logtest with option -e is wrong. For example: Running command logtest -e 14 2 All test cases in test suite 14 will be executed while we just expect that test case 2 of test suite 14 is executed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2039 NTF: Missleading returned code of ntftest when tests are failed
- **status**: review --> fixed --- ** [tickets:#2039] NTF: Missleading returned code of ntftest when tests are failed** **Status:** fixed **Milestone:** 5.17.10 **Created:** Thu Sep 15, 2016 09:11 AM UTC by Minh Hon Chau **Last Updated:** Wed Oct 04, 2017 09:30 AM UTC **Owner:** Srinivas Siva Mangipudy If running a test case of ntftest suite 37 (38, or 39) and it fails, the reported error is always SA_AIS_ERR_FAILED_OPERATION, but the actual failure code is different. The actual error code should be memorized and reported in test result. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2039 NTF: Missleading returned code of ntftest when tests are failed
commit ac1d727d2b70cb41a612c2b9a377fccb355c8b19 Author: SrinivasDate: Wed Oct 4 14:44:57 2017 +0530 ntf: correct return code is returned [#2039] --- ** [tickets:#2039] NTF: Missleading returned code of ntftest when tests are failed** **Status:** review **Milestone:** 5.17.10 **Created:** Thu Sep 15, 2016 09:11 AM UTC by Minh Hon Chau **Last Updated:** Fri Sep 15, 2017 11:13 AM UTC **Owner:** Srinivas Siva Mangipudy If running a test case of ntftest suite 37 (38, or 39) and it fails, the reported error is always SA_AIS_ERR_FAILED_OPERATION, but the actual failure code is different. The actual error code should be memorized and reported in test result. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1443 log: service is crashed if creating and deleting conf obj class continuously
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#1443] log: service is crashed if creating and deleting conf obj class continuously** **Status:** assigned **Milestone:** future **Created:** Tue Aug 11, 2015 07:37 AM UTC by Vu Minh Nguyen **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Srinivas Siva Mangipudy When creating application object class and deleting it continuously, log service could be crashed. To reproduce this case, perform following command. > for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do immcfg -c > SaLogStreamConfig safLgStrCfg=TestLog -a saLogStreamPathName=. -a > saLogStreamFileName=TestLog; echo "create ($i) - $?"; immcfg -d > safLgStrCfg=TestLog; echo "Delete ($i) - $?"; done Output something likes: > create (1) - 0 > Delete (1) - 0 > create (2) - 0 > error - saImmOmCcbObjectDelete for 'safLgStrCfg= TestLog' FAILED: > SA_AIS_ERR_FAILED_OPERATION (21) > error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) > Delete (2) - 1 > error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) > create (3) - 1 > reboot: Restarting system Here is the analysis: 1. When creating obj class is done by IMM, but logsv have not finished the `apply callback` job yet. In this case, it needs to update a run-time attribute ` saLogStreamCreationTimestamp`. This is done in main thread. 2. If deleting this obj class comes before `apply callback` job finishes, IMM will mark that obj class as `IMM_DELETE_LOCK` and call respective callbacks to logsv and *wait for response*, but logsv is busy in doing `apply callback` in (1). When the request `update runtime attribute` to IMM by logsv, IMM will returns TRY_AGAIN. IMM waits for logsv response to release “IMM_DELETE_LOCK”, while logsv still get stuck in `update rt attribute` as getting TRY_AGAIN. Consequently, logsv might be terminated if number of try-again is reached or delete action gets failed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2312 logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2
cat /usr/local/share/opensaf/immxml/nodes.cfg SC fm1 SC-1 SC fm2 PL-1 PL PL-3 PL-3 PL PL-4 PL-4 imm.xml generated. safAmfNodeGroup=AllNodes,safAmfCluster=myAmfCluster saAmfNGNodeList safAmfNode=fm1,safAmfCluster=myAmfCluster safAmfNode=fm2,safAmfCluster=myAmfCluster safAmfNode=PL-3,safAmfCluster=myAmfCluster safAmfNode=PL-4,safAmfCluster=myAmfCluster run logtest 4 Suite 4: LOG OI tests, stream objects 1 PASSED CCB Object Modify saLogStreamFileName 2 PASSED CCB Object Modify saLogStreamPathName, ERR not allowed 3 PASSED CCB Object Modify saLogStreamMaxLogFileSize 4 PASSED CCB Object Modify saLogStreamFixedLogRecordSize 5 PASSED CCB Object Modify saLogStreamLogFullAction=1 6 PASSED CCB Object Modify saLogStreamLogFullAction=2 7 PASSED CCB Object Modify saLogStreamLogFullAction=3 8 PASSED CCB Object Modify saLogStreamLogFullAction=4, ERR invalid 9 PASSED CCB Object Modify saLogStreamLogFullHaltThreshold=90% 10 PASSED CCB Object Modify saLogStreamLogFullHaltThreshold=101%, invalid 11 PASSED CCB Object Modify saLogStreamMaxFilesRotated 12 PASSED CCB Object Modify saLogStreamLogFileFormat 13 PASSED CCB Object Modify saLogStreamLogFileFormat - wrong format 14 PASSED CCB Object Modify saLogStreamSeverityFilter 15 PASSED saImmOiRtAttrUpdateCallback 16 PASSED Log Service Administration API, change sev filter for app stream OK 17 PASSED Log Service Administration API, change sev filter, ERR invalid stream 18 PASSED Log Service Administration API, change sev filter, ERR invalid arg type 19 PASSED Log Service Administration API, change sev filter, ERR invalid severity 20 PASSED Log Service Administration API, change sev filter, ERR invalid param name 21 PASSED Log Service Administration API, no change in sev filter, ERR NO OP 22 PASSED Log Service Administration API, invalid opId 23 PASSED Log Service Administration API, no parameters 24 PASSED CCB Object Create, strA 25 PASSED CCB Object Create, strB 26 PASSED CCB Object Create, strC 27 PASSED CCB Object Delete, strA 28 PASSED CCB Object Delete, strB 29 PASSED CCB Object Delete, strC 30 PASSED CCB Object Modify, saLogStreamMaxFilesRotated=1, strA 31 PASSED CCB Object Modify, saLogStreamMaxLogFileSize=0, strB, ERR not supported 32 PASSED CCB Object Modify, saLogStreamFixedLogRecordSize=150, strC 33 PASSED immlist strA-strC 34 PASSED immfind strA-strC 35 PASSED saflogger, writing to notification 36 PASSED saflogtest, writing to strA, strB, strC 37 PASSED CCB Object Modify, saLogStreamMaxLogFileSize=2000, strC 38 PASSED CCB Object Modify, saLogStreamFixedLogRecordSize=2048, strC, Error 39 PASSED CCB Object Modify, saLogStreamMaxLogFileSize=70, strC, Error 40 PASSED CCB Object Create, strD, illegal path, Error 41 PASSED CCB Object Create, strD 42 PASSED CCB Object Delete, strD 43 PASSED CCB Object Modify, saLogStreamLogFileFormat (strD) 44 PASSED saflogtest, writing to strD 45 PASSED CCB Object Modify, saLogStreamFileName (strD) 46 PASSED CCB Object Modify, saLogStreamLogFileFormat (all tokens) (strD) 47 PASSED saflogtest, writing to appTest 48 PASSED saflogtest, writing to saLogApplication1, severity filtering check 49 PASSED CCB Object Modify, saLogstreamLogFileFormat, timezone token (@Nz) 50 PASSED CCB Object Modify, saLogstreamLogFileFormat, millisecond token (@Nk) 51 PASSED CCB Object Modify, saLogstreamLogFileFormat, timezone token (@Cz) 52 PASSED CCB Object Modify, saLogstreamLogFileFormat, millisecond token (@Ck) 53 PASSED CCB Object Modify, saLogstreamLogFileFormat, timezone & millisecond token (@Cz @Ck) 54 PASSED CCB Object Modify, saLogStreamLogFileFormat, node name token (@Cq) 55 PASSED CCB Object Modify, saLogStreamLogFileFormat, network name token (@Cp) 56 PASSED Application stream with default log file format 57 PASSED CCB Object Modify, saLogStreamFileName with special character. ER 58 PASSED CCB Object Modify, saLogStreamSeverityFilter, filtering out log record that aren't written to log file = Test Result: Total: 58 Passed: 58 Failed: 0 Segmentation fault is not observed. --- ** [tickets:#2312] logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2 ** **Status:** assigned **Milestone:** future **Created:** Fri Feb 17, 2017 06:41 AM UTC by A V Mahesh (AVM) **Last Updated:** Fri Sep 22, 2017 05:43 AM UTC **Owner:** Srinivas
[tickets] [opensaf:tickets] #2312 logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#2312] logtest: Log test Segmentation faults if System controller name is other that SC-1 /SC-2 ** **Status:** assigned **Milestone:** future **Created:** Fri Feb 17, 2017 06:41 AM UTC by A V Mahesh (AVM) **Last Updated:** Fri Mar 24, 2017 10:59 AM UTC **Owner:** Srinivas Siva Mangipudy configure diffrent name for Systmen controlers (/usr/share/opensaf/immxml/nodes.cfg ) and created imm.xml and run logtest = /usr/share/opensaf/immxml # cat /usr/share/opensaf/immxml/nodes.cfg SC fm1 SC-1 SC fm2 PL-1 PL PL-3 PL-3 PL PL-4 PL-4 SC-1:~ # /usr/bin/logtest 4 Suite 4: LOG OI tests, stream objects 1 PASSED CCB Object Modify saLogStreamFileName; 2 PASSED CCB Object Modify saLogStreamPathName, ERR not allowed; 3 PASSED CCB Object Modify saLogStreamMaxLogFileSize; . 20 PASSED Log Service Administration API, change sev filter, ERR invalid param name; 21 PASSED Log Service Administration API, no change in sev filter, ERR NO OP; 22 PASSED Log Service Administration API, invalid opId; Segmentation fault SC-1:~ # / 14 PASSED CCB Object Modify saLogStreamSeverityFilter; Detaching after fork from child process 22461. 15 PASSED saImmOiRtAttrUpdateCallback; Detaching after fork from child process 22465. 16 PASSED Log Service Administration API, change sev filter for app stream OK; Detaching after fork from child process 22469. 17 PASSED Log Service Administration API, change sev filter, ERR invalid stream; Detaching after fork from child process 22473. 18 PASSED Log Service Administration API, change sev filter, ERR invalid arg type; Detaching after fork from child process 22477. 19 PASSED Log Service Administration API, change sev filter, ERR invalid severity; Detaching after fork from child process 22481. 20 PASSED Log Service Administration API, change sev filter, ERR invalid param name; Detaching after fork from child process 22485. Detaching after fork from child process 22489. 21 PASSED Log Service Administration API, no change in sev filter, ERR NO OP; Detaching after fork from child process 22493. 22 PASSED Log Service Administration API, invalid opId; Program received signal SIGSEGV, Segmentation fault. 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 312 src/log/apitest/logtest.c: No such file or directory. in src/log/apitest/logtest.c (gdb) bt /#0 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 /#1 0x55562ddc in saLogOi_116 () at src/log/apitest/tet_LogOiOps.c:582 /#2 0x55570855 in run_test_case () /#3 0x55570cf4 in test_run () /#4 0xbcad in main () at src/log/apitest/logtest.c:569 (gdb) dir /avm/staging-publish/ Source directories searched: /avm/staging-publish:$cdir:$cwd (gdb) bt /#0 0xdb50 in get_active_sc () at src/log/apitest/logtest.c:312 /#1 0x55562ddc in saLogOi_116 () at src/log/apitest/tet_LogOiOps.c:582 /#2 0x55570855 in run_test_case () /#3 0x55570cf4 in test_run () /#4 0xbcad in main () at src/log/apitest/logtest.c:569 (gdb) src/log/apitest # grep -r "SC-" * logtest.c: * @return 1 SC-1, 2 SC-2 logtest.c: SaConstStringT objname = "safSu=SC-1,safSg=2N,safApp=OpenSAF"; logtest.c: /* Checking SC-1 */ logtestfr.c: * @return 1 SC-1, 2 SC-2 logtestfr.c:SaNameT objectName1 = { /* Read object for SC-1 */ logtestfr.c:.value = "safSu=SC-1,safSg=2N,safApp=OpenSAF", logtestfr.c:.length = strlen("safSu=SC-1,safSg=2N,safApp=OpenSAF") + 1 logtestfr.c:/* Checking SC-1 */ --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2121 log: parsing command logtest with option -e is not correct
- **status**: assigned --> review --- ** [tickets:#2121] log: parsing command logtest with option -e is not correct** **Status:** review **Milestone:** future **Created:** Mon Oct 17, 2016 06:56 AM UTC by Canh Truong **Last Updated:** Tue Sep 19, 2017 09:11 AM UTC **Owner:** Srinivas Siva Mangipudy Parsing command logtest with option -e is wrong. For example: Running command logtest -e 14 2 All test cases in test suite 14 will be executed while we just expect that test case 2 of test suite 14 is executed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2586 build: dtm_inter_svc.c is being referred during make
- **status**: unassigned --> invalid --- ** [tickets:#2586] build: dtm_inter_svc.c is being referred during make** **Status:** invalid **Milestone:** 5.17.10 **Created:** Wed Sep 20, 2017 07:03 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Sep 20, 2017 08:33 AM UTC **Owner:** nobody src/dtm/dtmnd/dtm_inter_svc.c file has been changed to a .cc file, but “make” fails with the below error: CXXLDbin/osafclmna make[2]: *** No rule to make target 'src/dtm/dtmnd/dtm_inter_svc.c', needed by 'src/dtm/dtmnd/bin_osafdtmd-dtm_inter_svc.o'. Stop. make[2]: Leaving directory '/opensaf-code' Makefile:20145: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/opensaf-code' Makefile:6303: recipe for target 'all' failed make: *** [all] Error 2 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2586 build: dtm_inter_svc.c is being referred during make
after deleting the .deps folder in src/dtm/dtmnd and runnig "configure" command, the newly created bin_osafdtmd-dtm_inter_svc.Po file points to the "src/dtm/dtmnd/dtm_inter_svc.cc" and the make was sucessful. Hence closing the issue. --- ** [tickets:#2586] build: dtm_inter_svc.c is being referred during make** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Wed Sep 20, 2017 07:03 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Sep 20, 2017 08:08 AM UTC **Owner:** nobody src/dtm/dtmnd/dtm_inter_svc.c file has been changed to a .cc file, but “make” fails with the below error: CXXLDbin/osafclmna make[2]: *** No rule to make target 'src/dtm/dtmnd/dtm_inter_svc.c', needed by 'src/dtm/dtmnd/bin_osafdtmd-dtm_inter_svc.o'. Stop. make[2]: Leaving directory '/opensaf-code' Makefile:20145: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/opensaf-code' Makefile:6303: recipe for target 'all' failed make: *** [all] Error 2 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2586 build: dtm_inter_svc.c is being referred during make
bin_osafdtmd-dtm_inter_svc.Po still points to dtm_inter_svc.c src/dtm/dtmnd/.deps# head bin_osafdtmd-dtm_inter_svc.Po src/dtm/dtmnd/bin_osafdtmd-dtm_inter_svc.o: src/dtm/dtmnd/dtm_inter_svc.c \ --- ** [tickets:#2586] build: dtm_inter_svc.c is being referred during make** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Wed Sep 20, 2017 07:03 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Sep 20, 2017 07:18 AM UTC **Owner:** nobody src/dtm/dtmnd/dtm_inter_svc.c file has been changed to a .cc file, but “make” fails with the below error: CXXLDbin/osafclmna make[2]: *** No rule to make target 'src/dtm/dtmnd/dtm_inter_svc.c', needed by 'src/dtm/dtmnd/bin_osafdtmd-dtm_inter_svc.o'. Stop. make[2]: Leaving directory '/opensaf-code' Makefile:20145: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/opensaf-code' Makefile:6303: recipe for target 'all' failed make: *** [all] Error 2 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2586 build: dtm_inter_svc.c is being referred during make
--- ** [tickets:#2586] build: dtm_inter_svc.c is being referred during make** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Wed Sep 20, 2017 07:03 AM UTC by Srinivas Siva Mangipudy **Last Updated:** Wed Sep 20, 2017 07:03 AM UTC **Owner:** nobody src/dtm/dtmnd/dtm_inter_svc.c file has been changed to a .cc file, but “make” fails with the below error: CXXLDbin/osafclmna make[2]: *** No rule to make target 'src/dtm/dtmnd/dtm_inter_svc.c', needed by 'src/dtm/dtmnd/bin_osafdtmd-dtm_inter_svc.o'. Stop. make[2]: Leaving directory '/opensaf-code' Makefile:20145: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/opensaf-code' Makefile:6303: recipe for target 'all' failed make: *** [all] Error 2 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2121 log: parsing command logtest with option -e is not correct
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#2121] log: parsing command logtest with option -e is not correct** **Status:** assigned **Milestone:** future **Created:** Mon Oct 17, 2016 06:56 AM UTC by Canh Truong **Last Updated:** Mon Oct 17, 2016 06:56 AM UTC **Owner:** Srinivas Siva Mangipudy Parsing command logtest with option -e is wrong. For example: Running command logtest -e 14 2 All test cases in test suite 14 will be executed while we just expect that test case 2 of test suite 14 is executed. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #648 NTF IMCN: Reinitialize IMM API if OiImplementer set timeout
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#648] NTF IMCN: Reinitialize IMM API if OiImplementer set timeout** **Status:** assigned **Milestone:** future **Created:** Wed Dec 04, 2013 02:26 PM UTC by elunlen **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Srinivas Siva Mangipudy In imcn init: If ERR_EXIST re-initialize IMM API before changing name. If OiImplementerSet API timeout also re-initialize --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2039 NTF: Missleading returned code of ntftest when tests are failed
- **status**: assigned --> review - **Milestone**: future --> 5.17.10 --- ** [tickets:#2039] NTF: Missleading returned code of ntftest when tests are failed** **Status:** review **Milestone:** 5.17.10 **Created:** Thu Sep 15, 2016 09:11 AM UTC by Minh Hon Chau **Last Updated:** Thu Sep 07, 2017 05:51 AM UTC **Owner:** Srinivas Siva Mangipudy If running a test case of ntftest suite 37 (38, or 39) and it fails, the reported error is always SA_AIS_ERR_FAILED_OPERATION, but the actual failure code is different. The actual error code should be memorized and reported in test result. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1678 ntf: ntftest suite 35 result is not stable
- **status**: assigned --> invalid --- ** [tickets:#1678] ntf: ntftest suite 35 result is not stable** **Status:** invalid **Milestone:** future **Created:** Thu Feb 04, 2016 07:44 AM UTC by Quyen Dao **Last Updated:** Wed Sep 06, 2017 10:36 AM UTC **Owner:** Srinivas Siva Mangipudy root@SC-1:~# immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 8 Failed: 0 root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; error: in test_ntf_imcn.c at 4679: SA_AIS_ERR_TRY_AGAIN, expected SA_AIS_OK - exiting root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) 5 FAILED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute (expected SA_AIS_OK, got SA_AIS_ERR_FAILED_OPERATION); 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 7 Failed: 1 root@SC-1:~# --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2039 NTF: Missleading returned code of ntftest when tests are failed
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#2039] NTF: Missleading returned code of ntftest when tests are failed** **Status:** assigned **Milestone:** future **Created:** Thu Sep 15, 2016 09:11 AM UTC by Minh Hon Chau **Last Updated:** Tue Sep 20, 2016 05:51 PM UTC **Owner:** Srinivas Siva Mangipudy If running a test case of ntftest suite 37 (38, or 39) and it fails, the reported error is always SA_AIS_ERR_FAILED_OPERATION, but the actual failure code is different. The actual error code should be memorized and reported in test result. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1678 ntf: ntftest suite 35 result is not stable
Executed "ntftest 35" thru a shell script, 1000 times from a payload node and all 1000 times, the test was sucessful. Attached is the results file. This issue is not recreatable. Attachments: - [results.txt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/0c7087d8/940d/attachment/results.txt) (786.0 kB; text/plain) --- ** [tickets:#1678] ntf: ntftest suite 35 result is not stable** **Status:** assigned **Milestone:** future **Created:** Thu Feb 04, 2016 07:44 AM UTC by Quyen Dao **Last Updated:** Fri Sep 01, 2017 10:43 AM UTC **Owner:** Srinivas Siva Mangipudy root@SC-1:~# immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 8 Failed: 0 root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; error: in test_ntf_imcn.c at 4679: SA_AIS_ERR_TRY_AGAIN, expected SA_AIS_OK - exiting root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) 5 FAILED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute (expected SA_AIS_OK, got SA_AIS_ERR_FAILED_OPERATION); 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 7 Failed: 1 root@SC-1:~# --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #466 Length of the objectnames is more by one for configuration object notifications
- **status**: not-reproducible --> invalid - **Comment**: Tested with latest git rep ( commit a9a00db317978e4751213a2044a9dd99f6e548e8 ) and issue is not recreatable, hence closing it. --- ** [tickets:#466] Length of the objectnames is more by one for configuration object notifications** **Status:** invalid **Milestone:** future **Created:** Thu Jun 20, 2013 09:08 AM UTC by Sirisha Alla **Last Updated:** Mon Sep 04, 2017 06:57 AM UTC **Owner:** Srinivas Siva Mangipudy When ntfimcnd sends notifications for configuration object creation/modification/deletion, the length of the notifying object and the notification object is been shown wrongly. IMM callback gives the length of the notification object correctly. Notification object length in the imm callback: objectName->length: 37 objectName->value: 'attrName_testSA_registerSA_Node_37_69' Object create/modify/delete notifications indicate the length of notification object is 38 and the length of notifying object is 15 for "safApp=OpenSaf". This issue is reproducible. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #466 Length of the objectnames is more by one for configuration object notifications
- **status**: assigned --> not-reproducible --- ** [tickets:#466] Length of the objectnames is more by one for configuration object notifications** **Status:** not-reproducible **Milestone:** future **Created:** Thu Jun 20, 2013 09:08 AM UTC by Sirisha Alla **Last Updated:** Tue Aug 29, 2017 10:40 AM UTC **Owner:** Srinivas Siva Mangipudy When ntfimcnd sends notifications for configuration object creation/modification/deletion, the length of the notifying object and the notification object is been shown wrongly. IMM callback gives the length of the notification object correctly. Notification object length in the imm callback: objectName->length: 37 objectName->value: 'attrName_testSA_registerSA_Node_37_69' Object create/modify/delete notifications indicate the length of notification object is 38 and the length of notifying object is 15 for "safApp=OpenSaf". This issue is reproducible. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1678 ntf: ntftest suite 35 result is not stable
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy - **Blocker**: --> False --- ** [tickets:#1678] ntf: ntftest suite 35 result is not stable** **Status:** assigned **Milestone:** future **Created:** Thu Feb 04, 2016 07:44 AM UTC by Quyen Dao **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Srinivas Siva Mangipudy root@SC-1:~# immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 8 Failed: 0 root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; error: in test_ntf_imcn.c at 4679: SA_AIS_ERR_TRY_AGAIN, expected SA_AIS_OK - exiting root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) 5 FAILED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute (expected SA_AIS_OK, got SA_AIS_ERR_FAILED_OPERATION); 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 7 Failed: 1 root@SC-1:~# --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #466 Length of the objectnames is more by one for configuration object notifications
With the latest code, the issue is not recreatable. Test results: ( output of "ntfsubscribe -v" command below ) === Aug 29 14:20:29 - Attribute Change === notificationID = 13 subscriptionId = 1 eventType = SA_NTF_ATTRIBUTE_CHANGED notificationObject.length = 37 notificationObject = "attrName_testSA_registerSA_Node_37_69" notifyingObject.length = 14 notifyingObject = "safApp=OpenSaf" notificationClassId = 32993.8.0 (0x0) eventTime = 1503996629230537000 (Tue Aug 29 14:20:29 IST 2017) lengthAdditionalText = 0 sourceIndicator = SA_NTF_MANAGEMENT_OPERATION --- ** [tickets:#466] Length of the objectnames is more by one for configuration object notifications** **Status:** assigned **Milestone:** future **Created:** Thu Jun 20, 2013 09:08 AM UTC by Sirisha Alla **Last Updated:** Mon Aug 28, 2017 09:00 AM UTC **Owner:** Srinivas Siva Mangipudy When ntfimcnd sends notifications for configuration object creation/modification/deletion, the length of the notifying object and the notification object is been shown wrongly. IMM callback gives the length of the notification object correctly. Notification object length in the imm callback: objectName->length: 37 objectName->value: 'attrName_testSA_registerSA_Node_37_69' Object create/modify/delete notifications indicate the length of notification object is 38 and the length of notifying object is 15 for "safApp=OpenSaf". This issue is reproducible. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #466 Length of the objectnames is more by one for configuration object notifications
- **status**: unassigned --> assigned - **assigned_to**: Srinivas Siva Mangipudy --- ** [tickets:#466] Length of the objectnames is more by one for configuration object notifications** **Status:** assigned **Milestone:** future **Created:** Thu Jun 20, 2013 09:08 AM UTC by Sirisha Alla **Last Updated:** Thu Aug 24, 2017 05:48 AM UTC **Owner:** Srinivas Siva Mangipudy When ntfimcnd sends notifications for configuration object creation/modification/deletion, the length of the notifying object and the notification object is been shown wrongly. IMM callback gives the length of the notification object correctly. Notification object length in the imm callback: objectName->length: 37 objectName->value: 'attrName_testSA_registerSA_Node_37_69' Object create/modify/delete notifications indicate the length of notification object is 38 and the length of notifying object is 15 for "safApp=OpenSaf". This issue is reproducible. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets