[tickets] [opensaf:tickets] #532 leap: non async-signal-safe functions used in ncs_os_process_execute_timed()

2013-08-14 Thread Ramesh
Ok. Either way a ticket should be raised to resolve point-1. Because this issue(of IMMD) can occur if there is a problem in the CLC-script. w.r.t point-2, did we observe any other practical issue (i.e., other than syslog) with the current code fork() --execvp?. In my opinion, removing

[tickets] [opensaf:tickets] #532 leap: non async-signal-safe functions used in ncs_os_process_execute_timed()

2013-08-20 Thread Ramesh
take it up further. Otherwise the current implementation holds good. If the issue still persist and is consistent, can we get the respective core-dump by applying the alarm patch floated by Hans N. Because Nagendra tried all possible ways to reproduce the issue and failed. Thanks, Ramesh

[tickets] [opensaf:tickets] #532 base: non async-signal-safe functions used in ncs_os_process_execute_timed()

2013-09-03 Thread Ramesh
, Ramesh. --- ** [tickets:#532] base: non async-signal-safe functions used in ncs_os_process_execute_timed()** **Status:** unassigned **Created:** Tue Aug 06, 2013 11:04 AM UTC by hano **Last Updated:** Mon Aug 26, 2013 01:38 PM UTC **Owner:** nobody In the nid phase amfnd is about

[tickets] [opensaf:tickets] #34 Add utility function for pretty-printing errno

2013-09-09 Thread Ramesh
- **Milestone**: 4.4.FC -- future --- ** [tickets:#34] Add utility function for pretty-printing errno** **Status:** unassigned **Created:** Tue May 07, 2013 11:16 AM UTC by Ramesh **Last Updated:** Mon Aug 26, 2013 01:39 PM UTC **Owner:** nobody The function strerror() is used at many places

[tickets] [opensaf:tickets] #537 make base code unit test friendly and remove any dead code

2013-09-09 Thread Ramesh
- **status**: unassigned -- accepted - **assigned_to**: Ramesh --- ** [tickets:#537] make base code unit test friendly and remove any dead code** **Status:** accepted **Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan **Last Updated:** Mon Sep 09, 2013 10:33 AM UTC **Owner:** Ramesh

[tickets] [opensaf:tickets] #537 make base code unit test friendly and remove any dead code

2015-09-16 Thread Ramesh
Majority of code clean-up or organization in BASE/LEAP happened in 4.4 cycle itself. However further refinement (if any) will be taken up in 5.0 cycle. changeset: 4722:a7fd4081b098 user:Ramesh <ramesh.bet...@oracle.com> date:Thu Dec 12 15:24:26 2013 +0530 summary:

[tickets] [opensaf:tickets] #537 make base code unit test friendly and remove any dead code

2015-09-16 Thread Ramesh
- **Milestone**: 4.7.FC --> 5.0 --- ** [tickets:#537] make base code unit test friendly and remove any dead code** **Status:** accepted **Milestone:** 5.0 **Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan **Last Updated:** Wed Sep 16, 2015 12:10 PM UTC **Owner:** Ramesh A gr

[tickets] [opensaf:tickets] #537 make base code unit test friendly and remove any dead code

2016-03-22 Thread Ramesh
- **Milestone**: 5.0.FC --> future --- ** [tickets:#537] make base code unit test friendly and remove any dead code** **Status:** accepted **Milestone:** future **Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan **Last Updated:** Sun Nov 01, 2015 09:36 PM UTC **Owner:** Ram

[tickets] [opensaf:tickets] #1712 Check the available space of "/dev/shm" file system

2016-03-28 Thread Ramesh
--- ** [tickets:#1712] Check the available space of "/dev/shm" file system** **Status:** unassigned **Milestone:** 5.0.FC **Created:** Tue Mar 29, 2016 05:38 AM UTC by Ramesh **Last Updated:** Tue Mar 29, 2016 05:38 AM UTC **Owner:** nobody Check the available space on "/

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2017-01-22 Thread Ramesh
ner:** Ramesh Steps to reproduce: 1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 components on SC-2 and unlock them. Keep 1 sec delay in each component stop script. 2. Stop SC-1 and after that, stop SC-2. 3. During SC-2 is going down, start SC-1. Observed behavi

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2017-02-23 Thread Ramesh
ner:** Ramesh Steps to reproduce: 1. Start two controllers(SC-1 Act, SC-2 Standby) and two paylods. Configure 50 components on SC-2 and unlock them. Keep 1 sec delay in each component stop script. 2. Stop SC-1 and after that, stop SC-2. 3. During SC-2 is going down, start SC-1. Observed behaviour: Si

[tickets] [opensaf:tickets] #2041 Msg: saMsgInitialize is returning continuous TRY_AGAINS after mqsv ndrestarts in backward compatability.

2016-09-19 Thread Ramesh
- **Component**: msg --> imm - **Comment**: Seems this failure need to be investigate from IMM context as "immutil_saImmOiInitialize_2()" is returning SA_AIS_ERR_TIMEOUT error code. --- ** [tickets:#2041] Msg: saMsgInitialize is returning continuous TRY_AGAINS after mqsv ndrestarts in

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2016-11-08 Thread Ramesh
- **Type**: discussion --> enhancement --- ** [tickets:#2151] osaf: system in not in correct state during Act controller comming up** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar **Last Updated:** Fri Nov 04, 2016 12:33 PM UTC

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2016-11-08 Thread Ramesh
Based on the current implementation (functional) scope holding by different services of OpenSAF, introducing such functional behaviour into FM module seems more appropriate to handle the scenario. FM is been already in MDS subscription with AMFD, AMFND etc. However, this proposal is

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2016-11-22 Thread Ramesh
- **status**: unassigned --> assigned - **assigned_to**: Ramesh --- ** [tickets:#2151] osaf: system in not in correct state during Act controller comming up** **Status:** assigned **Milestone:** 5.2.FC **Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar **Last Updated:** Tue Nov

[tickets] [opensaf:tickets] Re: #2174 MDS: mdstest 5 1 failed

2017-03-23 Thread Ramesh
Mahesh, You can move the status to not-reproducible. Thanks, Ramesh. On 3/23/2017 12:09 PM, A V Mahesh (AVM) wrote: > > * *status*: assigned --> accepted > * *Comment*: > > Not able to reproduce the problem on changeset: 8711, with & without > export MDS_LOG_LEVEL

[tickets] [opensaf:tickets] #2363 fm: ER Two active controllers observed in a cluster

2017-03-14 Thread Ramesh
- **status**: review --> fixed --- ** [tickets:#2363] fm: ER Two active controllers observed in a cluster** **Status:** fixed **Milestone:** 5.2.RC1 **Created:** Fri Mar 10, 2017 03:48 PM UTC by elunlen **Last Updated:** Tue Mar 14, 2017 08:23 AM UTC **Owner:** Ramesh **Attachme

[tickets] [opensaf:tickets] #2363 fm: ER Two active controllers observed in a cluster

2017-03-14 Thread Ramesh
- **status**: accepted --> review --- ** [tickets:#2363] fm: ER Two active controllers observed in a cluster** **Status:** review **Milestone:** 5.2.RC1 **Created:** Fri Mar 10, 2017 03:48 PM UTC by elunlen **Last Updated:** Tue Mar 14, 2017 05:19 AM UTC **Owner:** Ramesh **Attachme

[tickets] [opensaf:tickets] #2363 fm: ER Two active controllers observed in a cluster

2017-03-14 Thread Ramesh
- **status**: unassigned --> assigned - **assigned_to**: Ramesh - **Comment**: Just to avoid confusion, changing **LOG_ER to LOG_WA** is sufficient ti fix this ticket. No other fix required. In these scenarios, need to check whether any application component on old-Active node is taking t

[tickets] [opensaf:tickets] #2363 fm: ER Two active controllers observed in a cluster

2017-03-14 Thread Ramesh
- **status**: assigned --> accepted --- ** [tickets:#2363] fm: ER Two active controllers observed in a cluster** **Status:** accepted **Milestone:** 5.2.RC1 **Created:** Fri Mar 10, 2017 03:48 PM UTC by elunlen **Last Updated:** Tue Mar 14, 2017 05:14 AM UTC **Owner:** Ramesh **Attachme

[tickets] [opensaf:tickets] #2363 fm: ER Two active controllers observed in a cluster

2017-03-13 Thread Ramesh
The reported ERR is not an issue. ER log reports the current state of the cluster and FM takes necessary correction (a fix of #2151) accordingly. Please see ticket #2151 for more details. --- ** [tickets:#2363] fm: ER Two active controllers observed in a cluster** **Status:** unassigned

[tickets] [opensaf:tickets] #2151 osaf: system in not in correct state during Act controller comming up

2017-03-02 Thread Ramesh
- **status**: review --> fixed - **Comment**: Fixed: changeset: 8641:de2260ab6ad4 tag: tip user: Ramesh Betham<ramesh.bet...@oracle.com> date:Fri Mar 03 10:52:34 2017 +0530 summary: osaf:fm on new-Active handling amfd up event of peer old-Active node which

Re: [tickets] [opensaf:tickets] #1050 amfnd sometimes fails to start due to ERR_LIBRARY from saImmOmInitialize

2014-09-17 Thread ramesh betham
review comments. Best Regards, Ramesh. On 9/17/2014 7:33 PM, Hans Feldt wrote: * *Comment*: Here's a trace snippet from an opensaf start that it is hard to explain... Sep 8 13:47:55.90 osafimmnd [5233:mds_c_api.c:1614] TR svc UP process_info NOTEXIST, svc:26, adest:2020f53b80025 Sep 8 13