[tickets] [opensaf:tickets] #1072 Sync stop after few payload nodes joining the cluster (TCP)

I am able to bring up 7 node cluster of Opensaf 4.5 code with TCP as Transport on VM setup of 512 MB memory ( with 70 node XML configuration ) with below specified Opensaf-socket (dtmd.conf)/Linux Send/Receive Buffers with out any issue

[tickets] [opensaf:tickets] Re: #1072 Sync stop after few payload nodes joining the cluster (TCP)

>On 10/2/2014 12:09 AM, Adrian Szwej wrote: > I have now applied patch for #1032 ontop of 4.6 changeset 5969:ead18326c13b. You mean [#1036] ? > [devel] [PATCH 1 of 1] mds: use correct buff-length to distinguish > mcast or multi-unicast [#1036] > This patch does not resolve the problem. This pa

Re: [tickets] [opensaf:tickets] #1072 Sync stop after few payload nodes joining the cluster (TCP)

Hi Adrian Szwej, On 10/2/2014 12:09 AM, Adrian Szwej wrote: I have now applied patch for #1032 ontop of 4.6 changeset *5969:ead18326c13b*. You mean [#1036] ? [devel] [PATCH 1 of 1] mds: use correct buff-length to distinguish mcast or multi-

[tickets] [opensaf:tickets] #230 core files are not getting formed for opensaf processes running with user opensaf

The following changes enable coredumps. diff -r ead18326c13b osaf/libs/core/common/daemon.c --- a/osaf/libs/core/common/daemon.cFri Sep 26 08:53:42 2014 +0200 +++ b/osaf/libs/core/common/daemon.cWed Oct 01 23:14:08 2014 + @@ -31,6 +31,7 @@ #include #include

[tickets] [opensaf:tickets] #1106 Coredumps are not generated when running as non root

The following patch enable coredump after setuid. diff -r ead18326c13b osaf/libs/core/common/daemon.c --- a/osaf/libs/core/common/daemon.cFri Sep 26 08:53:42 2014 +0200 +++ b/osaf/libs/core/common/daemon.cWed Oct 01 23:14:08 2014 + @@ -31,6 +31,7 @@ #includ

[tickets] [opensaf:tickets] #1072 Sync stop after few payload nodes joining the cluster (TCP)

I have now applied patch for #1032 ontop of 4.6 changeset **5969:ead18326c13b**. [devel] [PATCH 1 of 1] mds: use correct buff-length to distinguish mcast or multi-unicast [#1036] This patch does **not** resolve the problem. SC-1 immnd get the TRY_AGAIN message with to many outstanding messages.

[tickets] [opensaf:tickets] #1070 Access control don't check the primary group

- **status**: review --> fixed - **assigned_to**: Hans Feldt --> nobody --- ** [tickets:#1070] Access control don't check the primary group** **Status:** fixed **Milestone:** 4.5.0 **Created:** Fri Sep 12, 2014 07:59 PM UTC by Adrian Szwej **Last Updated:** Wed Sep 24, 2014 02:57 PM UTC **Ow

[tickets] [opensaf:tickets] #1138 opensaf as non root cannot be started in a container

- **status**: review --> fixed - **assigned_to**: Hans Feldt --> nobody - **Comment**: changeset: 5966:0fb0d27bde70 branch: opensaf-4.3.x parent: 5956:b8dfd4a2cc01 user:Hans Feldt date:Fri Sep 26 08:53:42 2014 +0200 summary: base: remove setgid/setuid calls in ex

[tickets] [opensaf:tickets] #1124 imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services

- **status**: accepted --> review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32886737/ --- ** [tickets:#1124] imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services** **Status:** review **Milestone:** 4.5.0 **Created:** Mon Sep 22, 2014 02:56 PM UTC by A

[tickets] [opensaf:tickets] #1120 CLM: clm sends SA_CLM_NODE_LEFT to active node

- **status**: review --> fixed - **Comment**: [staging:da9b03] [staging:50285c] [staging:b8dfd4] [staging:5f9ef2] [staging:09c46a] [staging:59a26a] [staging:f19978] [staging:314f5c] [staging:c74278] [staging:7d8b8a] [staging:1c48dd] [staging:1c0e18] changeset: 5954:da9b031be19f branch: ope

[tickets] [opensaf:tickets] #1124 imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services

- **status**: assigned --> accepted --- ** [tickets:#1124] imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services** **Status:** accepted **Milestone:** 4.5.0 **Created:** Mon Sep 22, 2014 02:56 PM UTC by Anders Widell **Last Updated:** Wed Oct 01, 2014 08:55 AM UTC **Owner:**

[tickets] [opensaf:tickets] #1126 SMF: Implementer-names must be re-used.

- **summary**: saImmOiImplementerSet returned ERR_LIB for campaign object DN greater than 255. --> SMF: Implementer-names must be re-used. - **Type**: enhancement --> defect - **Milestone**: future --> 4.3.3 - **Comment**: Changing this to a defect. Implementer names are not discarded by the imm

[tickets] [opensaf:tickets] #1148 IMM: Deprecate support for infinitely long class-names

- **summary**: IMM: DEprecate support for infinitely long class-names --> IMM: Deprecate support for infinitely long class-names - Description has changed: Diff: --- old +++ new @@ -8,7 +8,7 @@ not just impose a sanity limit on class-name-length. But the immsv can define a config attri

[tickets] [opensaf:tickets] #1148 IMM: DEprecate support for infinitely long class-names

--- ** [tickets:#1148] IMM: DEprecate support for infinitely long class-names** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Wed Oct 01, 2014 02:11 PM UTC by Anders Bjornerstedt **Last Updated:** Wed Oct 01, 2014 02:11 PM UTC **Owner:** nobody Currently (due to an omission) the i

[tickets] [opensaf:tickets] #673 dtm: leak mentioned by valgrind at mdtm_process_poll_recv_data_tcp()

- **Milestone**: 4.5.0 --> 4.6.FC --- ** [tickets:#673] dtm: leak mentioned by valgrind at mdtm_process_poll_recv_data_tcp()** **Status:** assigned **Milestone:** 4.6.FC **Created:** Wed Dec 18, 2013 09:22 AM UTC by A V Mahesh (AVM) **Last Updated:** Fri Aug 15, 2014 03:17 PM UTC **Owner:**

[tickets] [opensaf:tickets] #998 mds: change `tipc_or_tcp` variable from string to boolean to avoid strcmp

- **Milestone**: 4.5.0 --> 4.6.FC --- ** [tickets:#998] mds: change `tipc_or_tcp` variable from string to boolean to avoid strcmp** **Status:** assigned **Milestone:** 4.6.FC **Created:** Wed Aug 20, 2014 07:56 AM UTC by A V Mahesh (AVM) **Last Updated:** Wed Aug 20, 2014 07:56 AM UTC **Owne

[tickets] [opensaf:tickets] #928 base: Selection object fails due to re-cycled file descriptor

- **Milestone**: 4.5.0 --> 4.6.FC --- ** [tickets:#928] base: Selection object fails due to re-cycled file descriptor** **Status:** accepted **Milestone:** 4.6.FC **Created:** Wed May 28, 2014 07:48 AM UTC by Anders Widell **Last Updated:** Fri Aug 15, 2014 03:05 PM UTC **Owner:** nobody A c

[tickets] [opensaf:tickets] #1126 saImmOiImplementerSet returned ERR_LIB for campaign object DN greater than 255.

This is an enhancement ticket on SMF .. apaprently. The enhancement SMF I suggest should implement is to not use such long implementer-names. Does SMF run several campaigns in paralell ? Is that why SMF needs a separate OI (unique OI name) for each such concurrenlty existing campaign ? /Ander

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

- **Milestone**: 4.5.0 --> 4.6.FC --- ** [tickets:#537] make base code unit test friendly and remove any dead code** **Status:** accepted **Milestone:** 4.6.FC **Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan **Last Updated:** Fri Aug 15, 2014 03:07 PM UTC **Owner:** Ramesh A great

[tickets] [opensaf:tickets] #240 cpsv : checkpoint apis fail with try again continuously when multinode applications on try to invoke the api at the same time (70 nodes)

- **status**: accepted --> fixed - **Comment**: changeset: 5953:6ba1f54cd42f parent: 5951:86ec07bc91bc user:A V Mahesh date:Wed Oct 01 17:41:06 2014 +0530 summary: cpsv: Tune CPSV_WAIT_TIME for higher cluster size [#240] changeset: 5952:f9e12d446db6 branch: ope

[tickets] [opensaf:tickets] #1036 mds: IMMND restarts because of out of order messages

- **status**: assigned --> review --- ** [tickets:#1036] mds: IMMND restarts because of out of order messages** **Status:** review **Milestone:** 4.5.0 **Created:** Tue Sep 02, 2014 01:06 PM UTC by Neelakanta Reddy **Last Updated:** Tue Sep 23, 2014 10:05 AM UTC **Owner:** A V Mahesh (AVM) S

[tickets] [opensaf:tickets] #1126 saImmOiImplementerSet returned ERR_LIB for campaign object DN greater than 255.

- **Type**: defect --> enhancement - **Milestone**: 4.5.0 --> future - **Comment**: Currently IMM does not support object implementer names longer then 255. SMF needs to handle long OI names when IMM supports them. --- ** [tickets:#1126] saImmOiImplementerSet returned ERR_LIB for campaign obje

[tickets] [opensaf:tickets] #1130 immtools: immcfg is truncating the object names with longdns while loading

- **status**: unassigned --> accepted - **assigned_to**: Zoran Milinkovic - **Milestone**: 4.5.0 --> 4.3.3 - **Comment**: The same problem exists in immload. In some cases, long enough attribute name can also be truncated. --- ** [tickets:#1130] immtools: immcfg is truncating the object names

[tickets] [opensaf:tickets] #1089 immtools: buffer overflow in log_stderr_int in immcfg

- **status**: review --> fixed - **Comment**: opensaf-4.3.x: changeset: 5948:32afdc0a8169 branch: opensaf-4.3.x parent: 5940:665f39cbd878 user:Zoran Milinkovic date:Tue Sep 23 10:45:42 2014 +0200 summary: immtools: allocate enough memory for long log format in imm

[tickets] [opensaf:tickets] #1143 Opensaf Compilation issue on SLES 32bit machine.

- **status**: review --> fixed - **Comment**: [staging:80bc36] [staging:1c9578] changeset: 5947:1c9578f2fba3 tag: tip parent: 5945:17ebc648a310 user:Neelakanta Reddy date:Wed Oct 01 16:43:17 2014 +0530 summary: build:compilation issue on 32-bit machine [#1143]

[tickets] [opensaf:tickets] #1147 smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable

- **Comment**: Since #1124 moved to IMM, this ticket is not related to #1124 anymore. --- ** [tickets:#1147] smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable** **Status:** review **Milestone:** 4.5.0 **Created:** Wed Oct 01, 2014 08:12 AM UTC by Robert Apanowicz **Last Update

[tickets] [opensaf:tickets] #1147 smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable

- Description has changed: Diff: --- old +++ new @@ -1,3 +1,2 @@ -This is the SMF part of ticket 1124. Exporting "SA_ENABLE_EXTENDED_NAMES" shall be removed from configuration file of SMFD. SMFD shall always set the "SA_ENABLE_EXTENDED_NAMES" environmental variable at beginning of its m

[tickets] [opensaf:tickets] #1147 smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable

- **status**: accepted --> review --- ** [tickets:#1147] smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable** **Status:** review **Milestone:** 4.5.0 **Created:** Wed Oct 01, 2014 08:12 AM UTC by Robert Apanowicz **Last Updated:** Wed Oct 01, 2014 08:12 AM UTC **Owner:** Robert

[tickets] [opensaf:tickets] #1124 imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services

- **summary**: osaf: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services --> imm: SA_ENABLE_EXTENDED_NAMES should always be set in adapted services - **status**: unassigned --> assigned - **assigned_to**: Zoran Milinkovic - **Component**: osaf --> imm - **Comment**: Moving this tic

[tickets] [opensaf:tickets] #1143 Opensaf Compilation issue on SLES 32bit machine.

- **status**: accepted --> review --- ** [tickets:#1143] Opensaf Compilation issue on SLES 32bit machine.** **Status:** review **Milestone:** 4.3.3 **Created:** Tue Sep 30, 2014 09:28 AM UTC by manu **Last Updated:** Tue Sep 30, 2014 09:31 AM UTC **Owner:** Neelakanta Reddy Compilation issue

[tickets] [opensaf:tickets] #1147 smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable

- **status**: assigned --> accepted --- ** [tickets:#1147] smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable** **Status:** accepted **Milestone:** 4.5.0 **Created:** Wed Oct 01, 2014 08:12 AM UTC by Robert Apanowicz **Last Updated:** Wed Oct 01, 2014 08:12 AM UTC **Owner:** Rob

[tickets] [opensaf:tickets] #1147 smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable

--- ** [tickets:#1147] smf: SA_ENABLE_EXTENDED_NAMES env var should not be configurable** **Status:** assigned **Milestone:** 4.5.0 **Created:** Wed Oct 01, 2014 08:12 AM UTC by Robert Apanowicz **Last Updated:** Wed Oct 01, 2014 08:12 AM UTC **Owner:** Robert Apanowicz This is the SMF part

[tickets] [opensaf:tickets] #1145 IMM incorrect/irrelevant logging during loading with modified/corrupt xml file

Note also that the 'multivalued error' is reported by osafimmnd, not the immloader. I would claim that this is correctly reported by osafimmnd. Thus the immloader gets derailed by the corrupt imm.xml file and it generated an obj-create requests towards the immsv which has this exact problem, repo

Re: [tickets] [opensaf:tickets] #1145 IMM incorrect/irrelevant logging during loading with modified/corrupt xml file

Note also that the 'multivalued error' is reported by osafimmnd, not the immloader. I would claim that this is correctly reported by osafimmnd. Thus the immloader gets derailed by the corrupt imm.xml file and it generated an obj-create requests towards the immsv which has this exact problem, repo

[tickets] [opensaf:tickets] Re: #1145 IMM incorrect/irrelevant logging during loading with modified/corrupt xml file

Hi Surender, My point is this: The main purpose of the immloader is to load the imm as fast as possible (a cluster restart is *the* archetypical high-availability problem, if there is any). If the loading fails due to a corrupt imm.xml file then the only priority for the imm-loader is to clearly

[tickets] [opensaf:tickets] #205 Communication paths among IMM entities shown in PRDOC is not as per its description

- **status**: assigned --> fixed - **Comment**: IMMSV PR is updated in the below changeset changeset: 128:f61d114fae33 tag: tip user:Neelakanta Reddy date:Wed Oct 01 13:13:44 2014 +0530 summary: imm:Updated OpenSAF_IMMSv_PR.odt for OpenSAF 4.5[#984] --- ** [tic

[tickets] [opensaf:tickets] #936 IMM: Document OiImplementer set for 2nd time returns ERR_INVALID_PARAM

- **status**: accepted --> fixed - **Comment**: IMMSV PR is updated in the below changeset changeset: 128:f61d114fae33 tag: tip user:Neelakanta Reddy date:Wed Oct 01 13:13:44 2014 +0530 summary: imm:Updated OpenSAF_IMMSv_PR.odt for OpenSAF 4.5[#984] --- ** [tic

[tickets] [opensaf:tickets] #984 imm: IMM PR doc update for 4.5

- **status**: review --> fixed - **Comment**: changeset: 128:f61d114fae33 tag: tip user:Neelakanta Reddy date:Wed Oct 01 13:13:44 2014 +0530 summary: imm:Updated OpenSAF_IMMSv_PR.odt for OpenSAF 4.5[#984] --- ** [tickets:#984] imm: IMM PR doc update for 4.5 **

Re: [tickets] [opensaf:tickets] #1145 IMM incorrect/irrelevant logging during loading with modified/corrupt xml file

Hi Surender, My point is this: The main purpose of the immloader is to load the imm as fast as possible (a cluster restart is *the* archetypical high-availability problem, if there is any). If the loading fails due to a corrupt imm.xml file then the only priority for the imm-loader is to clearly