date:20160411

[tickets] [opensaf:tickets] #1748 MQSV service is not working ( Queue open does not succeed)

2016-04-11 Thread A V Mahesh (AVM)

Reproduce the problem with samples :
Just run mqsv sample   on two different consoles :

-
SC-1# samples/mqsv # ./msg_demo 1
 
STARTING THE MQSv DEMO
==
MessageQ Sender Application
Apr 12 11:00:55 SC-1 osafmsgd[3806]: ER Sending the message to the specified 
destination with error 6
Apr 12 11:00:55 SC-1 osafmsgd[3806]: ER ERR_FAILED_OPERATION: Couldn't Send 
ASAPi Name Resolution Response Message
##
 
SCENARIO#1:Sending Messages via Sync API - saMsgMessageSend START


SC-1# samples/mqsv # ./msg_demo 0
 
STARTING THE MQSv DEMO
==
MessageQ Receiver Application
#
 
DEMO SCENARIO#1: Receiving messages via Sync API - saMsgMessageGet START
 
 
MQSV:MQA:ONsaMsgQueueOpen failed with rc - 6
Press Enter Key to Continue...

-
 


---

** [tickets:#1748] MQSV service is not working ( Queue open does not succeed) **

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Tue Apr 12, 2016 03:49 AM UTC by Srikanth R
**Last Updated:** Tue Apr 12, 2016 03:52 AM UTC
**Owner:** nobody
**Attachments:**

- 
[mqsv.tgz](https://sourceforge.net/p/opensaf/tickets/1748/attachment/mqsv.tgz) 
(109.2 kB; application/x-compressed-tar)


Changeset : 7436 
Version : 5.0 FC


Issue : 

1) Queue opening fails with TRY_AGAIN / TIME_OUT.  

Below is the output of sample application :

DEMO SCENARIO#1: Receiving messages via Sync API - saMsgMessageGet START


MQSV:MQA:ONsaMsgQueueOpen failed with rc - 6
Press Enter Key to Continue...

Below is the output of test application with retry mechanism handled.

100|0| RETRY   : saMsgQueueOpen with valid params - Non Persistent
100|0| Return Value: SA_AIS_ERR_TRY_AGAIN
100|0|
100|0| Retry Count : 10
100|0| Retry Count : 20
100|0| Retry Count : 30
100|0| Retry Count : 40
100|0| Try again count exceeded


In the case of aysnc, queue open callback returns TRY_AGAIN.
 
100|0| Queue name  : safMq=nonpersistent_Q_37
100|0| size: 1000
100|0| creation flags  : SA_MSG_QUEUE_NON_PERSISTENT
100|0| open flags  : SA_MSG_QUEUE_CREATE
100|0| SUCCESS : saMsgQueueOpenAsync with valid parameters - Non 
Persistent
100|0| Return Value: SA_AIS_OK
100|0| Invocation  : 115
100|0|
100|0|
100|0| --- Queue Open Callback -
100|0| Error String  : SA_AIS_ERR_TRY_AGAIN
100|0| Invocation  : 115
100|0| ---

Below is the output in syslog .

Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER ERR_TRY_AGAIN: Timeout occurs 
Unable to send the respons in async case
Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER The procedure to open the 
Queue Failed with err 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER Sending the message to the 
specified destination with error 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER ERR_FAILED_OPERATION: Couldn't 
Send ASAPi Name Resolution Response Message



2) saMsgInitialize  and saMsgFinalize returning  TIME_OUT, which is not earlier 
observed on an idle system .


100|0| * Create a queue with zero retention time using saMsgQueueOpen *
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| FAILED  : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT
100|0|
100|0|
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK



100|0| Version : B.3.1
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK
100|0| Message Handle  : 6876704
100|0| Version Output  : B.3.1

100|0| FAILED  : saMsgFinalize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT


Traces of msgd, msgnd and test application are attached


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your

[tickets] [opensaf:tickets] #1740 amfd: unlock operation on SU gets timed out.

2016-04-11 Thread Praveen

- Description has changed:

Diff:



--- old
+++ new
@@ -10,19 +10,6 @@
 5) Since in the second assignment it is not the SU that was being unlocked, 
AMF loses the context of admin operation and when SG becomes stable it never 
searches for any pending admin operation. 
 6) AMFD never respond to IMM for the completion of admin operation,
 
-Also there is one more problem since AMF does not respond to the admin 
opeartion, it does not clear admin operation param in the SU. But when same SU 
is tried for lock operation, AMFD allowed it. Actually AMFD is checking all the 
other SUs in SG for any pending admin operation except for the SU for admin 
operation request had come. The problem is with the check in su.cc
-
- /* Avoid multiple admin operations on other SUs belonging to the same SG. */
-for (auto const& su_ptr : su->sg_of_su->list_of_su) {
-/* su's sg_fsm_state is checked below, just check other su. */
-if ((su != su_ptr) && (su_ptr->pend_cbk.invocation != 0)) {
-report_admin_op_error(immoi_handle, invocation, 
SA_AIS_ERR_TRY_AGAIN, nullptr,
-"Admin operation is already going on 
(su'%s')", su_ptr->name.value);
-goto done;
-}
-}
-if condition should not include expression (su != su_ptr).
-
 
 Attached is the amfd log and amfnd log and imm.xml
 



- **status**: accepted --> review
- **Comment**:

The other probelm is not there. In su_admin_op_cb(), AMFD is taking care of 
returning TRY_AGAIN.



---

** [tickets:#1740] amfd: unlock operation on SU gets timed out.**

**Status:** review
**Milestone:** 4.6.2
**Labels:** Admin op 
**Created:** Thu Apr 07, 2016 12:43 PM UTC by Praveen
**Last Updated:** Thu Apr 07, 2016 12:44 PM UTC
**Owner:** Praveen
**Attachments:**

- [imm.xml](https://sourceforge.net/p/opensaf/tickets/1740/attachment/imm.xml) 
(156.5 kB; text/xml)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/1740/attachment/osafamfd) 
(1.1 MB; application/octet-stream)
- 
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/1740/attachment/osafamfnd)
 (687.6 kB; application/octet-stream)


Applicable to all red models except NWAY. 
Appear in a special case when after cluster timer expiry unlock operation is 
invoked.
Attached is imm.xml in which problem is simulated with NoRed model.
About the application, in imm.xml one of the SU is kept in locked state.
Steps to reproduce:
1) Bring up one controller up with the above configuration.
2) After cluster timer expiry, AMF will instantiate the SUs. Make sure that 
instantiattion of unlocked su get delayed so that enoug time is to issue a 
unlock on the locked su.
3) When component of unlocked is instantiating, issue unlock of locked SU. Now 
again make sure that response to the assignment is done after instantiation of 
unlocked su gets completed.
4) After instantiation of unlocked su, AMFd get response from AMFND for the 
admin operated SU and it gives assignment to newly instantiated SU and thus SG 
remains unstable.
5) Since in the second assignment it is not the SU that was being unlocked, AMF 
loses the context of admin operation and when SG becomes stable it never 
searches for any pending admin operation. 
6) AMFD never respond to IMM for the completion of admin operation,


Attached is the amfd log and amfnd log and imm.xml







---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1739 log: logsv is providing same active handle value for different api calls

2016-04-11 Thread Vu Minh Nguyen

- **summary**: Logsv is providing same active handle value for different api 
calls --> log: logsv is providing same active handle value for different api 
calls
- **status**: accepted --> review



---

** [tickets:#1739] log: logsv is providing same active handle value for 
different api calls**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj
**Last Updated:** Tue Apr 12, 2016 04:41 AM UTC
**Owner:** Vu Minh Nguyen


Setup:
Changeset- 7436
Version - opensaf 5.0

Issue :
  Logsv is issuing same active handle value for different api calls

Steps:
 -> The logsv application stores the global system stream handle and for couple 
of scenarios , initialization and finalization has been done.
 
 -> At the startup of the application, system stream handle (4288675841) is 
obtained.
 
 -> After couple of flows, the initialization api saLogInitialize() obtained 
same handle ( 4288675841) and was finalized.
 
 ->  So when saLogWriteLogAsync()  api is invoked  with the earlier obtained 
system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE.  Note that the 
init  handle  associated with the system stream handle 4288675841  is not 
finalized.


100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4290772993
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4287627265
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4286578689
100|0|system stream handle  4288675841
...
100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogFinalize()
100|0|  Handle used is 4288675841
100|0| Return value : <-- SA_AIS_OK
100|0|Invoking saLogSelectionObjectGet()
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE

100|0|Invoking saLogWriteLogAsync()
100|0|Handle used is 4288675841
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE
100|0|saLogWriteLogAsync return values did not match Actual_Value :9  
Expected_Value :1

 This application used to work with 4.7


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls

2016-04-11 Thread Vu Minh Nguyen

- **status**: unassigned --> accepted
- **assigned_to**: Vu Minh Nguyen
- **Milestone**: 4.6.2 --> 5.0.RC2



---

** [tickets:#1739] Logsv is providing same active handle value for different 
api calls**

**Status:** accepted
**Milestone:** 5.0.RC2
**Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj
**Last Updated:** Mon Apr 11, 2016 11:51 AM UTC
**Owner:** Vu Minh Nguyen


Setup:
Changeset- 7436
Version - opensaf 5.0

Issue :
  Logsv is issuing same active handle value for different api calls

Steps:
 -> The logsv application stores the global system stream handle and for couple 
of scenarios , initialization and finalization has been done.
 
 -> At the startup of the application, system stream handle (4288675841) is 
obtained.
 
 -> After couple of flows, the initialization api saLogInitialize() obtained 
same handle ( 4288675841) and was finalized.
 
 ->  So when saLogWriteLogAsync()  api is invoked  with the earlier obtained 
system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE.  Note that the 
init  handle  associated with the system stream handle 4288675841  is not 
finalized.


100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4290772993
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4287627265
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4286578689
100|0|system stream handle  4288675841
...
100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogFinalize()
100|0|  Handle used is 4288675841
100|0| Return value : <-- SA_AIS_OK
100|0|Invoking saLogSelectionObjectGet()
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE

100|0|Invoking saLogWriteLogAsync()
100|0|Handle used is 4288675841
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE
100|0|saLogWriteLogAsync return values did not match Actual_Value :9  
Expected_Value :1

 This application used to work with 4.7


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1748 MQSV service is not working ( Queue open does not succeed)

2016-04-11 Thread Srikanth R

- Description has changed:

Diff:



--- old
+++ new
@@ -86,4 +86,4 @@
 100|0| Return Value: SA_AIS_ERR_TIMEOUT
 
 
-3) 
+Traces of msgd, msgnd and test application are attached



- Attachments has changed:

Diff:



--- old
+++ new
@@ -0,0 +1 @@
+mqsv.tgz (109.2 kB; application/x-compressed-tar)






---

** [tickets:#1748] MQSV service is not working ( Queue open does not succeed) **

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Tue Apr 12, 2016 03:49 AM UTC by Srikanth R
**Last Updated:** Tue Apr 12, 2016 03:49 AM UTC
**Owner:** nobody
**Attachments:**

- 
[mqsv.tgz](https://sourceforge.net/p/opensaf/tickets/1748/attachment/mqsv.tgz) 
(109.2 kB; application/x-compressed-tar)


Changeset : 7436 
Version : 5.0 FC


Issue : 

1) Queue opening fails with TRY_AGAIN / TIME_OUT.  

Below is the output of sample application :

DEMO SCENARIO#1: Receiving messages via Sync API - saMsgMessageGet START


MQSV:MQA:ONsaMsgQueueOpen failed with rc - 6
Press Enter Key to Continue...

Below is the output of test application with retry mechanism handled.

100|0| RETRY   : saMsgQueueOpen with valid params - Non Persistent
100|0| Return Value: SA_AIS_ERR_TRY_AGAIN
100|0|
100|0| Retry Count : 10
100|0| Retry Count : 20
100|0| Retry Count : 30
100|0| Retry Count : 40
100|0| Try again count exceeded


In the case of aysnc, queue open callback returns TRY_AGAIN.
 
100|0| Queue name  : safMq=nonpersistent_Q_37
100|0| size: 1000
100|0| creation flags  : SA_MSG_QUEUE_NON_PERSISTENT
100|0| open flags  : SA_MSG_QUEUE_CREATE
100|0| SUCCESS : saMsgQueueOpenAsync with valid parameters - Non 
Persistent
100|0| Return Value: SA_AIS_OK
100|0| Invocation  : 115
100|0|
100|0|
100|0| --- Queue Open Callback -
100|0| Error String  : SA_AIS_ERR_TRY_AGAIN
100|0| Invocation  : 115
100|0| ---

Below is the output in syslog .

Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER ERR_TRY_AGAIN: Timeout occurs 
Unable to send the respons in async case
Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER The procedure to open the 
Queue Failed with err 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER Sending the message to the 
specified destination with error 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER ERR_FAILED_OPERATION: Couldn't 
Send ASAPi Name Resolution Response Message



2) saMsgInitialize  and saMsgFinalize returning  TIME_OUT, which is not earlier 
observed on an idle system .


100|0| * Create a queue with zero retention time using saMsgQueueOpen *
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| FAILED  : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT
100|0|
100|0|
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK



100|0| Version : B.3.1
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK
100|0| Message Handle  : 6876704
100|0| Version Output  : B.3.1

100|0| FAILED  : saMsgFinalize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT


Traces of msgd, msgnd and test application are attached


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1748 MQSV service is not working ( Queue open does not succeed)

2016-04-11 Thread Srikanth R




---

** [tickets:#1748] MQSV service is not working ( Queue open does not succeed) **

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Tue Apr 12, 2016 03:49 AM UTC by Srikanth R
**Last Updated:** Tue Apr 12, 2016 03:49 AM UTC
**Owner:** nobody


Changeset : 7436 
Version : 5.0 FC


Issue : 

1) Queue opening fails with TRY_AGAIN / TIME_OUT.  

Below is the output of sample application :

DEMO SCENARIO#1: Receiving messages via Sync API - saMsgMessageGet START


MQSV:MQA:ONsaMsgQueueOpen failed with rc - 6
Press Enter Key to Continue...

Below is the output of test application with retry mechanism handled.

100|0| RETRY   : saMsgQueueOpen with valid params - Non Persistent
100|0| Return Value: SA_AIS_ERR_TRY_AGAIN
100|0|
100|0| Retry Count : 10
100|0| Retry Count : 20
100|0| Retry Count : 30
100|0| Retry Count : 40
100|0| Try again count exceeded


In the case of aysnc, queue open callback returns TRY_AGAIN.
 
100|0| Queue name  : safMq=nonpersistent_Q_37
100|0| size: 1000
100|0| creation flags  : SA_MSG_QUEUE_NON_PERSISTENT
100|0| open flags  : SA_MSG_QUEUE_CREATE
100|0| SUCCESS : saMsgQueueOpenAsync with valid parameters - Non 
Persistent
100|0| Return Value: SA_AIS_OK
100|0| Invocation  : 115
100|0|
100|0|
100|0| --- Queue Open Callback -
100|0| Error String  : SA_AIS_ERR_TRY_AGAIN
100|0| Invocation  : 115
100|0| ---

Below is the output in syslog .

Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER ERR_TRY_AGAIN: Timeout occurs 
Unable to send the respons in async case
Apr 10 20:31:21 CONTROLLER-2 osafmsgnd[13195]: ER The procedure to open the 
Queue Failed with err 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER Sending the message to the 
specified destination with error 6
Apr 10 20:31:21 CONTROLLER-2 osafmsgd[13213]: ER ERR_FAILED_OPERATION: Couldn't 
Send ASAPi Name Resolution Response Message



2) saMsgInitialize  and saMsgFinalize returning  TIME_OUT, which is not earlier 
observed on an idle system .


100|0| * Create a queue with zero retention time using saMsgQueueOpen *
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| FAILED  : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT
100|0|
100|0|
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0|
100|0| Version : B.3.1
100|0|MQSV:MQA:ON
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK



100|0| Version : B.3.1
100|0| SUCCESS : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_OK
100|0| Message Handle  : 6876704
100|0| Version Output  : B.3.1

100|0| FAILED  : saMsgFinalize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TIMEOUT


3) 


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1726 immtools: immcfg is slow when working with a large number of objects

2016-04-11 Thread Hung Nguyen

- **status**: review --> fixed



---

** [tickets:#1726] immtools: immcfg is slow when working with a large number of 
objects**

**Status:** fixed
**Milestone:** 4.7.1
**Created:** Wed Apr 06, 2016 07:19 AM UTC by Hung Nguyen
**Last Updated:** Tue Apr 12, 2016 03:05 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[create_objects.sh](https://sourceforge.net/p/opensaf/tickets/1726/attachment/create_objects.sh)
 (2.3 kB; application/octet-stream)


immcfg from OpenSAF 4.6
root@SC-1:~# time /tmp/immcfg_46 -f /tmp/20k_objects.xml
real0m15.502s
user0m1.480s
sys 0m1.368s

immcfg from OpenSAF 4.7
root@SC-1:~# time immcfg -f /tmp/20k_objects.xml
real0m21.919s
user0m4.976s
sys 0m1.656s

Attached is the script used to generate the xml file.
root@SC-1:~# ./create_objects.sh 2 > /tmp/20k_objects.xml

Related ticket: [#1283]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1726 immtools: immcfg is slow when working with a large number of objects

2016-04-11 Thread Hung Nguyen


opensaf-4.7.x [staging:cdcd31]
changeset:   7479:cdcd318cbc8e
branch:  opensaf-4.7.x
parent:  7476:8de790072798
user:Hung Nguyen 
date:Thu Apr 07 15:03:31 2016 +0700
summary: immtools: Improve object info list handling in immcfg [#1726]

opensaf-5.0.x [staging:b3c036]
changeset:   7480:b3c036f1b0bd
branch:  opensaf-5.0.x
parent:  7478:d04daac4cb0c
user:Hung Nguyen 
date:Thu Apr 07 16:37:51 2016 +0700
summary: immtools: Use safe read to retrieve class name for immcfg [#1726]

opensaf-5.1.x [staging:3476bd]
changeset:   7481:3476bd4fd93b
tag: tip
parent:  7472:17f1193a61df
user:Hung Nguyen 
date:Thu Apr 07 16:37:51 2016 +0700
summary: immtools: Use safe read to retrieve class name for immcfg [#1726]



---

** [tickets:#1726] immtools: immcfg is slow when working with a large number of 
objects**

**Status:** review
**Milestone:** 4.7.1
**Created:** Wed Apr 06, 2016 07:19 AM UTC by Hung Nguyen
**Last Updated:** Thu Apr 07, 2016 10:23 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[create_objects.sh](https://sourceforge.net/p/opensaf/tickets/1726/attachment/create_objects.sh)
 (2.3 kB; application/octet-stream)


immcfg from OpenSAF 4.6
root@SC-1:~# time /tmp/immcfg_46 -f /tmp/20k_objects.xml
real0m15.502s
user0m1.480s
sys 0m1.368s

immcfg from OpenSAF 4.7
root@SC-1:~# time immcfg -f /tmp/20k_objects.xml
real0m21.919s
user0m4.976s
sys 0m1.656s

Attached is the script used to generate the xml file.
root@SC-1:~# ./create_objects.sh 2 > /tmp/20k_objects.xml

Related ticket: [#1283]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1170 Support for multiple hot-standby controllers elected to run in different availability zones

2016-04-11 Thread Mathi Naickan

- **labels**: 5.0, #439, #79 --> 5.0, #439, #79, raft
- **status**: assigned --> accepted
- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#1170] Support for multiple hot-standby controllers elected to run 
in different availability zones**

**Status:** accepted
**Milestone:** 5.1.FC
**Labels:** 5.0 #439 #79 raft 
**Created:** Wed Oct 15, 2014 08:37 AM UTC by Mathi Naickan
**Last Updated:** Wed Nov 25, 2015 12:01 PM UTC
**Owner:** Mathi Naickan


The ticket is an extension of https://sourceforge.net/p/opensaf/tickets/79/

To be able to support usecases involving 
a) flexible deployment based on special hardware requirements to deploy for 
more than two system controllers
b) multiple nodes failing simultaneously in virtualized environments (cattles)

 The scope of this ticket is to 
 (a) support multiple hot-standby system controllers
 (b) use RAFT adaptation layer(refer #439) for ACTIVE SC election and to 
perform fencing and arbitration actions
 (c) harden the checkpointing mechanism for maintaining hot standbys - possibly 
use RAFT for maintaining hot standbys!
 
 With tickets #79, #439 in place, this ticket would enable opensaf to be 
flexibly deployed with spares and or multiple standby system controllers.
 
 More details to come.
 A prototyping of multiple-standbys is available at 
https://sourceforge.net/u/praveenmalviya/5.0_prototypes/ci/default/tree/


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #439 Enhanced cluster management

2016-04-11 Thread Mathi Naickan

- **status**: assigned --> accepted
- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#439] Enhanced cluster management**

**Status:** accepted
**Milestone:** 5.1.FC
**Labels:** #79 #1170 
**Created:** Fri May 31, 2013 11:15 AM UTC by Mathi Naickan
**Last Updated:** Wed Nov 25, 2015 12:22 PM UTC
**Owner:** Mathi Naickan


The purpose of this ticket is to achieve the following enhancements to OpenSAF 
cluster management/membership:

- Perform high level node monitoring(heartbeating)
- Enhanced split-brain avoidance techniques.
RAFT is being considered for implementing the above cluster management 
enhancements.
. 
The scope of this ticket includes the following:

(a) Implement RAFT and/or RAFT adaptation layer that provides interfaces for
- adding/removing nodes to the cluster membership
- querying leader
- callbacks notifying about new leader
- read/write interface
- notification of nodes joining/leaving the cluster membership
Note: Yet to be seen if a leader yield interface is necessary

(b) an interface that alows invoking a fencing mechanism

(c) an interface that allows invoking an arbitration mechanism


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1073 --disable-ais-plm does not work on fedora

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#1073] --disable-ais-plm does not work on fedora**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Fri Sep 12, 2014 09:29 PM UTC by Adrian Szwej
**Last Updated:** Mon Nov 02, 2015 11:21 AM UTC
**Owner:** Alex Jones


I am using the following line in two different build targets; (Ubuntu 14 and 
fedora 21).

./configure --enable-imm-pbe --disable-ais-plm --disable-ais-msg 
--disable-ais-lck --disable-ais-evt --disable-rpm-target

The output in both targets indicate PLM is disabled:
  Enable PLM support: no
  Enable TIPC transport: no
  Enable systemd: no

But when build on fedora 21 is finished the 
*/etc/opensaf/nodeinit.conf.controller* contain instruction to start PLMD; 
`/usr/local/lib/opensaf/clc-cli/osaf-plmd:PLMD:S:/usr/local/lib/opensaf/clc-cli/osaf-plmd:6500:4:2:1:start:stop`

Workaround is to sed the file to disable PLMD in order to get opensaf started.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #79 Support for spare system controllers - 2N + spare SCs

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.0.RC2



---

** [tickets:#79] Support for spare system controllers - 2N + spare SCs**

**Status:** review
**Milestone:** 5.0.RC2
**Labels:** #439 #1170 
**Created:** Mon May 13, 2013 04:33 AM UTC by Nagendra Kumar
**Last Updated:** Thu Apr 07, 2016 03:10 PM UTC
**Owner:** Anders Widell
**Attachments:**

- [Support for Spare System Controllers in 
OpenSAF.odt](https://sourceforge.net/p/opensaf/tickets/79/attachment/Support%20for%20Spare%20System%20Controllers%20in%20OpenSAF.odt)
 (70.9 kB; application/vnd.oasis.opendocument.text)
- 
[spare_sc.diff](https://sourceforge.net/p/opensaf/tickets/79/attachment/spare_sc.diff)
 (116.6 kB; text/x-patch)
- 
[spare_sc_uml_test.diff](https://sourceforge.net/p/opensaf/tickets/79/attachment/spare_sc_uml_test.diff)
 (2.6 kB; text/x-patch)


Migrated from http://devel.opensaf.org/ticket/2101

This ticket and subsequent ticket 
https://sourceforge.net/p/opensaf/tickets/1170/ is to support
the following two use scenarios
a) flexible deployment based on special hardware requirements for more than two 
system controllers
b) multiple nodes failing simultaneously in a cattle-type of deployment

The following is the scope of this ticket:

* It will be possible to configure nodes termed as spares (to the system 
controller group of nodes).
* If one of the system controller nodes dies, another "spare" system contoller 
node (if there is any available) will be get an assignment (active / standby). 
This assignment happens without requiring the spare system controller node to 
reboot.

We can add support for configuring more than two system controllers. One node 
will get an active assignment, another node will get a standby assignment, and 
the rest of the system controller nodes will have no assignment for their 
OpenSAF 2N SUs (they will be "spares").

For locking/unlocking the middleware 2N SU, refer the patch floated for 
http://devel.opensaf.org/ticket/2023

Ticket #1170 will be supported subsequent to this ticket.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #475 osaf: update daemon start scripts to support debug tools

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> future



---

** [tickets:#475] osaf: update daemon start scripts to support debug tools**

**Status:** accepted
**Milestone:** future
**Created:** Tue Jun 25, 2013 12:37 PM UTC by Anders Widell
**Last Updated:** Mon Nov 02, 2015 11:22 AM UTC
**Owner:** Anders Widell


Migrated from 

During test when running the NTF daemon under valgrind some problems where 
found in the start script also. For the killproc command the name of the binary 
executable must have the same name as the linux link /proc//exe. For 
valgrind this is a problem since valgrind is doing exec() according to the 
choice of tool provided by the args and that name will always differ from the 
original started binary name.

Goal for this ticket is to deliver scripts and conf files for osaflogd, 
osafntfd, osafamfxd and osafimmxd where it is easy to start a debug mode for 
valgrind or some other tool.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #751 pyosaf: fix bad pylint rating

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> future



---

** [tickets:#751] pyosaf: fix bad pylint rating**

**Status:** accepted
**Milestone:** future
**Created:** Tue Jan 28, 2014 12:17 PM UTC by Hans Feldt
**Last Updated:** Mon Nov 02, 2015 11:22 AM UTC
**Owner:** Hans Nordebäck


pyosaf is still not in production quality. When pylint is run it reports many 
problems. In order to create the next level "pythonic" API we need to have a 
good base.

The modules should be clean pep8 style and we should aim for a pylint rating of 
9 or higher.

The modules should be fixed in prio order:
1) imm
2) ntf
3) log
4) amf




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #777 base: Add more glibc wrapper functions with error handling

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> future



---

** [tickets:#777] base: Add more glibc wrapper functions with error handling**

**Status:** accepted
**Milestone:** future
**Created:** Mon Feb 10, 2014 02:20 PM UTC by Anders Widell
**Last Updated:** Mon Feb 29, 2016 12:43 PM UTC
**Owner:** Anders Widell


This is a generic ticket for adding more convenience/utility functions to BASE.

The generic strategy is to add utility functions with the same name as the 
corresponding glibc function, but with an osaf_ prefix. The utility functions 
will have the following added value:

* For errno == EINTR, it will try the function again in a loop (only in the 
case if EINTR is a possible result of the function according the the manual 
page). Also note the important exception that the close() function shall NOT 
have a loop when it returns EINTR (it's a fairly common mistake to implement 
such a loop for close()).
* For errors that can only happen due to a bug in the program itself (e.g. 
EFAULT, EINVAL, EBADF, EMFILE etc), call osaf_abort() to generate a core dump.
* For out-of-system-resources errors (ENOMEM, ENFILE etc), typically log a 
message and terminate the process. We should not generate a core-dump, since 
it's (probably) not a bug in the process itself (of course it could be, if it 
is the one leaking memory). Still there is not much we can do if the system has 
run out of memory or file descriptors so all we can do is exit.
* For run-time erros that can happen and do not necessarily mean there is a bug 
(ECONNREFUSED, ENETUNREACH, ETIMEDOUT etc), typically log the error and return 
-1 to let the caller handle the error. Logging in this case should be done with 
care, if it is something that can happen often. One possibility is to only log 
into a ring-buffer in the process' own memory, that can be inspected in a core 
dump. Or we could have some kind of suppression mechanism to avoid filling up 
the log files.

By using such utility functions, the program code can be made simpler. We don't 
need to have loops checking for EINTR everywhere, and in many cases these 
wrapper functions can be made so that they can never fail (meaning that the 
process is terminated in such a case, and the function doesn't return to the 
caller).


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1242 LOG: Incorrect error return in filehandling function

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> future



---

** [tickets:#1242] LOG: Incorrect error return in filehandling function**

**Status:** accepted
**Milestone:** future
**Created:** Wed Jan 21, 2015 04:06 PM UTC by elunlen
**Last Updated:** Sun Nov 01, 2015 09:36 PM UTC
**Owner:** elunlen


Function log_stream_config_change() in file lgs_stream.c always return error if 
called in mode create_files_f = false


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1218 Incorporate SAM command line tool into opensaf repository

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#1218] Incorporate SAM command line tool into opensaf repository**

**Status:** accepted
**Milestone:** 5.1.FC
**Labels:** command line tool easy integration for the new user 
**Created:** Wed Nov 19, 2014 09:56 AM UTC by Mathi Naickan
**Last Updated:** Sun Nov 01, 2015 09:36 PM UTC
**Owner:** Mathi Naickan


HansFeldt had named and created the prototype for the 'SAM' tool under the 
opensaf-tools repository within the project.

One functionality originally planned is available today as a prototype and it 
helps the enduser with some simple commands to integrate an application to 
OpenSAF.

SAM can be used in the bigger goal for OpenSAF to come up with a full fledged 
CLI that would hide any strenous SAF terminology and provides a minimal set of 
commands to configure, deploy and monitor their application in OpenSAF.

This ticket is a placeholder to move the SAM tool protoype from the 
opensaf-tools repo to the opensaf main repo and to continue reusing and adding 
stuff.
The opensaf-tools also contain the 'imm-om' python package which helps with a 
lot of utility(IMM iterators, CCB helpers) for imm access.

For eg:- "
from pyosaf.immom import SearchIterator
for obj in SearchIterator():
 print obj.dn
"

Example of how the subset CLI commands can be used are as below:
# create program/software related entities
./amf-cstype create demo1-svc ATTR1
./amf-cstype create demo2-svc ATTR2
./amf-comptype create --saaware --osaf-cmd /opt/amf_demo/amf_demo_script demo1
./amf-comptype create --saaware --osaf-cmd /opt/amf_demo/amf_demo_script demo2
./amf-comptype provides -c one-active-or-one-standby demo1 demo1-svc
./amf-comptype provides -c one-active-or-one-standby demo2 demo2-svc

# service composition
./amf-svctype create demo-svc
./amf-svctype provides demo-svc demo1-svc demo2-svc

# query
./amf-comptype list
./amf-comptype list demo1
./amf-cstype list
./amf-cstype list demo2-svc
./amf-svctype list
./amf-svctype list demo-svc

immfind | grep demo

# cleanup
./amf-svctype delete demo-svc
./amf-comptype delete demo1 demo2
./amf-cstype delete demo1-svc demo2-svc



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1553 AMF: Send CsiSetCallback immediately when CSI attributes are modified (loadbalancing, VM migration usecases)

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#1553] AMF: Send CsiSetCallback immediately when CSI attributes are 
modified (loadbalancing, VM migration usecases)**

**Status:** accepted
**Milestone:** 5.1.FC
**Labels:** VM migration loadbalancer-synchronization 
**Created:** Wed Oct 21, 2015 10:03 AM UTC by Mathi Naickan
**Last Updated:** Mon Mar 21, 2016 09:47 AM UTC
**Owner:** Praveen


AMF is the 'workload' manager in OpenSAF. There are also loadbalancers external 
to OpenSAF that can choose to modify some attributes of an application 
component's workload which is currently assigned ACTIVE (without loss of 
service). In such scenarios it is possible (and necessary) for both AMF and the 
external load balancers to throttle each other. The reverse throttling(from AMF 
to the external load balancer) is possible based on any changes to the 
NodeCapacity limitations set in AMF, but that is for later/future 
considerations.

For eg:- Suppose an application component (say modelled in n-way active) is 
currently serving traffic originating from a source/target X, based on some 
network criteria the load balancer can choose to re-configure/modify that 
application to serve traffic from a different source/target Y. Such change in 
information related to that workload could be communicated to that application 
component at runtime without loss of service.

The above scenario is achieved if the admin (or a loadbalancer) modifies the 
attributes of a workload i.e. csiattribute name-value pair, and then the 
altered name-value information is communicated to that application or 
associated application components 'immediately' instead of waiting for the next 
admin operation!

Today AMF supports modifying csi attribute name-value without requiring that SI 
to be locked. But the modified attributes are sent only after a subsequent 
admin operation. This ticket is intended to evaluate and support sending 
CSIsetcallback (with the same CSI state information but modified csi 
attributes) immediately.

Implementation scope:
1)Upon modification of CSI attribute, AMF will send a CSI Set callback to the 
component (to which corresponding CSI is assigned) with same HA state. Callback 
will contain list of all configured csiattribute name-value pairs (not only the 
changed one). If CSI is not assigned, then no callback will be issued.
Note: AMF spec does not talk about reinvocation of CSI set callback in the 
context of csi-attribute modification. But reinvocation of calback with same HA 
state information is discussed in case like failure handing in N-Way model  AMF 
B.04.01 "3.6.4.5 Failure Handling " page 167.
2)All characteristics associated with a CSI SET callback will be applicable 
with respect to invocation of callback like waiting response from component via 
saAmfResponse() API and generation of error report if component does not 
respond within the configured callbacktimeout.
3)Feature will be configurable either through amfd.conf or via some attribute 
in CSI. It means if the feature is enabled then only AMF will invoke callback 
on component. If feature is disabled then existing behaviour will continue 
which means change will come into effect via lock/unlock of SI and other 
similar means involving reassignment of SI.
4) Although  CLC-CLI commands are idempotents as per spec, modification of CSI 
attribture for a NPI component will not lead to re-execution of INSTANTIATE 
command for a NPI component. For such a component existing behavior will 
continue.
5)Since all middleware components are sa-aware, this feature will be supported 
for MW services also.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1572 smf: Node by node upgrade

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.1.FC



---

** [tickets:#1572] smf: Node by node upgrade**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Wed Oct 28, 2015 06:44 AM UTC by Ingvar Bergström
**Last Updated:** Sun Nov 01, 2015 09:36 PM UTC
**Owner:** Rafael


The puropse of this ticket is to decrease campaign execution time, without 
rewriting the campaign.

If configured, smfd will automatically upgrade the nodes one by one in a 
rolling manner, with actions fetched from all rolling procedures in the 
campaign.xml.

This will prevent the campaigns different procedures to roll over one and the 
same node/nodes several times i.e. a node will never be 
locked/unlocked/rebooted more than once.

The procedures are not allowed to have order dependencies to each other.

Single step procedures are leaved "as is" and executed before the new "node by 
node" procedure.

This is the second step in a three step upgrade time improvement plan.
1) One step upgrade. Delivered with ticket #1401 in OpenSAF 4.7
2) Node by node upgrade. This ticket.
3) TBD, Upgrade several nodes at a time in a rolling manner


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1613 Remove limitation of max 255 nodes in the cluster

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.0.RC2



---

** [tickets:#1613] Remove limitation of max 255 nodes in the cluster**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Fri Nov 27, 2015 08:36 AM UTC by Anders Widell
**Last Updated:** Mon Apr 04, 2016 06:28 PM UTC
**Owner:** Anders Widell
**Attachments:**

- 
[4095nodes_prototype.diff](https://sourceforge.net/p/opensaf/tickets/1613/attachment/4095nodes_prototype.diff)
 (10.8 kB; text/x-patch)


Currently, OpenSAF imposes a limit of max 255 nodes in the same cluster due to 
the use of 8 bits for representing the slot id. However, TIPC supports up to 
4095 nodes on the same network. The proposal is that OpenSAF should also 
support up to 4095 nodes, by using the 4 bits in the subslot id in addition to 
the 8 bits in the slot id. This extension can be made in a backwards compatible 
way without affecting existing installations of OpenSAF.

A proof-of-concept prototype is attached to the ticket.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1688 log: update PR document for node originator

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.0.RC2



---

** [tickets:#1688] log: update PR document for node originator**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Fri Mar 04, 2016 07:45 AM UTC by Vu Minh Nguyen
**Last Updated:** Tue Mar 29, 2016 08:47 AM UTC
**Owner:** Vu Minh Nguyen


Update the PR document regarding node originator ticket [#1480].


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1707 NTF: Update PR doc for cloud resilience

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.FC --> 5.0.RC2



---

** [tickets:#1707] NTF: Update PR doc for cloud resilience**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Mon Mar 21, 2016 05:10 AM UTC by Minh Hon Chau
**Last Updated:** Wed Apr 06, 2016 06:32 AM UTC
**Owner:** Minh Hon Chau


Update the PR document with changes from cloud resilience [#1180].


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1717 amf: when second controller is down opensafd status is not showing correctly

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1717] amf: when second controller is down opensafd status is not 
showing correctly**

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Tue Apr 05, 2016 12:58 PM UTC by Neelakanta Reddy
**Last Updated:** Tue Apr 05, 2016 12:58 PM UTC
**Owner:** nobody


Build: 5.0 FC
Procedure:
1) Bring two controllers UP
2) stop the cluster in SC-2
3) Opensafd status is still showin SC-2 NoRED as Up

SC1:~ # /etc/init.d/opensafd status
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1718 AMF: ProtectionGroup Start/Stop should return TRY_AGAIN while headless

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1718] AMF: ProtectionGroup Start/Stop should return TRY_AGAIN 
while headless**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 12:52 AM UTC by Minh Hon Chau
**Last Updated:** Fri Apr 08, 2016 01:53 AM UTC
**Owner:** Gary Lee


The API saAmfProtectionGroupTrack and saAmfProtectionGroupTrackStop should 
return TRY_AGAIN while cluster is in headless, since AMFD updates the changes 
on protection group.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1720 AMF: RT attribute values are read as dummy after headless

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1720] AMF: RT attribute values are read as dummy after headless**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 01:02 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 07, 2016 01:49 AM UTC
**Owner:** Minh Hon Chau


After headless, some of RTA values are retrieved as dummy at the time AMFD 
initiate role.
The reason is these RTA are read before AMFD set itself as implementer.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1719 AMF: ProtectionGroup info lost after headless

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1719] AMF: ProtectionGroup info lost after headless**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 12:55 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 07, 2016 01:36 AM UTC
**Owner:** Minh Hon Chau


After cluster is back from headless, protection group information currently is 
lost so there will be not track callback issued to component. Amfnd needs to 
resend these protection group information to amfd after headless


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1721 AMF: Lock-in healthy SU set SU's Oper state as DISABLED

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1721] AMF: Lock-in healthy SU set SU's Oper state as DISABLED**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 01:08 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 07, 2016 01:49 PM UTC
**Owner:** Minh Hon Chau


If lock-in SU currently amfnd set SU Oper's state as DISABLED. It seems not to 
be a right setting since SU has been *healthy* state. The problem only exposes 
when SC recovers from headless, amfnd will report locked-in SU with its 
Operstate as DISABLED.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1722 AMF: Downgrade severity of logging in case data_update from absent amfnd

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1722] AMF: Downgrade severity of logging in case data_update from 
absent amfnd**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 01:23 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 07, 2016 01:53 PM UTC
**Owner:** Minh Hon Chau


While amfd is performing *sync* with all amfnd(s), there should be component/su 
error (for instance a restart error) occuring during sync period. Amfnd(s) 
sends data_update msg(s) to increase the error counter. These data_update will 
be ignored at amfd since amfnd is still absent due to on-going sync. Amfnd(s) 
will resend these update messages after sync completes.



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1725 AMF: Recover transient SUSIs left over from headless

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1725] AMF: Recover transient SUSIs left over from headless**

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau
**Last Updated:** Thu Apr 07, 2016 01:54 PM UTC
**Owner:** nobody


This ticket is more likely an enhancement that targets on how AMFD detect and 
recover the transients SUSI left over from headless. There are three major 
situations:
(1) - Cluster goes headless, su/node failover on any payloads can happen, then 
cluster recover
(2) - issue admin op on any AMF entities, cluster goes headless. During 
headless, the middle HA assignments of whole admin op sequence between AMFND 
and components could be:
(2.1) The assignment completes, component returns OK with csi callback, 
then cluster recover
(2.2) The assignment is under going, then cluster recover. The assignment 
afterward could complete, or csi callback returns FAILED_OPERATION or error can 
also happen

At the time cluster recover, amfd has collected all assignments from all 
amfnd(s). These assignments can be in assigned or assigning states whilst its 
HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen 
in a combination, which means while issuing admin op (2), cluster go headless 
and any kinds of failover (1) can happen during headless.  



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1723 amf: send extra state information from nd to d after headless state

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1723] amf: send extra state information from nd to d after 
headless state**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 01:52 AM UTC by Gary Lee
**Last Updated:** Thu Apr 07, 2016 03:30 AM UTC
**Owner:** Gary Lee


To fully recover after a headless state, the AMF director needs to know the 
current assignment state of each SUSI on the payloads. Currently, it is assumed 
to be in the assigned state which is incorrect. This scope of this ticket is to 
make this information available at the director. Further changes are required 
to handle the various assignment states.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1727 immtools: immutil for saImmOmCcbObjectRead() is missing

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1727] immtools: immutil for saImmOmCcbObjectRead() is missing**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 07:28 AM UTC by Hung Nguyen
**Last Updated:** Wed Apr 06, 2016 10:57 AM UTC
**Owner:** Hung Nguyen


immutil for saImmOmCcbObjectRead() is missing.

it should be added to
osaf/tools/safimm/src/immutil.c
samples/immsv/immutils/immutil.c


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1732 OUT_OF_SYNC (failed over) new active controller should go for immediate reboot

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1732] OUT_OF_SYNC (failed over) new active controller should go 
for immediate reboot**

**Status:** review
**Milestone:** 5.0.RC2
**Created:** Wed Apr 06, 2016 11:02 AM UTC by Srikanth R
**Last Updated:** Thu Apr 07, 2016 10:46 AM UTC
**Owner:** nobody


Changeset : 7436 
Version : 5.0 FC
Setup : Two controllers


Issue :
  Out of sync (failed over) new active controller should go for immediate 
reboot,
  
  During failover, if the standby controller is OUT OF SYNC and could not get 
promoted to active, the node should be rebooted immediately.
 
Apr  6 16:03:53 CONTROLLER-2 osafamfd[431]: ER FAILOVER StandBy --> Active 
FAILED, Standby OUT OF SYNC
Apr  6 16:03:53 CONTROLLER-2 osafamfd[431]: ER avd_role_change role change 
failure
Apr  6 16:03:53 CONTROLLER-2 osafimmd[380]: WA IMMND DOWN on active controller 
1 detected at standby immd!! 2. Possible failover
..
Apr  6 16:06:53 CONTROLLER-2 osafamfnd[441]: WA AMF director unexpectedly 
crashed
Apr  6 16:06:53 CONTROLLER-2 osafamfnd[441]: Rebooting OpenSAF NodeId = 131599 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received, 
OwnNodeId = 131599, SupervisionTime = 60
Apr  6 16:06:53 CONTROLLER-2 opensaf_reboot: Rebooting local node; timeout=60

This issue is fixed as part of  #1334, but might be observed because of #79


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1742 amfd: reject admin ops during headless recovery

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1742] amfd: reject admin ops during headless recovery**

**Status:** accepted
**Milestone:** 5.0.RC2
**Created:** Fri Apr 08, 2016 01:48 AM UTC by Gary Lee
**Last Updated:** Fri Apr 08, 2016 01:49 AM UTC
**Owner:** Gary Lee


During the headless recovery period (waiting for node_ups from payloads / 
adjusting assignments), admin ops should be rejected.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1736 immd: IMMSV PR update

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1736] immd: IMMSV PR update**

**Status:** accepted
**Milestone:** 5.0.RC2
**Created:** Thu Apr 07, 2016 06:01 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Apr 07, 2016 06:01 AM UTC
**Owner:** Neelakanta Reddy


This defect is to update IMMSV_PR for 5.0 release.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1745 ntf: Trefine error category messages in syslog. Related to #1639

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1745] ntf: Trefine error category messages in syslog. Related to 
#1639**

**Status:** accepted
**Milestone:** 5.0.RC2
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:52 PM UTC
**Owner:** Praveen


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1745 ntf: Trefine error category messages in syslog. Related to #1639

2016-04-11 Thread Mathi Naickan

- **summary**: ntf: Too many ER messages in syslog. Related to #1639 --> ntf: 
Trefine error category messages in syslog. Related to #1639



---

** [tickets:#1745] ntf: Trefine error category messages in syslog. Related to 
#1639**

**Status:** accepted
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 09:54 AM UTC
**Owner:** Praveen


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1746 clm: logging category related to lock of active node needs consideration. Related to #1639

2016-04-11 Thread Mathi Naickan

- **Type**: defect --> discussion
- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1746] clm: logging category related to lock of active node needs 
consideration. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Mon Apr 11, 2016 08:39 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:47 PM UTC
**Owner:** nobody


See ticket [#1745]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1747 IMMND trying to start PBE process while stopping OpenSAF services

2016-04-11 Thread Mathi Naickan

- **Milestone**: 5.0.RC1 --> 5.0.RC2



---

** [tickets:#1747] IMMND trying to start PBE process while stopping OpenSAF 
services**

**Status:** unassigned
**Milestone:** 5.0.RC2
**Created:** Mon Apr 11, 2016 10:30 AM UTC by Chani Srivastava
**Last Updated:** Mon Apr 11, 2016 10:39 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0
1-PBE enabled
Issue is not observed always.

Apr 11 13:32:52 OSAF-SC1 opensafd: Stopping OpenSAF Services
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Shutdown initiated
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Terminating all AMF components
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db 
handle
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: IN IMM PBE process EXITING...
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 18 <545, 2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 18 <545, 
2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: WA Persistent back-end process has 
apparently died.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO STARTING PBE process.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO 
pbe-db-file-path:/home/chani/immPBE/imm.db VETERAN:1 B:0
Apr 11 13:32:53 OSAF-SC1 osafckptnd[30049]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfd[29976]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflckd[30057]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2412 <321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 2412 
<321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osaflcknd[30032]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafclmna[29860]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmd[29888]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaffmd[29878]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafrded[29869]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafevtd[30088]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2413 <315, 2010f> (safEvtService)
Apr 11 13:32:53 OSAF-SC1 osafckptd[30097]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2411 <330, 2010f> (safCheckPointService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgd[30011]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgnd[29995]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfnd[29978]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflogd[29914]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafntfimcnd[5780]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Apr 11 13:32:53 OSAF-SC1 osafclmd[29940]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[0] == 
'/usr/lib64/opensaf/osafimmpbed'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[1] == '--recover'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[2] == '--pbe'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[3] == '/home/chani/immPBE/imm.db'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: ER osafimmpbe is not started by osafimmnd



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1746 clm: logging category related to lock of active node needs consideration. Related to #1639

2016-04-11 Thread Mathi Naickan

- **summary**: clm: Too many ER messages in syslog. Related to #1639 --> clm: 
logging category related to lock of active node needs consideration. Related to 
#1639



---

** [tickets:#1746] clm: logging category related to lock of active node needs 
consideration. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:39 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:46 PM UTC
**Owner:** nobody


See ticket [#1745]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1746 clm: Too many ER messages in syslog. Related to #1639

2016-04-11 Thread Mathi Naickan

- **Priority**: major --> minor



---

** [tickets:#1746] clm: Too many ER messages in syslog. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:39 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:41 AM UTC
**Owner:** nobody


See ticket [#1745]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1731 ntf: Deadlock with CLM

2016-04-11 Thread Praveen

- **status**: review --> fixed
- **Comment**:

changeset:   7471:0396db09eb4a
branch:  opensaf-5.0.x
parent:  7469:5dd5e2cc679f
user:praveen.malv...@oracle.com
date:Mon Apr 11 19:01:04 2016 +0530
summary: ntfs: init with CLM in a separate thread to avoid deadlock 
situation[#1731]

changeset:   7472:17f1193a61df
tag: tip
parent:  7470:4c6ce577476a
user:praveen.malv...@oracle.com
date:Mon Apr 11 19:01:24 2016 +0530
summary: ntfs: init with CLM in a separate thread to avoid deadlock 
situation[#1731]





---

** [tickets:#1731] ntf: Deadlock with CLM**

**Status:** fixed
**Milestone:** 5.0.RC1
**Created:** Wed Apr 06, 2016 10:34 AM UTC by Anders Widell
**Last Updated:** Wed Apr 06, 2016 12:48 PM UTC
**Owner:** Praveen


There is a possibility for a deadlock between NTF and CLM during startup, if 
NTF is calling saClmInitialize() at exactly the same time as CLM is calling 
saNtfNotificationSend().


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1690 imm: update documentation with new enhancements

2016-04-11 Thread Zoran Milinkovic

- **status**: review --> fixed
- **Comment**:

opensaf-5.0.x:

changeset:   7469:5dd5e2cc679f
branch:  opensaf-5.0.x
user:Zoran Milinkovic 
date:Mon Apr 11 15:17:38 2016 +0200
summary: imm: update README with IMM enhancements for OpenSAF 5.0 [#1690]

-

default(5.1):

changeset:   7470:4c6ce577476a
tag: tip
parent:  7467:ce2960949e60
user:Zoran Milinkovic 
date:Mon Apr 11 15:17:38 2016 +0200
summary: imm: update README with IMM enhancements for OpenSAF 5.0 [#1690]



---

** [tickets:#1690] imm: update documentation with new enhancements**

**Status:** fixed
**Milestone:** 5.0.FC
**Created:** Fri Mar 04, 2016 12:40 PM UTC by Zoran Milinkovic
**Last Updated:** Thu Apr 07, 2016 01:03 PM UTC
**Owner:** nobody


Documentation needs to be updated with the new IMM enhancements


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1738 ClmTrack stop failed error message observed in the syslog during switchover

2016-04-11 Thread Ritu Raj

log files of Active and Standby controller attached.


Attachments:

- 
[1738-logs.tar.bz2](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e66384cf/04f3/attachment/1738-logs.tar.bz2)
 (1.5 MB; application/x-bzip)


---

** [tickets:#1738] ClmTrack stop failed error message observed in the syslog 
during switchover **

**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Thu Apr 07, 2016 08:55 AM UTC by Ritu Raj
**Last Updated:** Mon Apr 11, 2016 07:30 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0
4 nodes configured with single PBE and a load of 30K objects

Steps performed:
During switchover, on the quiesced controller  the error  message "Failed to 
stop cluster tracking" is observed in the syslog

Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: NO ROLE SWITCH Active --> 
Quiesced
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer (applier) 
connected: 9499 (@OpenSafImmReplicatorA) <13773, 2010f>
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafntfimcnd[17992]: NO Started
**Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: ER Failed to stop cluster 
tracking 12
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: ER ClmTrack stop failed**
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafrded[6108]: NO RDE role set to QUIESCED
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer (applier) 
connected: 9500 (@OpenSafImmReplicatorB) <0, 2020f>
Apr  7 04:12:43 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer disconnected 
9490 <26, 2010f> (safAmfService)





---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1728 amfnd: message ID mismatch causing node reboot

2016-04-11 Thread Nagendra Kumar

- **status**: review --> fixed
- **Comment**:

changeset:   7466:71b86f3732ba
branch:  opensaf-5.0.x
user:Nagendra Kumar
date:Mon Apr 11 17:13:25 2016 +0530
summary: amfnd: remove receive message id counter from threads  [#1728]

changeset:   7467:ce2960949e60
tag: tip
parent:  7462:0f5b04d5f67e
user:Nagendra Kumar
date:Mon Apr 11 17:35:25 2016 +0530
summary: amfnd: remove receive message id counter from threads  [#1728]

[staging:71b86f]
[staging:ce2960]




---

** [tickets:#1728] amfnd: message ID mismatch causing node reboot**

**Status:** fixed
**Milestone:** 5.0.RC1
**Created:** Wed Apr 06, 2016 08:39 AM UTC by Gary Lee
**Last Updated:** Mon Apr 11, 2016 11:52 AM UTC
**Owner:** Nagendra Kumar


"Message ID mismatch, rec %u, expected %u" can sometimes be seen on a node.

This seems to be caused by the addition of the IMM reader thread.

In various message handlers, rcv_msg_id is recorded:

avnd_msgid_assert(info->msg_id);
cb->rcv_msg_id = info->msg_id;

But now we potentially have the main thread and IMM reader thread updating this 
concurrently.

The update of rcv_msg_id should possibly be done in a single thread. Eg. in 
avnd_mds_rcv() when a message is received from AMFD.



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1728 amfnd: message ID mismatch causing node reboot

2016-04-11 Thread Nagendra Kumar

- **status**: accepted --> review



---

** [tickets:#1728] amfnd: message ID mismatch causing node reboot**

**Status:** review
**Milestone:** 5.0.RC1
**Created:** Wed Apr 06, 2016 08:39 AM UTC by Gary Lee
**Last Updated:** Thu Apr 07, 2016 05:17 AM UTC
**Owner:** Nagendra Kumar


"Message ID mismatch, rec %u, expected %u" can sometimes be seen on a node.

This seems to be caused by the addition of the IMM reader thread.

In various message handlers, rcv_msg_id is recorded:

avnd_msgid_assert(info->msg_id);
cb->rcv_msg_id = info->msg_id;

But now we potentially have the main thread and IMM reader thread updating this 
concurrently.

The update of rcv_msg_id should possibly be done in a single thread. Eg. in 
avnd_mds_rcv() when a message is received from AMFD.



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls

2016-04-11 Thread Ritu Raj

The above sequence was done in one process
osaflogd trace and Agent log file attached.

Please, note that even same handle is also obtained in saLogInitialize()


Attachments:

- 
[logsv.trace](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e863d596/d2cd/attachment/logsv.trace)
 (49.8 kB; application/octet-stream)
- 
[osaflogd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e863d596/d2cd/attachment/osaflogd)
 (973.1 kB; application/octet-stream)


---

** [tickets:#1739] Logsv is providing same active handle value for different 
api calls**

**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj
**Last Updated:** Fri Apr 08, 2016 07:30 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0

Issue :
  Logsv is issuing same active handle value for different api calls

Steps:
 -> The logsv application stores the global system stream handle and for couple 
of scenarios , initialization and finalization has been done.
 
 -> At the startup of the application, system stream handle (4288675841) is 
obtained.
 
 -> After couple of flows, the initialization api saLogInitialize() obtained 
same handle ( 4288675841) and was finalized.
 
 ->  So when saLogWriteLogAsync()  api is invoked  with the earlier obtained 
system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE.  Note that the 
init  handle  associated with the system stream handle 4288675841  is not 
finalized.


100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4290772993
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4287627265
100|0|Invoking saLogStreamOpen_2()
100|0|Handle used is 4290772993
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4286578689
100|0|system stream handle  4288675841
...
100|0|Invoking saLogInitialize()
100|0| Return value : <-- SA_AIS_OK
100|0|  Handle obtained is 4288675841
100|0|Invoking saLogFinalize()
100|0|  Handle used is 4288675841
100|0| Return value : <-- SA_AIS_OK
100|0|Invoking saLogSelectionObjectGet()
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE

100|0|Invoking saLogWriteLogAsync()
100|0|Handle used is 4288675841
100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE
100|0|saLogWriteLogAsync return values did not match Actual_Value :9  
Expected_Value :1

 This application used to work with 4.7


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1715 imm: change log priority for error message "Late detection of other SC up"

2016-04-11 Thread Zoran Milinkovic

- **status**: review --> fixed
- **Comment**:

opensaf-4.6.x:

changeset:   7463:2b578deadae2
branch:  opensaf-4.6.x
parent:  7456:acf5f6702baa
user:Zoran Milinkovic 
date:Tue Apr 05 12:53:58 2016 +0200
summary: imm: change log priority to warning for log message 'Late 
detection of other SC up' [#1715]

-

opensaf-4.7.x:

changeset:   7464:f7a399227229
branch:  opensaf-4.7.x
parent:  7458:f4b12405d979
user:Zoran Milinkovic 
date:Tue Apr 05 12:53:58 2016 +0200
summary: imm: change log priority to warning for log message 'Late 
detection of other SC up' [#1715]

-

opensaf-5.0.x:

changeset:   7465:82d3db26958e
branch:  opensaf-5.0.x
tag: tip
parent:  7460:1422f9a6c18f
user:Zoran Milinkovic 
date:Tue Apr 05 12:53:58 2016 +0200
summary: imm: change log priority to warning for log message 'Late 
detection of other SC up' [#1715]

-

default(5.1):

changeset:   7454:d7f4957db2c3
user:Zoran Milinkovic 
date:Tue Apr 05 12:53:58 2016 +0200
summary: imm: change log priority to warning for log message 'Late 
detection of other SC up' [#1715]



---

** [tickets:#1715] imm: change log priority for error message "Late detection 
of other SC up"**

**Status:** fixed
**Milestone:** 4.6.2
**Created:** Tue Apr 05, 2016 08:55 AM UTC by Zoran Milinkovic
**Last Updated:** Wed Apr 06, 2016 08:52 AM UTC
**Owner:** Zoran Milinkovic


Apr  4 18:15:07 SC-2-2 osafimmnd[4107]: NO PBE-OI established on other SC. 
Dumping incrementally to file imm.db
Apr  4 18:15:07 SC-2-2 osafimmnd[4107]: ER Late detection of other SC up

After reporting the error message, IMMND silently ignore the message and 
continues to work correctly.
The only case that IMMND crashes after the error message is if IMM is running 
in 1safePBE mode.

The log priority can be changed to warning instead of error.


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1743 osaf: Build fails with GCC version 6

2016-04-11 Thread Anders Widell

- **status**: review --> fixed
- **Comment**:

changeset:   7455:378dc641beaf
branch:  opensaf-4.6.x
parent:  7447:8f0b8473b8fc
user:Anders Widell 
date:Mon Apr 11 13:07:12 2016 +0200
summary: immtools: Correct code indentation [#1743]

changeset:   7456:acf5f6702baa
branch:  opensaf-4.6.x
user:Anders Widell 
date:Mon Apr 11 13:07:19 2016 +0200
summary: immtest: Remove dead code [#1743]

changeset:   7457:43ceee49a385
branch:  opensaf-4.7.x
parent:  7448:7daa5fdf557c
user:Anders Widell 
date:Mon Apr 11 13:07:38 2016 +0200
summary: immtools: Correct code indentation [#1743]

changeset:   7458:f4b12405d979
branch:  opensaf-4.7.x
user:Anders Widell 
date:Mon Apr 11 13:07:19 2016 +0200
summary: immtest: Remove dead code [#1743]

changeset:   7459:4b926e9740be
branch:  opensaf-5.0.x
parent:  7450:1f9920a8958b
user:Anders Widell 
date:Mon Apr 11 13:07:38 2016 +0200
summary: immtools: Correct code indentation [#1743]

changeset:   7460:1422f9a6c18f
branch:  opensaf-5.0.x
user:Anders Widell 
date:Mon Apr 11 13:07:19 2016 +0200
summary: immtest: Remove dead code [#1743]

changeset:   7461:75d65721f4c5
parent:  7454:d7f4957db2c3
user:Anders Widell 
date:Mon Apr 11 13:07:38 2016 +0200
summary: immtools: Correct code indentation [#1743]

changeset:   7462:0f5b04d5f67e
user:Anders Widell 
date:Mon Apr 11 13:07:19 2016 +0200
summary: immtest: Remove dead code [#1743]

[staging:378dc6]
[staging:acf5f6]
[staging:43ceee]
[staging:f4b124]
[staging:4b926e]
[staging:1422f9]
[staging:75d657]
[staging:0f5b04]




---

** [tickets:#1743] osaf: Build fails with GCC version 6**

**Status:** fixed
**Milestone:** 4.6.2
**Created:** Fri Apr 08, 2016 12:34 PM UTC by Anders Widell
**Last Updated:** Mon Apr 11, 2016 09:02 AM UTC
**Owner:** Anders Widell


The following build errors were observed with GCC version 6 and optimization 
level -O3:


imm_dumper.cc: In function 'int main(int, char**)':
imm_dumper.cc:149:5: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
 if ((c = getopt_long(argc, argv, "hp:x:c:a:", long_options, NULL)) == -1)
 ^~
imm_dumper.cc:152:13: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
 switch (c) {
 ^~




compdb.cc: In function 'int comp_init(AVND_COMP*, const SaImmAttrValuesT_2**)':
compdb.cc:1579:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSISetCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1582:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiSetCallbackTimeout);
   ^~~~
compdb.cc:1584:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSIRmvCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1587:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiRemoveCallbackTimeout);
   ^~~~




tet_Log_recov.c:76:18: error: 'wr_delay' defined but not used 
[-Werror=unused-const-variable=]
 static const int wr_delay = 100*1000; /* 100 ms */
  ^~~~




test_saImmOmCcbObjectCreate_2.c:20:30: error: 'nonExistingClassName' defined 
but not used [-Werror=unused-const-variable=]
 static const SaImmClassNameT nonExistingClassName = (SaImmClassNameT) __FILE__;
  ^~~~




In file included from ../../../../../osaf/libs/core/include/ncs_osprm.h:32:0,
 from ../../../../../osaf/libs/core/include/ncs_ubaid.h:45,
 from ../../../../../osaf/libs/core/include/mbcsv_papi.h:29,
 from lgs.h:30,
 from lgs_stream.cc:29:
../../../../../osaf/libs/core/common/include/logtrace.h: In function 'int 
log_stream_file_close(log_stream_t*)':
../../../../../osaf/libs/core/common/include/logtrace.h:131:46: error: 
'errno_ret' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
 #define LOG_NO(format, args...) _logtrace_log(__FILE__, __LINE__, LOG_NOTICE, 
(format), ##args)
  ^
lgs_stream.cc:978:6: note: 'errno_ret' was declared here
  int errno_ret;
  ^




---

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

[tickets] [opensaf:tickets] #1747 IMMND trying to start PBE process while stopping OpenSAF services

2016-04-11 Thread Chani Srivastava

- Description has changed:

Diff:



--- old
+++ new
@@ -1,6 +1,8 @@
 Setup:
 Changeset- 7436
 Version - opensaf 5.0
+1-PBE enabled
+Issue is not observed always.
 
 Apr 11 13:32:52 OSAF-SC1 opensafd: Stopping OpenSAF Services
 Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Shutdown initiated






---

** [tickets:#1747] IMMND trying to start PBE process while stopping OpenSAF 
services**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 10:30 AM UTC by Chani Srivastava
**Last Updated:** Mon Apr 11, 2016 10:30 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0
1-PBE enabled
Issue is not observed always.

Apr 11 13:32:52 OSAF-SC1 opensafd: Stopping OpenSAF Services
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Shutdown initiated
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Terminating all AMF components
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db 
handle
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: IN IMM PBE process EXITING...
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 18 <545, 2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 18 <545, 
2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: WA Persistent back-end process has 
apparently died.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO STARTING PBE process.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO 
pbe-db-file-path:/home/chani/immPBE/imm.db VETERAN:1 B:0
Apr 11 13:32:53 OSAF-SC1 osafckptnd[30049]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfd[29976]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflckd[30057]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2412 <321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 2412 
<321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osaflcknd[30032]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafclmna[29860]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmd[29888]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaffmd[29878]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafrded[29869]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafevtd[30088]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2413 <315, 2010f> (safEvtService)
Apr 11 13:32:53 OSAF-SC1 osafckptd[30097]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2411 <330, 2010f> (safCheckPointService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgd[30011]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgnd[29995]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfnd[29978]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflogd[29914]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafntfimcnd[5780]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Apr 11 13:32:53 OSAF-SC1 osafclmd[29940]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[0] == 
'/usr/lib64/opensaf/osafimmpbed'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[1] == '--recover'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[2] == '--pbe'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[3] == '/home/chani/immPBE/imm.db'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: ER osafimmpbe is not started by osafimmnd



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1716 imm: immnd is asserting in 2PBE when modify operation is performed

2016-04-11 Thread Neelakanta Reddy

- **status**: review --> fixed
- **Comment**:

changeset:   7453:ec2e4f2e2270
tag: tip
user:Neelakanta Reddy
date:Mon Apr 11 16:02:50 2016 +0530
summary: imm: Remove the assertion when object is modified with 2PBE [#1716]




---

** [tickets:#1716] imm: immnd is asserting in 2PBE when modify operation is 
performed**

**Status:** fixed
**Milestone:** 5.0.RC1
**Created:** Tue Apr 05, 2016 12:55 PM UTC by Neelakanta Reddy
**Last Updated:** Tue Apr 05, 2016 01:11 PM UTC
**Owner:** Neelakanta Reddy


SC2 osafimmnd[20735]: immnd_evt.c:6566: immnd_evt_proc_object_modify: Assertion 
'canonicalizedAttrMod' failed.
SC2 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting
SC2 osafamfnd[20785]: NO 'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' component 
restart probation timer started (timeout: 600 ns)
SC2 osafamfnd[20785]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
SC2 osafamfnd[20785]: NO 'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' 
faulted due to 'avaDown' : Recovery is 'componentRestart'
SC2 osafamfd[20775]: NO Re-initializing with IMM
SC2 osafimmnd[20976]: Started
SC2 osafimmnd[20976]: NO Persistent Back-End capability configured, Pbe 
file:imm.db (suffix may get added)
SC2 osafimmnd[20976]: NO IMMD service is UP ... ScAbsenseAllowed?:0 
introduced?:0



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1747 IMMND trying to start PBE process while stopping OpenSAF services

2016-04-11 Thread Chani Srivastava




---

** [tickets:#1747] IMMND trying to start PBE process while stopping OpenSAF 
services**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 10:30 AM UTC by Chani Srivastava
**Last Updated:** Mon Apr 11, 2016 10:30 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0

Apr 11 13:32:52 OSAF-SC1 opensafd: Stopping OpenSAF Services
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Shutdown initiated
Apr 11 13:32:52 OSAF-SC1 osafamfnd[29960]: NO Terminating all AMF components
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: NO IMM PBE received SIG_TERM, closing db 
handle
Apr 11 13:32:52 OSAF-SC1 osafimmpbed: IN IMM PBE process EXITING...
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 18 <545, 2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 18 <545, 
2010f> (OpenSafImmPBE)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: WA Persistent back-end process has 
apparently died.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO STARTING PBE process.
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO 
pbe-db-file-path:/home/chani/immPBE/imm.db VETERAN:1 B:0
Apr 11 13:32:53 OSAF-SC1 osafckptnd[30049]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfd[29976]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflckd[30057]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2412 <321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer disconnected 2412 
<321, 2010f> (safLckService)
Apr 11 13:32:53 OSAF-SC1 osaflcknd[30032]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafclmna[29860]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmd[29888]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaffmd[29878]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafrded[29869]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafevtd[30088]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2413 <315, 2010f> (safEvtService)
Apr 11 13:32:53 OSAF-SC1 osafckptd[30097]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: NO Implementer locally disconnected. 
Marking it as doomed 2411 <330, 2010f> (safCheckPointService)
Apr 11 13:32:53 OSAF-SC1 osafimmnd[29899]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgd[30011]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafmsgnd[29995]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafsmfnd[29978]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osaflogd[29914]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafntfimcnd[5780]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Apr 11 13:32:53 OSAF-SC1 osafclmd[29940]: exiting for shutdown
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[0] == 
'/usr/lib64/opensaf/osafimmpbed'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[1] == '--recover'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[2] == '--pbe'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: IN arg[3] == '/home/chani/immPBE/imm.db'
Apr 11 13:32:53 OSAF-SC1 osafimmpbed: ER osafimmpbe is not started by osafimmnd



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1620 amf: add support for 'cloud resilience' feature

2016-04-11 Thread Nagendra Kumar

Hi Gary,
   Could you please do the same udpate in Amf PR doc. All the other 
services are following the same thing. The update goes to README and PR doc 
together.

 Thanks
 -Nagu


---

** [tickets:#1620] amf: add support for 'cloud resilience' feature**

**Status:** fixed
**Milestone:** 5.0.FC
**Created:** Mon Dec 07, 2015 07:47 AM UTC by Gary Lee
**Last Updated:** Wed Apr 06, 2016 08:15 AM UTC
**Owner:** Minh Hon Chau
**Attachments:**

- [New TC 
1.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%201.rar)
 (245.9 kB; application/octet-stream)
- [New TC 
2.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%202.rar)
 (268.3 kB; application/octet-stream)
- [New TC 
3.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%203.rar)
 (398.2 kB; application/octet-stream)
- [New TC 
4.a.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%204.a.rar)
 (411.5 kB; application/octet-stream)
- [New TC 
4.b.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%204.b.rar)
 (410.1 kB; application/octet-stream)
- [New TC 
5.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/New%20TC%205.rar)
 (250.1 kB; application/octet-stream)
- [TC 
1.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%201.rar) 
(233.9 kB; application/octet-stream)
- [TC 
2.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%202.rar) 
(243.5 kB; application/octet-stream)
- [TC 
21.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2021.rar) 
(127.3 kB; application/octet-stream)
- [TC 
22.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2022.rar) 
(315.3 kB; application/octet-stream)
- [TC 
24.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2024.rar) 
(250.3 kB; application/octet-stream)
- [TC 
25.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2025.rar) 
(251.6 kB; application/octet-stream)
- [TC 
26.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2026.rar) 
(272.7 kB; application/octet-stream)
- [TC 
27.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2027.rar) 
(238.6 kB; application/octet-stream)
- [TC 
28.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2028.rar) 
(198.3 kB; application/octet-stream)
- [TC 
29.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2029.rar) 
(275.6 kB; application/octet-stream)
- [TC 
30.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2030.rar) 
(265.5 kB; application/octet-stream)
- [TC 
31.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2031.rar) 
(259.4 kB; application/octet-stream)
- [TC 
32.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2032.rar) 
(450.2 kB; application/octet-stream)
- [TC 
33.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2033.rar) 
(246.3 kB; application/octet-stream)
- [TC 
43.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2043.rar) 
(1.1 kB; application/octet-stream)
- [TC 
45.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2045.rar) 
(195.3 kB; application/octet-stream)
- [TC 
46.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2046.rar) 
(248.1 kB; application/octet-stream)
- [TC 
47.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2047.rar) 
(475.1 kB; application/octet-stream)
- [TC 
48.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2048.rar) 
(247.0 kB; application/octet-stream)
- [TC 
49.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2049.rar) 
(236.4 kB; application/octet-stream)
- [TC 
5.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%205.rar) 
(247.4 kB; application/octet-stream)
- [TC 
50.rar](https://sourceforge.net/p/opensaf/tickets/1620/attachment/TC%2050.rar) 
(220.3 kB; application/octet-stream)


amf: add support for 'cloud resilience' feature


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1745 ntf: Too many ER messages in syslog. Related to #1639

2016-04-11 Thread Praveen

- **Version**: 4.7 --> 5.0 FC



---

** [tickets:#1745] ntf: Too many ER messages in syslog. Related to #1639**

**Status:** accepted
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 09:53 AM UTC
**Owner:** Praveen


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1745 ntf: Too many ER messages in syslog. Related to #1639

2016-04-11 Thread Praveen

- **status**: unassigned --> accepted
- **assigned_to**: Praveen
- **Part**: - --> tests
- **Version**:  --> 4.7



---

** [tickets:#1745] ntf: Too many ER messages in syslog. Related to #1639**

**Status:** accepted
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:42 AM UTC
**Owner:** Praveen


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1743 osaf: Build fails with GCC version 6

2016-04-11 Thread Anders Widell

changeset:   7447:8f0b8473b8fc
branch:  opensaf-4.6.x
parent:  7443:efa10f74060f
user:Anders Widell 
date:Mon Apr 11 10:42:00 2016 +0200
summary: log: Ensure output parameter is always initialized by 
fileclose_h() [#1743]

changeset:   7448:7daa5fdf557c
branch:  opensaf-4.7.x
parent:  7444:140fb8a4ee6f
user:Anders Widell 
date:Mon Apr 11 10:42:00 2016 +0200
summary: log: Ensure output parameter is always initialized by 
fileclose_h() [#1743]

changeset:   7449:75325f5b6194
branch:  opensaf-5.0.x
parent:  7445:77a0f4135508
user:Anders Widell 
date:Mon Apr 11 10:55:08 2016 +0200
summary: log: Ensure output parameter is always initialized by 
fileclose_h() [#1743]

changeset:   7450:1f9920a8958b
branch:  opensaf-5.0.x
user:Anders Widell 
date:Mon Apr 11 10:55:09 2016 +0200
summary: logtest: Remove dead code [#1743]

changeset:   7451:794ef2b78564
parent:  7446:833a967c3bea
user:Anders Widell 
date:Mon Apr 11 10:55:08 2016 +0200
summary: log: Ensure output parameter is always initialized by 
fileclose_h() [#1743]

changeset:   7452:a22cc7b62aff
user:Anders Widell 
date:Mon Apr 11 10:55:09 2016 +0200
summary: logtest: Remove dead code [#1743]

[staging:8f0b84]
[staging:7daa5f]
[staging:75325f]
[staging:1f9920]
[staging:794ef2]
[staging:a22cc7]



---

** [tickets:#1743] osaf: Build fails with GCC version 6**

**Status:** review
**Milestone:** 4.6.2
**Created:** Fri Apr 08, 2016 12:34 PM UTC by Anders Widell
**Last Updated:** Mon Apr 11, 2016 08:39 AM UTC
**Owner:** Anders Widell


The following build errors were observed with GCC version 6 and optimization 
level -O3:


imm_dumper.cc: In function 'int main(int, char**)':
imm_dumper.cc:149:5: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
 if ((c = getopt_long(argc, argv, "hp:x:c:a:", long_options, NULL)) == -1)
 ^~
imm_dumper.cc:152:13: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
 switch (c) {
 ^~




compdb.cc: In function 'int comp_init(AVND_COMP*, const SaImmAttrValuesT_2**)':
compdb.cc:1579:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSISetCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1582:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiSetCallbackTimeout);
   ^~~~
compdb.cc:1584:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSIRmvCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1587:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiRemoveCallbackTimeout);
   ^~~~




tet_Log_recov.c:76:18: error: 'wr_delay' defined but not used 
[-Werror=unused-const-variable=]
 static const int wr_delay = 100*1000; /* 100 ms */
  ^~~~




test_saImmOmCcbObjectCreate_2.c:20:30: error: 'nonExistingClassName' defined 
but not used [-Werror=unused-const-variable=]
 static const SaImmClassNameT nonExistingClassName = (SaImmClassNameT) __FILE__;
  ^~~~




In file included from ../../../../../osaf/libs/core/include/ncs_osprm.h:32:0,
 from ../../../../../osaf/libs/core/include/ncs_ubaid.h:45,
 from ../../../../../osaf/libs/core/include/mbcsv_papi.h:29,
 from lgs.h:30,
 from lgs_stream.cc:29:
../../../../../osaf/libs/core/common/include/logtrace.h: In function 'int 
log_stream_file_close(log_stream_t*)':
../../../../../osaf/libs/core/common/include/logtrace.h:131:46: error: 
'errno_ret' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
 #define LOG_NO(format, args...) _logtrace_log(__FILE__, __LINE__, LOG_NOTICE, 
(format), ##args)
  ^
lgs_stream.cc:978:6: note: 'errno_ret' was declared here
  int errno_ret;
  ^




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your

[tickets] [opensaf:tickets] #1745 ntf: Too many ER messages in syslog. Related to #1639

2016-04-11 Thread elunlen

- **summary**: Too many ER messages in syslog. Related to #1639 --> ntf: Too 
many ER messages in syslog. Related to #1639



---

** [tickets:#1745] ntf: Too many ER messages in syslog. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:37 AM UTC
**Owner:** nobody


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1746 clm: Too many ER messages in syslog. Related to #1639

2016-04-11 Thread elunlen

- **summary**: Too many ER messages in syslog. Related to #1639 --> clm: Too 
many ER messages in syslog. Related to #1639



---

** [tickets:#1746] clm: Too many ER messages in syslog. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:39 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:39 AM UTC
**Owner:** nobody


See ticket [#1745]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1743 osaf: Build fails with GCC version 6

2016-04-11 Thread Anders Widell

- **Milestone**: 5.0.RC1 --> 4.6.2
- **Comment**:

changeset:   7443:efa10f74060f
branch:  opensaf-4.6.x
parent:  7413:76c2220731b3
user:Anders Widell 
date:Mon Apr 11 10:25:49 2016 +0200
summary: amfnd: Add missing braces [#1743]

changeset:   7444:140fb8a4ee6f
branch:  opensaf-4.7.x
parent:  7414:55b4fe6d2537
user:Anders Widell 
date:Mon Apr 11 10:25:49 2016 +0200
summary: amfnd: Add missing braces [#1743]

changeset:   7445:77a0f4135508
branch:  opensaf-5.0.x
parent:  7441:5b6ecbd4a400
user:Anders Widell 
date:Mon Apr 11 10:25:49 2016 +0200
summary: amfnd: Add missing braces [#1743]

changeset:   7446:833a967c3bea
parent:  7442:4063690ec922
user:Anders Widell 
date:Mon Apr 11 10:25:49 2016 +0200
summary: amfnd: Add missing braces [#1743]

[staging:efa10f]
[staging:140fb8]
[staging:77a0f4]
[staging:833a96]




---

** [tickets:#1743] osaf: Build fails with GCC version 6**

**Status:** review
**Milestone:** 4.6.2
**Created:** Fri Apr 08, 2016 12:34 PM UTC by Anders Widell
**Last Updated:** Fri Apr 08, 2016 04:12 PM UTC
**Owner:** Anders Widell


The following build errors were observed with GCC version 6 and optimization 
level -O3:


imm_dumper.cc: In function 'int main(int, char**)':
imm_dumper.cc:149:5: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
 if ((c = getopt_long(argc, argv, "hp:x:c:a:", long_options, NULL)) == -1)
 ^~
imm_dumper.cc:152:13: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
 switch (c) {
 ^~




compdb.cc: In function 'int comp_init(AVND_COMP*, const SaImmAttrValuesT_2**)':
compdb.cc:1579:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSISetCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1582:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiSetCallbackTimeout);
   ^~~~
compdb.cc:1584:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if 
(immutil_getAttr(const_cast("saAmfCompCSIRmvCallbackTimeout"), 
attributes,
  ^~
compdb.cc:1587:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   comp->use_comptype_attr->set(CsiRemoveCallbackTimeout);
   ^~~~




tet_Log_recov.c:76:18: error: 'wr_delay' defined but not used 
[-Werror=unused-const-variable=]
 static const int wr_delay = 100*1000; /* 100 ms */
  ^~~~




test_saImmOmCcbObjectCreate_2.c:20:30: error: 'nonExistingClassName' defined 
but not used [-Werror=unused-const-variable=]
 static const SaImmClassNameT nonExistingClassName = (SaImmClassNameT) __FILE__;
  ^~~~




In file included from ../../../../../osaf/libs/core/include/ncs_osprm.h:32:0,
 from ../../../../../osaf/libs/core/include/ncs_ubaid.h:45,
 from ../../../../../osaf/libs/core/include/mbcsv_papi.h:29,
 from lgs.h:30,
 from lgs_stream.cc:29:
../../../../../osaf/libs/core/common/include/logtrace.h: In function 'int 
log_stream_file_close(log_stream_t*)':
../../../../../osaf/libs/core/common/include/logtrace.h:131:46: error: 
'errno_ret' may be used uninitialized in this function 
[-Werror=maybe-uninitialized]
 #define LOG_NO(format, args...) _logtrace_log(__FILE__, __LINE__, LOG_NOTICE, 
(format), ##args)
  ^
lgs_stream.cc:978:6: note: 'errno_ret' was declared here
  int errno_ret;
  ^




---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1746 Too many ER messages in syslog. Related to #1639

2016-04-11 Thread elunlen




---

** [tickets:#1746] Too many ER messages in syslog. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:39 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:39 AM UTC
**Owner:** nobody


See ticket [#1745]


---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1745 Too many ER messages in syslog. Related to #1639

2016-04-11 Thread elunlen




---

** [tickets:#1745] Too many ER messages in syslog. Related to #1639**

**Status:** unassigned
**Milestone:** 5.0.RC1
**Created:** Mon Apr 11, 2016 08:37 AM UTC by elunlen
**Last Updated:** Mon Apr 11, 2016 08:37 AM UTC
**Owner:** nobody


The patch seems to work but there is still some problems with the [#1639] fix

When running NTF test a lot of ER messages is written to the syslog

Example:
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:40 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:41 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER Lock on active node not allowed
2016-04-06 21:54:42 SC-1 osafclmd[486]: ER clms_imm_node_lock failed
.
.
.
.

Other example:
Apr  7 09:52:14 SC-1 local0.warn osafckptd[673]: WA saImmOiImplementerSet 
returned 9
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER Lock on active node not 
allowed
Apr  7 09:54:10 SC-1 local0.err osafclmd[475]: ER clms_imm_node_lock failed
Apr  7 09:54:29 SC-1 local0.err osafntfd[465]: ER NtfAdmin::subscriptionRemoved 
client 18 not found
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)
Apr  7 09:54:56 SC-1 local0.err osafntfd[465]: ER Failed to log an alarm or 
security alarm notification (7)



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1533 AMF : Deletion of node group should be allowed, if node group is in LOCK-IN state

2016-04-11 Thread Praveen

Updated AMF PR doc in change set:

changeset:   171:2680e0bca0f4
tag: tip
user:praveen.malv...@oracle.com
date:Mon Apr 11 13:07:17 2016 +0530
summary: amf: updated for enhancement [#1533]



---

** [tickets:#1533] AMF : Deletion of node group should be allowed, if node 
group is in LOCK-IN state**

**Status:** fixed
**Milestone:** 5.0.FC
**Created:** Fri Oct 09, 2015 09:08 AM UTC by Srikanth R
**Last Updated:** Thu Mar 24, 2016 04:57 AM UTC
**Owner:** Praveen


Changeset :  6901
 
  Deletion of node group should be allowed, if node group is in 
locked-instantiation state. 

  SOLO:/opt/goahead/tetware/opensaffire/suites/avsv/infra # immcfg -d  
safAmfNodeGroup=BasicNG2,safAmfCluster=myAmfCluster
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
OI reports: IMM: Validation abort: Completed validation fails 
(ERR_BAD_OPERATION)
OI reports: 'safAmfNodeGroup=BasicNG2,safAmfCluster=myAmfCluster' can be 
deleted in locked or unlocked admin state
SOLO:/opt/goahead/tetware/opensaffire/suites/avsv/infra # amf-state ng
safAmfNodeGroup=SCs,safAmfCluster=myAmfCluster
saAmfNGAdminState=UNLOCKED(1)
safAmfNodeGroup=PLs,safAmfCluster=myAmfCluster
saAmfNGAdminState=UNLOCKED(1)
safAmfNodeGroup=AllNodes,safAmfCluster=myAmfCluster
saAmfNGAdminState=UNLOCKED(1)
safAmfNodeGroup=BasicNG2,safAmfCluster=myAmfCluster
saAmfNGAdminState=LOCKED-INSTANTIATION(3)





---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1738 ClmTrack stop failed error message observed in the syslog during switchover

2016-04-11 Thread Nagendra Kumar

Please upload the logs.


---

** [tickets:#1738] ClmTrack stop failed error message observed in the syslog 
during switchover **

**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Thu Apr 07, 2016 08:55 AM UTC by Ritu Raj
**Last Updated:** Thu Apr 07, 2016 08:55 AM UTC
**Owner:** nobody


Setup:
Changeset- 7436
Version - opensaf 5.0
4 nodes configured with single PBE and a load of 30K objects

Steps performed:
During switchover, on the quiesced controller  the error  message "Failed to 
stop cluster tracking" is observed in the syslog

Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: NO ROLE SWITCH Active --> 
Quiesced
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer (applier) 
connected: 9499 (@OpenSafImmReplicatorA) <13773, 2010f>
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafntfimcnd[17992]: NO Started
**Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: ER Failed to stop cluster 
tracking 12
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafamfd[6197]: ER ClmTrack stop failed**
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafrded[6108]: NO RDE role set to QUIESCED
Apr  7 04:12:42 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer (applier) 
connected: 9500 (@OpenSafImmReplicatorB) <0, 2020f>
Apr  7 04:12:43 SLES-64BIT-SLOT1 osafimmnd[6138]: NO Implementer disconnected 
9490 <26, 2010f> (safAmfService)





---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1733 Payload got rebooted when cpnd is killed on payload

2016-04-11 Thread Pham Hoang Nhat

Hi,

Can you send me the running test application on four nodes?

/Nhat 


---

** [tickets:#1733] Payload got rebooted when cpnd is killed on payload**

**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Wed Apr 06, 2016 11:05 AM UTC by Madhurika Koppula
**Last Updated:** Mon Apr 11, 2016 06:22 AM UTC
**Owner:** nobody
**Attachments:**

- 
[cpsv.tgz](https://sourceforge.net/p/opensaf/tickets/1733/attachment/cpsv.tgz) 
(15.0 MB; application/octet-stream)


Setup:
Changeset- 7436
Version - opensaf 5.0
4 nodes configured with single PBE

Issue Observed: It is random.

1) When CPND is killed on payload, component restart of CPND failed because of 
expiration of component registration timer.
2) Node went for reboot. Test application is being ran.

Below is the timestamp of PL-4:

Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO Restarting a component of 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)

Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'componentRestart'

Apr  6 10:52:00 OEL_M-SLOT-4 osafckptnd[6263]: Started
Apr  6 10:52:10 OEL_M-SLOT-4 osafamfnd[3015]: NO Instantiation of 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' failed
Apr  6 10:52:10 OEL_M-SLOT-4 osafamfnd[3015]: NO Reason: component registration 
timer expired
Apr  6 10:52:10 OEL_M-SLOT-4 osafckptnd[6294]: Started

Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Instantiation of 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' failed

Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Reason: component registration 
timer expired
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: WA 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State RESTARTING 
=> INSTANTIATION_FAILED
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Component Failover trigerred 
for 'safSu=PL-4,safSg=NoRed,safApp=OpenSAF': Failed component: 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF'
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: ER 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF'got Inst failed
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: Rebooting OpenSAF NodeId = 132111 
EE Name = , Reason: NCS component Instantiation failed, OwnNodeId = 132111, 
SupervisionTime = 60
Apr  6 10:52:20 OEL_M-SLOT-4 opensaf_reboot: Rebooting local node; timeout=60
Apr  6 10:52:46 OEL_M-SLOT-4 kernel: imklog 5.8.10, log source = /proc/kmsg 
started.

3) Below is the timestamp of ACTIVE controller:

Apr  6 10:51:59 OEL_M-SLOT-1 osafimmd[6916]: WA No coordinator IMMND known 
(case B) - ignoring sync request
Apr  6 10:51:59 OEL_M-SLOT-1 osafimmd[6916]: NO Node 2040f request sync 
sync-pid:2980 epoch:0
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Resetting link 
<1.1.1:eth3-1.1.4:eth3>, peer not responding
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Lost link <1.1.1:eth3-1.1.4:eth3> on 
network plane A
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Lost contact with <1.1.4>
Apr  6 10:52:24 OEL_M-SLOT-1 osafamfd[7003]: NO Node 'PL-4' left the cluster
Apr  6 10:52:24 OEL_M-SLOT-1 osafclmd[6988]: NO Node 132111 went down. Not 
sending track callback for agents on that node
Apr  6 10:52:24 OEL_M-SLOT-1 osafclmd[6988]: NO Node 132111 went down. Not 
sending track callback for agents on that node
Apr  6 10:52:24 OEL_M-SLOT-1 osafimmnd[3728]: NO Global discard node received 
for nodeId:2040f pid:2980
Apr  6 10:52:24 OEL_M-SLOT-1 osafimmnd[3728]: NO Implementer connected: 1539 
(MsgQueueService132111) <12283, 2010f>



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1733 Payload got rebooted when cpnd is killed on payload

2016-04-11 Thread A V Mahesh (AVM)

I Not able to reproduce the problem,  and it seems it happened to once .

Nhat,

You can try to reproduce :

Have a 4 node setup and then  configuring below
`immcfg -a saAmfSGCompRestartMax=1000 safSg=NoRed,safApp=OpenSAF`
 and then while running application on  four nodes  restart cpnd multiple times.

-AVM




---

** [tickets:#1733] Payload got rebooted when cpnd is killed on payload**

**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Wed Apr 06, 2016 11:05 AM UTC by Madhurika Koppula
**Last Updated:** Thu Apr 07, 2016 11:21 AM UTC
**Owner:** nobody
**Attachments:**

- 
[cpsv.tgz](https://sourceforge.net/p/opensaf/tickets/1733/attachment/cpsv.tgz) 
(15.0 MB; application/octet-stream)


Setup:
Changeset- 7436
Version - opensaf 5.0
4 nodes configured with single PBE

Issue Observed: It is random.

1) When CPND is killed on payload, component restart of CPND failed because of 
expiration of component registration timer.
2) Node went for reboot. Test application is being ran.

Below is the timestamp of PL-4:

Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO Restarting a component of 
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)

Apr  6 10:52:00 OEL_M-SLOT-4 osafamfnd[3015]: NO 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'componentRestart'

Apr  6 10:52:00 OEL_M-SLOT-4 osafckptnd[6263]: Started
Apr  6 10:52:10 OEL_M-SLOT-4 osafamfnd[3015]: NO Instantiation of 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' failed
Apr  6 10:52:10 OEL_M-SLOT-4 osafamfnd[3015]: NO Reason: component registration 
timer expired
Apr  6 10:52:10 OEL_M-SLOT-4 osafckptnd[6294]: Started

Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Instantiation of 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' failed

Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Reason: component registration 
timer expired
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: WA 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State RESTARTING 
=> INSTANTIATION_FAILED
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: NO Component Failover trigerred 
for 'safSu=PL-4,safSg=NoRed,safApp=OpenSAF': Failed component: 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF'
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: ER 
'safComp=CPND,safSu=PL-4,safSg=NoRed,safApp=OpenSAF'got Inst failed
Apr  6 10:52:20 OEL_M-SLOT-4 osafamfnd[3015]: Rebooting OpenSAF NodeId = 132111 
EE Name = , Reason: NCS component Instantiation failed, OwnNodeId = 132111, 
SupervisionTime = 60
Apr  6 10:52:20 OEL_M-SLOT-4 opensaf_reboot: Rebooting local node; timeout=60
Apr  6 10:52:46 OEL_M-SLOT-4 kernel: imklog 5.8.10, log source = /proc/kmsg 
started.

3) Below is the timestamp of ACTIVE controller:

Apr  6 10:51:59 OEL_M-SLOT-1 osafimmd[6916]: WA No coordinator IMMND known 
(case B) - ignoring sync request
Apr  6 10:51:59 OEL_M-SLOT-1 osafimmd[6916]: NO Node 2040f request sync 
sync-pid:2980 epoch:0
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Resetting link 
<1.1.1:eth3-1.1.4:eth3>, peer not responding
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Lost link <1.1.1:eth3-1.1.4:eth3> on 
network plane A
Apr  6 10:52:24 OEL_M-SLOT-1 kernel: TIPC: Lost contact with <1.1.4>
Apr  6 10:52:24 OEL_M-SLOT-1 osafamfd[7003]: NO Node 'PL-4' left the cluster
Apr  6 10:52:24 OEL_M-SLOT-1 osafclmd[6988]: NO Node 132111 went down. Not 
sending track callback for agents on that node
Apr  6 10:52:24 OEL_M-SLOT-1 osafclmd[6988]: NO Node 132111 went down. Not 
sending track callback for agents on that node
Apr  6 10:52:24 OEL_M-SLOT-1 osafimmnd[3728]: NO Global discard node received 
for nodeId:2040f pid:2980
Apr  6 10:52:24 OEL_M-SLOT-1 osafimmnd[3728]: NO Implementer connected: 1539 
(MsgQueueService132111) <12283, 2010f>



---

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.--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

64 matches

Mail list logo