[tickets] [opensaf:tickets] #1481 ckpt: cpsv tests improment

2015-09-16 Thread Pham Hoang Nhat 



---

** [tickets:#1481] ckpt: cpsv tests improment**

**Status:** assigned
**Milestone:** future
**Created:** Wed Sep 16, 2015 06:12 AM UTC by Pham Hoang Nhat
**Last Updated:** Wed Sep 16, 2015 06:12 AM UTC
**Owner:** Pham Hoang Nhat


To make cpsv tests working again and independent from tetware.


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1481 ckpt: cpsv tests improvement

2015-09-16 Thread Pham Hoang Nhat 
- **summary**: ckpt: cpsv tests improment --> ckpt: cpsv tests improvement



---

** [tickets:#1481] ckpt: cpsv tests improvement**

**Status:** accepted
**Milestone:** future
**Created:** Wed Sep 16, 2015 06:12 AM UTC by Pham Hoang Nhat
**Last Updated:** Wed Sep 16, 2015 06:12 AM UTC
**Owner:** Pham Hoang Nhat


To make cpsv tests working again and independent from tetware.


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1481 ckpt: cpsv tests improment

2015-09-16 Thread Pham Hoang Nhat 
- **status**: assigned --> accepted



---

** [tickets:#1481] ckpt: cpsv tests improment**

**Status:** accepted
**Milestone:** future
**Created:** Wed Sep 16, 2015 06:12 AM UTC by Pham Hoang Nhat
**Last Updated:** Wed Sep 16, 2015 06:12 AM UTC
**Owner:** Pham Hoang Nhat


To make cpsv tests working again and independent from tetware.


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1399 log: logsv gets stuck in a loop if passing zero(0) to maxFilesRotated

2015-09-16 Thread Vu Minh Nguyen 
- **status**: accepted --> review



---

** [tickets:#1399] log: logsv gets stuck in a loop if passing zero(0) to 
maxFilesRotated**

**Status:** review
**Milestone:** 4.5.2
**Created:** Thu Jul 02, 2015 08:47 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Aug 27, 2015 02:50 PM UTC
**Owner:** Vu Minh Nguyen


When users open an application stream with `maxFilesRotated` is set to zero (0) 
or leave it to default value, logsv will get stuck in a while loop forever.



---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1484 amf: Nway, two SUs active for same SI after sufailover recovery during si lock.

2015-09-16 Thread Praveen 



---

** [tickets:#1484] amf: Nway, two SUs  active for same SI  after sufailover 
recovery during si lock.**

**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 09:08 AM UTC by Praveen
**Last Updated:** Wed Sep 16, 2015 09:08 AM UTC
**Owner:** nobody
**Attachments:**

- 
[AppConfig-N-Way_2actives.xml](https://sourceforge.net/p/opensaf/tickets/1484/attachment/AppConfig-N-Way_2actives.xml)
 (16.1 kB; text/xml)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/1484/attachment/osafamfd) 
(1.3 MB; application/octet-stream)


Attached is the configuration and AMF traces to reproduce the problem.

steps to reproduce:
1)Lock the SI which has assignment on all the SUs.
2)When active component is processing quiesced callback, kill the standby comp 
for this Si on other SU with 
sufailover recovery.
3)AMF will revert back SI to unlocked state.
4)user will see two actives for same SIs.

Assignments before si lock:
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)

Assignment after si lock was tried and sufailover recovery:
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

For safSi=AmfDemo1,safApp=AmfDemo1, there are two active assignments.




---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1474 imm: Assigning default value to no-dangling attributes make cluster fail to start

2015-09-16 Thread Hung Nguyen 
- **status**: accepted --> review



---

** [tickets:#1474] imm: Assigning default value to no-dangling attributes make 
cluster fail to start**

**Status:** review
**Milestone:** 4.5.2
**Created:** Thu Sep 10, 2015 02:27 PM UTC by Hung Nguyen
**Last Updated:** Tue Sep 15, 2015 11:40 AM UTC
**Owner:** Hung Nguyen


root@SC1:~# immlist -c Test
<< Test - CONFIG >>
test : SA_STRING_T [1] {RDN, CONFIG, INITIALIZED}
dep : SA_NAME_T [0] = test=1 (6)  {CONFIG, WRITEABLE, NO_DANGLING}

Create test=1 and test=2
root@SC1:~# immcfg -c Test test=1
root@SC1:~# immcfg -c Test test=2

Set the attribute with default value to empty.
root@SC1:~# immcfg -a dep= test=2
root@SC-1:~# immlist -a dep test=2
dep=

Now test=1 can be deleted
root@SC1:~# immcfg -d test=1

Reboot cluster and it will fail to start
Sep 10 21:03:36 SC1 osafimmloadd: NO * Loading from PBE file imm.db at 
/srv/shared/imm/ *
Sep 10 21:03:40 SC1 osafimmnd[421]: NO ERR_FAILED_OPERATION: NO_DANGLING 
reference (test=1) is dangling (Ccb 1)
Sep 10 21:03:40 SC1 osafimmnd[421]: NO Ccb 1 ABORTED (IMMLOADER)

[#1377]


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1482 log: size of destination buffer is smaller than the size of the source buffer

2015-09-16 Thread Vu Minh Nguyen 



---

** [tickets:#1482] log: size of destination buffer is smaller than the size of 
the source buffer**

**Status:** unassigned
**Milestone:** 5.0
**Created:** Wed Sep 16, 2015 07:29 AM UTC by Vu Minh Nguyen
**Last Updated:** Wed Sep 16, 2015 07:29 AM UTC
**Owner:** nobody


In the function `void log_stream_delete(log_stream_t **s)` @ `lgs_stream.c`, 
there is using `strcpy()`
in which the size of destination buffer (max: 256 bytes) is smaller than the 
size of the source buffer (max: 257 bytes).

strcpy((char *)objectName.value, stream->name);

If long DN is enabled/supported, logsv could get trouble.


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1483 amf: isssue with nodeswitchvoer recovery when sufailover is enabled.

2015-09-16 Thread Praveen 



---

** [tickets:#1483] amf: isssue with nodeswitchvoer recovery when sufailover is 
enabled.**

**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 08:11 AM UTC by Praveen
**Last Updated:** Wed Sep 16, 2015 08:11 AM UTC
**Owner:** nobody



During admin operation like lock on su, if component faults with nodeswitchvoer 
recovery and sufailover flag is enabled for the component, it is observed that 
su was failover before the request for nodeswitchover comes to AMFD. The reason 
is AMFND responds with success for quiesced assignments before the clean up of 
components is over.
Attached is the traces and configuration to reproduce the problem for 2N model. 
Since problem is in AMFND, it may affects all red models. Also it may come in 
case of other admin operations also.

AMFD messages:
1)AMFD performs failover:
si'safSi=AmfDemo1,safApp=AmfDemo1', state'2'
Sep 16 12:52:07.526744 osafamfd [3215:sg_2n_fsm.cc:3946] TR act_found'0', 
quisced_found'0', quiscing_found'0'
Sep 16 12:52:07.526749 osafamfd [3215:sg_2n_fsm.cc:3963] << 
avd_su_state_determine: state '2'
Sep 16 12:52:07.526754 osafamfd [3215:sg_2n_fsm.cc:0558] << avd_sg_2n_act_susi: 
act: 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', stdby: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526759 osafamfd [3215:si_dep.cc:2072] >> 
avd_sidep_si_dependency_exists_within_su
Sep 16 12:52:07.526765 osafamfd [3215:sgproc.cc:2238] >> avd_su_role_failover:  
from SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' to 
SU:'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526770 osafamfd [3215:si_dep.cc:1706] >> 
avd_sidep_is_su_failover_possible: SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' 
node_state:2
Sep 16 12:52:07.526775 osafamfd [3215:si_dep.cc:1728] << 
avd_sidep_is_su_failover_possible: return value: 1
Sep 16 12:52:07.526780 osafamfd [3215:sgproc.cc:2076] >> avd_sg_su_si_mod_snd: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1', state 1
Sep 16 12:52:07.526786 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.526794 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537

2)It gets node switchover request
Sep 16 12:52:07.560701 osafamfd [3215:ntfa_api.c:1566] << saNtfNotificationSend
Sep 16 12:52:07.560707 osafamfd [3215:ntfa_api.c:1327] >> saNtfNotificationFree
Sep 16 12:52:07.560712 osafamfd [3215:ntfa_api.c:1331] T1 notificationHandle = 
4289724426
Sep 16 12:52:07.560720 osafamfd [3215:ntfa_util.c:1104] T1 free v_data.p_base 
(nil)
Sep 16 12:52:07.560726 osafamfd [3215:ntfa_api.c:1367] << saNtfNotificationFree
Sep 16 12:52:07.560731 osafamfd [3215:ntf.cc:0261] << avd_send_oper_chg_ntf
Sep 16 12:52:07.560736 osafamfd [3215:sgproc.cc:0576] >> 
perform_nodeswitchover_recovery: 'safAmfNode=SC-1,safAmfCluster=myAmfCluster'
Sep 16 12:52:07.560742 osafamfd [3215:sgproc.cc:0424] >> sg_su_failover_func: 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', 2
Sep 16 12:52:07.560748 osafamfd [3215:imm.cc:1819] >> 
avd_saImmOiAdminOperationResult: inv:120259084289, res:1
Sep 16 12:52:07.560754 osafamfd [3215:imm.cc:1824] << 
avd_saImmOiAdminOperationResult
Sep 16 12:52:07.560760 osafamfd [3215:comp.cc:0173] >> avd_comp_oper_state_set: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' ENABLED => DISABLED
Sep 16 12:52:07.560780 osafamfd [3215:imm.cc:1543] >> 
avd_saImmOiRtObjectUpdate: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' saAmfCompOperState
Sep 16 12:52:07.560808 osafamfd [3215:imm.cc:1562] << avd_saImmOiRtObjectUpdate
Sep 16 12:52:07.560817 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.560823 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537
Sep 16 12:52:07.560829 osafamfd [3215:mbcsv_util.c:0343] >> 
mbcsv_send_ckpt_data_to_all_peers
Sep 16 12:52:07.560834 osafamfd [3215:mbcsv_util.c:0387] TR dispatching FSM for 
NCSMBCSV_SEND_ASYNC_UPDAT



---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1485 amf:Nway, Unstable SG during SI lock when standby faulted with comp failover recovery.

2015-09-16 Thread Praveen 



---

** [tickets:#1485] amf:Nway, Unstable SG during SI lock when standby faulted 
with comp failover recovery.**

**Status:** unassigned
**Milestone:** 4.5.2
**Labels:** NWAY COMP_FAILOVER 
**Created:** Wed Sep 16, 2015 09:24 AM UTC by Praveen
**Last Updated:** Wed Sep 16, 2015 09:24 AM UTC
**Owner:** nobody
**Attachments:**

- 
[AppConfig-N-Way.xml](https://sourceforge.net/p/opensaf/tickets/1485/attachment/AppConfig-N-Way.xml)
 (16.1 kB; text/xml)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/1485/attachment/osafamfd) 
(280.5 kB; application/octet-stream)


Attached is the configuration and AMF traces to reproduce the problem.
steps to reproduce:
1)Lock the SI which has assignment on all the SUs.
2)When active component is processing quiesced callback, kill the standby comp 
for this SI on other SU with 
component failover  recovery.
3)AMF will revert back SI to unlocked state.
4)SG becomes unstable.
5)For the faulted SU, removal of assignments is not performed and it stuck in 
Terminating state.

Assignments before si lock:

safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

After SI lock and fault assignment status and su state:
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)

safSu=SU3,safSg=AmfDemo,safApp=AmfDemo1
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=TERMINATING(4)
saAmfSUReadinessState=OUT-OF-SERVICE(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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1483 amf: isssue with nodeswitchvoer recovery when sufailover is enabled.

2015-09-16 Thread Praveen 
- Description has changed:

Diff:



--- old
+++ new
@@ -1,4 +1,3 @@
-
 During admin operation like lock on su, if component faults with 
nodeswitchvoer recovery and sufailover flag is enabled for the component, it is 
observed that su was failover before the request for nodeswitchover comes to 
AMFD. The reason is AMFND responds with success for quiesced assignments before 
the clean up of components is over.
 Attached is the traces and configuration to reproduce the problem for 2N 
model. Since problem is in AMFND, it may affects all red models. Also it may 
come in case of other admin operations also.
 



- **status**: unassigned --> accepted
- **assigned_to**: Praveen



---

** [tickets:#1483] amf: isssue with nodeswitchvoer recovery when sufailover is 
enabled.**

**Status:** accepted
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 08:11 AM UTC by Praveen
**Last Updated:** Wed Sep 16, 2015 08:11 AM UTC
**Owner:** Praveen


During admin operation like lock on su, if component faults with nodeswitchvoer 
recovery and sufailover flag is enabled for the component, it is observed that 
su was failover before the request for nodeswitchover comes to AMFD. The reason 
is AMFND responds with success for quiesced assignments before the clean up of 
components is over.
Attached is the traces and configuration to reproduce the problem for 2N model. 
Since problem is in AMFND, it may affects all red models. Also it may come in 
case of other admin operations also.

AMFD messages:
1)AMFD performs failover:
si'safSi=AmfDemo1,safApp=AmfDemo1', state'2'
Sep 16 12:52:07.526744 osafamfd [3215:sg_2n_fsm.cc:3946] TR act_found'0', 
quisced_found'0', quiscing_found'0'
Sep 16 12:52:07.526749 osafamfd [3215:sg_2n_fsm.cc:3963] << 
avd_su_state_determine: state '2'
Sep 16 12:52:07.526754 osafamfd [3215:sg_2n_fsm.cc:0558] << avd_sg_2n_act_susi: 
act: 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', stdby: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526759 osafamfd [3215:si_dep.cc:2072] >> 
avd_sidep_si_dependency_exists_within_su
Sep 16 12:52:07.526765 osafamfd [3215:sgproc.cc:2238] >> avd_su_role_failover:  
from SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' to 
SU:'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526770 osafamfd [3215:si_dep.cc:1706] >> 
avd_sidep_is_su_failover_possible: SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' 
node_state:2
Sep 16 12:52:07.526775 osafamfd [3215:si_dep.cc:1728] << 
avd_sidep_is_su_failover_possible: return value: 1
Sep 16 12:52:07.526780 osafamfd [3215:sgproc.cc:2076] >> avd_sg_su_si_mod_snd: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1', state 1
Sep 16 12:52:07.526786 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.526794 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537

2)It gets node switchover request
Sep 16 12:52:07.560701 osafamfd [3215:ntfa_api.c:1566] << saNtfNotificationSend
Sep 16 12:52:07.560707 osafamfd [3215:ntfa_api.c:1327] >> saNtfNotificationFree
Sep 16 12:52:07.560712 osafamfd [3215:ntfa_api.c:1331] T1 notificationHandle = 
4289724426
Sep 16 12:52:07.560720 osafamfd [3215:ntfa_util.c:1104] T1 free v_data.p_base 
(nil)
Sep 16 12:52:07.560726 osafamfd [3215:ntfa_api.c:1367] << saNtfNotificationFree
Sep 16 12:52:07.560731 osafamfd [3215:ntf.cc:0261] << avd_send_oper_chg_ntf
Sep 16 12:52:07.560736 osafamfd [3215:sgproc.cc:0576] >> 
perform_nodeswitchover_recovery: 'safAmfNode=SC-1,safAmfCluster=myAmfCluster'
Sep 16 12:52:07.560742 osafamfd [3215:sgproc.cc:0424] >> sg_su_failover_func: 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', 2
Sep 16 12:52:07.560748 osafamfd [3215:imm.cc:1819] >> 
avd_saImmOiAdminOperationResult: inv:120259084289, res:1
Sep 16 12:52:07.560754 osafamfd [3215:imm.cc:1824] << 
avd_saImmOiAdminOperationResult
Sep 16 12:52:07.560760 osafamfd [3215:comp.cc:0173] >> avd_comp_oper_state_set: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' ENABLED => DISABLED
Sep 16 12:52:07.560780 osafamfd [3215:imm.cc:1543] >> 
avd_saImmOiRtObjectUpdate: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' saAmfCompOperState
Sep 16 12:52:07.560808 osafamfd [3215:imm.cc:1562] << avd_saImmOiRtObjectUpdate
Sep 16 12:52:07.560817 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.560823 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537
Sep 16 12:52:07.560829 osafamfd [3215:mbcsv_util.c:0343] >> 
mbcsv_send_ckpt_data_to_all_peers
Sep 16 12:52:07.560834 osafamfd [3215:mbcsv_util.c:0387] TR dispatching FSM for 
NCSMBCSV_SEND_ASYNC_UPDAT



---

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

[tickets] [opensaf:tickets] #1483 amf: isssue with nodeswitchvoer recovery when sufailover is enabled.

2015-09-16 Thread Praveen 
Attached are amfd trace file and configuration.


Attachments:

- 
[nodeswitchover.xml](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/0ffe8725/6896/attachment/nodeswitchover.xml)
 (15.7 kB; text/xml)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/0ffe8725/6896/attachment/osafamfd)
 (757.3 kB; application/octet-stream)


---

** [tickets:#1483] amf: isssue with nodeswitchvoer recovery when sufailover is 
enabled.**

**Status:** accepted
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 08:11 AM UTC by Praveen
**Last Updated:** Wed Sep 16, 2015 08:16 AM UTC
**Owner:** Praveen


During admin operation like lock on su, if component faults with nodeswitchvoer 
recovery and sufailover flag is enabled for the component, it is observed that 
su was failover before the request for nodeswitchover comes to AMFD. The reason 
is AMFND responds with success for quiesced assignments before the clean up of 
components is over.
Attached is the traces and configuration to reproduce the problem for 2N model. 
Since problem is in AMFND, it may affects all red models. Also it may come in 
case of other admin operations also.

AMFD messages:
1)AMFD performs failover:
si'safSi=AmfDemo1,safApp=AmfDemo1', state'2'
Sep 16 12:52:07.526744 osafamfd [3215:sg_2n_fsm.cc:3946] TR act_found'0', 
quisced_found'0', quiscing_found'0'
Sep 16 12:52:07.526749 osafamfd [3215:sg_2n_fsm.cc:3963] << 
avd_su_state_determine: state '2'
Sep 16 12:52:07.526754 osafamfd [3215:sg_2n_fsm.cc:0558] << avd_sg_2n_act_susi: 
act: 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', stdby: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526759 osafamfd [3215:si_dep.cc:2072] >> 
avd_sidep_si_dependency_exists_within_su
Sep 16 12:52:07.526765 osafamfd [3215:sgproc.cc:2238] >> avd_su_role_failover:  
from SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' to 
SU:'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 16 12:52:07.526770 osafamfd [3215:si_dep.cc:1706] >> 
avd_sidep_is_su_failover_possible: SU:'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' 
node_state:2
Sep 16 12:52:07.526775 osafamfd [3215:si_dep.cc:1728] << 
avd_sidep_is_su_failover_possible: return value: 1
Sep 16 12:52:07.526780 osafamfd [3215:sgproc.cc:2076] >> avd_sg_su_si_mod_snd: 
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1', state 1
Sep 16 12:52:07.526786 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.526794 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537

2)It gets node switchover request
Sep 16 12:52:07.560701 osafamfd [3215:ntfa_api.c:1566] << saNtfNotificationSend
Sep 16 12:52:07.560707 osafamfd [3215:ntfa_api.c:1327] >> saNtfNotificationFree
Sep 16 12:52:07.560712 osafamfd [3215:ntfa_api.c:1331] T1 notificationHandle = 
4289724426
Sep 16 12:52:07.560720 osafamfd [3215:ntfa_util.c:1104] T1 free v_data.p_base 
(nil)
Sep 16 12:52:07.560726 osafamfd [3215:ntfa_api.c:1367] << saNtfNotificationFree
Sep 16 12:52:07.560731 osafamfd [3215:ntf.cc:0261] << avd_send_oper_chg_ntf
Sep 16 12:52:07.560736 osafamfd [3215:sgproc.cc:0576] >> 
perform_nodeswitchover_recovery: 'safAmfNode=SC-1,safAmfCluster=myAmfCluster'
Sep 16 12:52:07.560742 osafamfd [3215:sgproc.cc:0424] >> sg_su_failover_func: 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', 2
Sep 16 12:52:07.560748 osafamfd [3215:imm.cc:1819] >> 
avd_saImmOiAdminOperationResult: inv:120259084289, res:1
Sep 16 12:52:07.560754 osafamfd [3215:imm.cc:1824] << 
avd_saImmOiAdminOperationResult
Sep 16 12:52:07.560760 osafamfd [3215:comp.cc:0173] >> avd_comp_oper_state_set: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' ENABLED => DISABLED
Sep 16 12:52:07.560780 osafamfd [3215:imm.cc:1543] >> 
avd_saImmOiRtObjectUpdate: 
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' saAmfCompOperState
Sep 16 12:52:07.560808 osafamfd [3215:imm.cc:1562] << avd_saImmOiRtObjectUpdate
Sep 16 12:52:07.560817 osafamfd [3215:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Sep 16 12:52:07.560823 osafamfd [3215:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537
Sep 16 12:52:07.560829 osafamfd [3215:mbcsv_util.c:0343] >> 
mbcsv_send_ckpt_data_to_all_peers
Sep 16 12:52:07.560834 osafamfd [3215:mbcsv_util.c:0387] TR dispatching FSM for 
NCSMBCSV_SEND_ASYNC_UPDAT



---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click

[tickets] [opensaf:tickets] #1486 SMFD faulted in active callback during switchovers

2015-09-16 Thread Ritu Raj 



---

** [tickets:#1486] SMFD faulted in active callback during switchovers**

**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 10:04 AM UTC by Ritu Raj
**Last Updated:** Wed Sep 16, 2015 10:04 AM UTC
**Owner:** nobody


Setup
4.6GA with changeset 6490
4 nodes(OEL6.4 with TIPC version 1.7.7) configured with no PBE configured 

Issues Observed:
> Cluser went for reboot during switchover as SMFD faulted due to 
'csiSetcallbackFailed'

Steps Performed:

 * Continuous switchovers are invoked on the setup.
 * After a count of over 1000 switchovers, Standby Controller (SC-2) got 
rebooted when it is being promoted to ACTIVE state , as SMFD failed in active 
callback.

Sep 16 06:25:00 SLOT-2 osafsmfd[1926]: ER amf_active_state_handler oi activate 
FAIL
Sep 16 06:25:00 SLOT-2 osafamfnd[1802]: NO 
'safComp=SMF,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 
'csiSetcallbackFailed' : Recovery is 'nodeFailfast'
Sep 16 06:25:00 SLOT-2 osafamfnd[1802]: ER 
safComp=SMF,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due 
to:csiSetcallbackFailed Recovery is:nodeFailfast
Sep 16 06:25:00 SLOT-2 osafamfnd[1802]: Rebooting OpenSAF NodeId = 131599 EE 
Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 
131599, SupervisionTime = 60


* After SC-2 went for reboot, SC-1 tried to become active, during which smfd 
also faulted on the new promoted back active controller.

Sep 16 06:25:00 SLOT-1 root: Invoking switchover from invoke_switchover.sh
Sep 16 06:25:00 SLOT-1 osafamfd[3830]: NO safSi=SC-2N,safApp=OpenSAF Swap 
initiated
Sep 16 06:25:00 SLOT-1 osafamfnd[3845]: NO Assigning 
'safSi=SC-2N,safApp=OpenSAF' QUIESCED to 'safSu=SC-1,safSg=2N,safApp=OpenSAF'
Sep 16 06:25:00 SLOT-1 osafsmfd[3871]: ncs_sel_obj_create: socketpair failed - 
Too many open files

Sep 16 06:25:05 SLOT-1 kernel: TIPC: Resetting link <1.1.1:eth0-1.1.2:eth1>, 
peer not responding
Sep 16 06:25:05 SLOT-1 kernel: TIPC: Lost link <1.1.1:eth0-1.1.2:eth1> on 
network plane A
Sep 16 06:25:05 SLOT-1 kernel: TIPC: Lost contact with <1.1.2>
Sep 16 06:25:05 SLOT-1 osaffmd[3716]: NO Node Down event for node id 2020f:

Sep 16 06:25:06 SLOT-1 osafimmnd[3746]: NO This IMMND re-elected coord 
redundantly, failover ?
Sep 16 06:25:06 SLOT-1 osafsmfd[3871]: ncs_sel_obj_create: socketpair failed - 
Too many open files
Sep 16 06:25:06 SLOT-1 osafsmfd[3871]: ER immutil_saImmOiInitialize_2 fail, rc 
= 2
...
Sep 16 06:25:06 SLOT-1 osafamfnd[3845]: ER 
safComp=SMF,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due 
to:csiSetcallbackFailed Recovery is:nodeFailfast
Sep 16 06:25:06 SLOT-1 osafamfnd[3845]: Rebooting OpenSAF NodeId = 131343 EE 
Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 
131343, SupervisionTime = 60



---

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

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

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

2015-09-16 Thread Ramesh 
Majority of code clean-up or organization in BASE/LEAP happened in 4.4 cycle 
itself. However further refinement (if any) will be taken up in 5.0 cycle.


changeset:   4722:a7fd4081b098
user:Ramesh 
date:Thu Dec 12 15:24:26 2013 +0530
summary: PLM: Avoid using macro m_GET_ASCII_DATE_TIME_STAMP in 
plms_dbg_utils.c [#537]

changeset:   4721:2499bf363834
user:Ramesh 
date:Thu Dec 12 15:14:54 2013 +0530
summary: base: Removed unsed functions from ncs_main_pub.h[#537]

changeset:   4720:989229e5218e
user:Ramesh 
date:Thu Dec 12 15:13:39 2013 +0530
summary: base: Deleted ncs_mds_def.h[#537]

changeset:   4719:30d309da122e
user:Ramesh 
date:Thu Dec 12 15:12:21 2013 +0530
summary: base: Removed unsued function definitions from usrbuf.h[#537]

changeset:   4718:b6de0e6e813a
user:Ramesh 
date:Thu Dec 12 15:11:25 2013 +0530
summary: base: Removed unused macros from ncs_tmr.h

changeset:   4717:4be957de83e8
user:Ramesh 
date:Thu Dec 12 15:10:44 2013 +0530
summary: base: Removed unused macros/structs from ncs_svd.h

changeset:   4716:567244554b36
user:Ramesh 
date:Thu Dec 12 15:08:58 2013 +0530
summary: base: Removed unused macros from ncs_osprm.h, ncssysf_def.h and 
os_defs.h files [#537]

changeset:   4715:5c60d8c4698f
user:Ramesh 
date:Thu Dec 12 15:08:18 2013 +0530
summary: base: Removed unused macros from sysf_ipc.h file.[#537]

changeset:   4714:39d880986561
user:Ramesh 
date:Thu Dec 12 15:07:20 2013 +0530
summary: base: Removed MMGR macro's from sysf_exc_scr.h andreplaced with 
malloc, free [#537]

changeset:   4713:f89d39bbbe9a
user:Ramesh 
date:Thu Dec 12 15:06:29 2013 +0530
summary: base: Deleted sysf_def.h file[#537]

changeset:   4712:e282fbc884fe
user:Ramesh 
date:Thu Dec 12 15:05:41 2013 +0530
summary: base: Deleted patricia.h file[#537]

changeset:   4711:c7023c82fe1a
user:Ramesh 
date:Thu Dec 12 15:04:51 2013 +0530
summary: base: Deleted ncs_tasks.h file[#537]

changeset:   4710:6581beaa2ab4
user:Ramesh 
date:Thu Dec 12 15:04:00 2013 +0530
summary: base: Removed MMGR macro's from ncs_hdl.h andreplaced with malloc, 
free[#537]

changeset:   4709:664f3aa0109a
user:Ramesh 
date:Thu Dec 12 15:02:42 2013 +0530
summary: base: Removed unsed macro's from ncs_edu.h[#537]

changeset:   4708:a6b84f73dac1
user:Ramesh 
date:Thu Dec 12 15:01:41 2013 +0530
summary: base: Deleted sysf_pat.h file[#537]

changeset:   4707:cdfbca484829
user:Ramesh 
date:Thu Dec 12 15:00:44 2013 +0530
summary: base: Deleted ncsft.h file[#537]

changeset:   4706:e337fe61b5a2
user:Ramesh 
date:Thu Dec 12 14:59:18 2013 +0530
summary: base: Deleted ncs_stack.h ncs_stack_pub.h hj_stack.c files[#537]





---

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

**Status:** accepted
**Milestone:** 4.7.FC
**Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan
**Last Updated:** Tue Aug 25, 2015 04:08 PM UTC
**Owner:** Ramesh


A great deal of legacy leap code cleanup was done through ticket 
http://devel.opensaf.org/ticket/652.
It can be seen that LEAP is *no more* a portation layer that it used to be, but 
is now providing functionality more of an *utility layer*.

Currently leap is acting as a bunch of wrapper/utility code providing the 
following functionalities:
- encode/decode routines
- buffer management
- patricia db
- wrappers for tasks
- mailbox
- timers
- other utilties

With this as the background, the following further cleanup and streamlining is 
desired to enable leap code to be unit-test ready:

- Remove any leftover dead code. I can see that for eg:- hj_stack.c, and some 
functions in os_defs.c can be removed. 
- Move code related to one particular functionality into one file.
- Identify functions that could be equivalent to APIs around which unit tests 
could be performed.
- Streamline .h files(same as above for .c files)


---

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] #537 make base code unit test friendly and remove any dead code

2015-09-16 Thread Ramesh 
- **Milestone**: 4.7.FC --> 5.0



---

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

**Status:** accepted
**Milestone:** 5.0
**Created:** Thu Aug 08, 2013 11:55 AM UTC by Mathi Naickan
**Last Updated:** Wed Sep 16, 2015 12:10 PM UTC
**Owner:** Ramesh


A great deal of legacy leap code cleanup was done through ticket 
http://devel.opensaf.org/ticket/652.
It can be seen that LEAP is *no more* a portation layer that it used to be, but 
is now providing functionality more of an *utility layer*.

Currently leap is acting as a bunch of wrapper/utility code providing the 
following functionalities:
- encode/decode routines
- buffer management
- patricia db
- wrappers for tasks
- mailbox
- timers
- other utilties

With this as the background, the following further cleanup and streamlining is 
desired to enable leap code to be unit-test ready:

- Remove any leftover dead code. I can see that for eg:- hj_stack.c, and some 
functions in os_defs.c can be removed. 
- Move code related to one particular functionality into one file.
- Identify functions that could be equivalent to APIs around which unit tests 
could be performed.
- Streamline .h files(same as above for .c files)


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1487 OpenSAF Compilation failed on OEL6.4 machine

2015-09-16 Thread Ritu Raj 



---

** [tickets:#1487] OpenSAF Compilation failed on OEL6.4 machine**

**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 11:49 AM UTC by Ritu Raj
**Last Updated:** Wed Sep 16, 2015 11:49 AM UTC
**Owner:** nobody


Setup:
This issue is seen on 4.7MO with changeset 6829
OEL6.4(64bit) with TIPC version 1.7.7 and gcc version 4.9.0 

Issues Observed:
  *OpenSAF fails to compile, as 'pidname' uninitialized in 'mdsc_db.c' and 
'mds_log.c'

--> make fails with below errors:
(1). mds_c_db.c: In function ‘get_adest_details’:
 **mds_c_db.c:102:5: error: ‘pid_name’ may be used uninitialized in** this 
function [-Werror=maybe-uninitialized]
 snprintf(process_name, MDS_MAX_PROCESS_NAME_LEN, "%s[%d]", pid_name, 
process_id);
 ^
mds_c_db.c: In function ‘get_subtn_adest_details’:
**mds_c_db.c:170:5: error: ‘pid_name’ may be used uninitialized in this 
function** [-Werror=maybe-uninitialized]
 snprintf(process_name, MDS_MAX_PROCESS_NAME_LEN, "%s[%u]", pid_name, 
process_id);
cc1: all warnings being treated as errors
make[6]: *** [libmds_la-mds_c_db.lo] Error 1
 
 
(2). mds_log.c: In function ‘get_process_name’:
**mds_log.c:61:2: error: ‘pid_name’ may be used uninitialized** in this 
function [-Werror=maybe-uninitialized]
  snprintf(process_name, MDS_MAX_PROCESS_NAME_LEN, "%s[%d]", pid_name, 
process_id);



---

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

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1488 LCK: if master GLND reboots deadlock can occur for currently held locks

2015-09-16 Thread Alex Jones 



---

** [tickets:#1488] LCK: if master GLND reboots deadlock can occur for currently 
held locks**

**Status:** assigned
**Milestone:** 4.5.2
**Created:** Wed Sep 16, 2015 02:54 PM UTC by Alex Jones
**Last Updated:** Wed Sep 16, 2015 02:54 PM UTC
**Owner:** Alex Jones


If the master GLND is rebooted while an exclusive lock (or locks) is held, when 
the new master is elected and the other GLNDs send over the current lock 
information held by them to the new master, they do not send all information 
needed by the new master to lock/unlock currently held locks.

When this happens the lock(s) can never be unlocked or granted.


---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1435 AMF: Delete nodegroup leaves app su OUT_OF_SERVICE

2015-09-16 Thread Praveen 
- **status**: review --> fixed
- **Comment**:

changeset:   6837:955ebb41de35
parent:  6835:b2ea16cef47f
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:09:48 2015 +0530
summary: amfd: assign SUs on unlocked nodes when locked NG is deleted 
[#1435].

changeset:   6836:39806387b4c3
branch:  opensaf-4.6.x
parent:  6834:477078a6e0bc
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:09:35 2015 +0530
summary: amfd: assign SUs on unlocked nodes when locked NG is deleted 
[#1435].

https://sourceforge.net/p/opensaf/mailman/message/34379547/



---

** [tickets:#1435] AMF: Delete nodegroup leaves app su OUT_OF_SERVICE **

**Status:** fixed
**Milestone:** 4.6.1
**Labels:** nodegroup NG 
**Created:** Thu Aug 06, 2015 06:24 AM UTC by Minh Hon Chau
**Last Updated:** Fri Aug 14, 2015 05:30 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[app3_twon2su2si.xml](https://sourceforge.net/p/opensaf/tickets/1435/attachment/app3_twon2su2si.xml)
 (11.5 kB; text/xml)


 Configuration: 2 SUs are hosted on PL-4 PL5 (as in app3_twon2su2si.xml)
 Steps:

  * Create nodegroup contains PL4 and PL5, with UNLOCK admin state
  * Load app3_twon2su2si.xml, unlock-in, unlock 2 SUs
  * Lock ng
  -> Admin state of ng, PL4, PL5 are LOCKED.
  * Unlock individual nodes PL4, PL5. This operation is allowed as documented 
in AMF PR
  (After completion of nodegroup SHUTDOWN or LOCK operation, a user can 
unlock either the individual nodes by performing unlock on that node or by 
performing unlock operation on that nodegorup. If unlock admin op is targeted 
on nodegroup, all nodes of nodegroup will be marked unlocked by  AMF.)
  -> NG is LOCKED, both PL4 PL5 are UNLOCKED. Also there are no assignments 
for amfdemo SU on PL4 PL5
  * Now, delete NG. This operation is allowed per documentation
   (Delete CCB operation is allowed on node group in LOCKED or UNLOCKED 
admin state and when node group is not undergoing any admin operation)
   
At the end, all states of nodes and su(s) on PL4 PL5 are healthy but the 
amfdemo su(s) are still out of service

safAmfNode=PL-4,safAmfCluster=myAmfCluster
saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)
safAmfNode=PL-5,safAmfCluster=myAmfCluster
saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)
safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)

At step 4, AMF could start app assignment once the nodes are UNLOCKED, or if NG 
deletion ccb is accepted, AMF should ensure services up after operation 
(provided that no interrupted 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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1363 amf: amfnd does not read all healthcheckKeys for same comptype in dynamic addtion of Su.

2015-09-16 Thread Praveen 
- **status**: review --> fixed
- **Milestone**: 4.6.1 --> 4.5.2
- **Comment**:

changeset:   6835:b2ea16cef47f
parent:  6832:e5e1fc6e2a9c
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:06:26 2015 +0530
summary: amfnd: avoid creating existing safHealthcheckKey record in amfnd 
database [#1363]

changeset:   6834:477078a6e0bc
branch:  opensaf-4.6.x
parent:  6831:aa867a12c10d
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:06:16 2015 +0530
summary: amfnd: avoid creating existing safHealthcheckKey record in amfnd 
database [#1363]

changeset:   6833:1ad451348b04
branch:  opensaf-4.5.x
parent:  6830:141747d20de4
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:06:01 2015 +0530
summary: amfnd: avoid creating existing safHealthcheckKey record in amfnd 
database [#1363]
https://sourceforge.net/p/opensaf/mailman/message/34081210/



---

** [tickets:#1363] amf: amfnd does not read all healthcheckKeys for same 
comptype in dynamic addtion of Su.**

**Status:** fixed
**Milestone:** 4.5.2
**Labels:** HealthCheck 
**Created:** Mon May 04, 2015 05:02 AM UTC by Praveen
**Last Updated:** Wed Jul 15, 2015 01:02 PM UTC
**Owner:** Praveen
**Attachments:**

- [tmp.xml](https://sourceforge.net/p/opensaf/tickets/1363/attachment/tmp.xml) 
(2.4 kB; text/xml)


This can be observed if a SU, component and a new health check key is added 
dynamically
in an existing model.

Steps to reproduce:
1)Bring amf demo up.
2)run immcfg -f tmp.xml.
  This will add a SU3 in the system.

amfnd logs:
AMFnd is reading only old key not the new one that is added in tmp.xml.

May  4 10:24:03.609690 osafamfnd [4808:di.cc:0672] >> avnd_di_object_upd_send: 
Comp 'safComp=AmfDemo,safSu=SU3,safSg=AmfDemo,safApp=AmfDemo1'
May  4 10:24:03.609696 osafamfnd [4808:di.cc:0777] >> avnd_di_msg_send: Msg 
type '8'
May  4 10:24:03.609702 osafamfnd [4808:di.cc:0968] >> avnd_diq_rec_add
May  4 10:24:03.609707 osafamfnd [4808:di.cc:0983] << avnd_diq_rec_add
May  4 10:24:03.609720 osafamfnd [4808:di.cc:1044] >> avnd_diq_rec_send
May  4 10:24:03.609726 osafamfnd [4808:mds.cc:1169] >> avnd_mds_send: Msg type 
'1'
May  4 10:24:03.609955 osafamfnd [4808:mds.cc:1224] << avnd_mds_send: 1
May  4 10:24:03.609992 osafamfnd [4808:di.cc:1064] << avnd_diq_rec_send: 1
May  4 10:24:03.610007 osafamfnd [4808:di.cc:0809] << avnd_di_msg_send: 1
May  4 10:24:03.610017 osafamfnd [4808:di.cc:0691] << avnd_di_object_upd_send: 1
May  4 10:24:03.610031 osafamfnd [4808:compdb.cc:1814] << avnd_comp_create: 0
May  4 10:24:03.610041 osafamfnd [4808:imma_om_api.c:0154] >> saImmOmInitialize
May  4 10:24:03.610057 osafamfnd [4808:imma_om_api.c:0180] TR OM client version 
A.2.1
May  4 10:24:03.610068 osafamfnd [4808:imma_om_api.c:0216] >> initialize_common
May  4 10:24:03.610078 osafamfnd [4808:imma_init.c:0270] >> imma_startup: use 
count 1
May  4 10:24:03.610087 osafamfnd [4808:imma_init.c:0293] << imma_startup: use 
count 2
May  4 10:24:03.610219 osafamfnd [4808:imma_om_api.c:0337] T1 Trying to add OM 
client id:287 node:2020f
May  4 10:24:03.610235 osafamfnd [4808:imma_om_api.c:0431] << initialize_common
May  4 10:24:03.610245 osafamfnd [4808:imma_om_api.c:0202] << saImmOmInitialize
May  4 10:24:03.610254 osafamfnd [4808:hcdb.cc:0311] >> avnd_hctype_config_get: 
'safVersion=1,safCompType=AmfDemo1'
May  4 10:24:03.610265 osafamfnd [4808:imma_om_api.c:6584] >> search_init_common
May  4 10:24:03.610278 osafamfnd [4808:imma_om_api.c:6842] TR root: 
safVersion=1,safCompType=AmfDemo1 param:0x7fff95f6a370
May  4 10:24:03.610441 osafamfnd [4808:imma_om_api.c:6987] << search_init_common
May  4 10:24:03.611175 osafamfnd [4808:hcdb.cc:0328] T1 
'safHealthcheckKey=AmfDemo,safVersion=1,safCompType=AmfDemo1'
May  4 10:24:03.611189 osafamfnd [4808:imma_om_api.c:7365] >> 
saImmOmSearchFinalize
May  4 10:24:03.611195 osafamfnd [4808:imma_om_api.c:7391] TR Freeing last 
result
May  4 10:24:03.611201 osafamfnd [4808:imma_om_api.c:7400] TR Freeing search 
buffer
May  4 10:24:03.611431 osafamfnd [4808:imma_om_api.c:7523] << 
saImmOmSearchFinalize
May  4 10:24:03.611449 osafamfnd [4808:hcdb.cc:0339] << avnd_hctype_config_get: 
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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list

[tickets] [opensaf:tickets] #1141 si assignments are not removed after lock/lock-in of su with failover

2015-09-16 Thread Praveen 
- **status**: review --> fixed
- **Comment**:

changeset:   6840:a2c9e8a31cb4
tag: tip
parent:  6837:955ebb41de35
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:34:59 2015 +0530
summary: amfd: maintain runtime updates for su, comp, si and csi at standby 
[#1141]

changeset:   6839:964e043fa545
branch:  opensaf-4.6.x
parent:  6836:39806387b4c3
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:33:32 2015 +0530
summary: amfd: maintain runtime updates for su, comp, si and csi at standby 
[#1141]

changeset:   6838:9ff3ee6e28df
branch:  opensaf-4.5.x
parent:  6833:1ad451348b04
user:praveen.malv...@oracle.com
date:Thu Sep 17 10:31:22 2015 +0530
summary: amfd: maintain runtime updates for su, comp, si and csi at standby 
[#1141]

https://sourceforge.net/p/opensaf/mailman/message/34335056/
Inroporated the comment before pushing.



---

** [tickets:#1141] si assignments are not removed after lock/lock-in of su with 
failover**

**Status:** fixed
**Milestone:** 4.5.2
**Created:** Mon Sep 29, 2014 02:03 PM UTC by surender khetavath
**Last Updated:** Fri Jul 31, 2015 12:36 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/1141/attachment/logs.tgz) 
(11.3 MB; application/x-compressed-tar)


changeset : 5918
model : 2n

configuration:
1App,1SG,2SUs with 50comps each,50SIs with 1CSI each

bring up the application. lock SU and parallely kill amfd on active node

Here sc2 was active. PL-3 and PL-4 hosts SU1 & SU2 resp.

safSu=SU1,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SG,safApp=test2nApp
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)

safSi=SI1,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI2,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI3,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI4,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
.

safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI49,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI50,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI27,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI28,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI29,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)






---

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

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1333 AMF: amfnd segfaults on controllers during opensafd shutdown

2015-09-16 Thread Praveen 
- **status**: review --> fixed
- **Comment**:

changeset:   6832:e5e1fc6e2a9c
parent:  6829:051902f2c511
user:praveen.malv...@oracle.com
date:Thu Sep 17 09:57:26 2015 +0530
summary: amfd: do not create compcsi of dependent csis if sponosr csi is 
unassigned [#1333]

changeset:   6831:aa867a12c10d
branch:  opensaf-4.6.x
parent:  6825:c5a67cc1d469
user:praveen.malv...@oracle.com
date:Thu Sep 17 09:56:52 2015 +0530
summary: amfd: do not create compcsi of dependent csis if sponosr csi is 
unassigned [#1333]

changeset:   6830:141747d20de4
branch:  opensaf-4.5.x
parent:  6824:c10165338d62
user:praveen.malv...@oracle.com
date:Thu Sep 17 09:56:17 2015 +0530
summary: amfd: do not create compcsi of dependent csis if sponosr csi is 
unassigned [#1333]

https://sourceforge.net/p/opensaf/mailman/message/34114878/



---

** [tickets:#1333] AMF: amfnd segfaults on controllers during opensafd 
shutdown**

**Status:** fixed
**Milestone:** 4.5.2
**Created:** Wed Apr 22, 2015 04:02 PM UTC by Srikanth R
**Last Updated:** Fri May 15, 2015 05:38 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[AMFND_COREDUMP.tgz](https://sourceforge.net/p/opensaf/tickets/1333/attachment/AMFND_COREDUMP.tgz)
 (350.5 kB; application/x-compressed-tar)


Changeset : 6377

Attached is the xml configuration with which opensafd is configured for 6 nodes 
and one  2N application ( two SUs hosted on each of the controller). Cluster 
startup timeout is set for 120 seconds

 * Brought up opensafd on all the nodes from SC-1, SC-2, PL-3 to PL-4.

 * After expiry of cluster timer,  the assignments are done to both the SUs

 * After some time, stopped opensafd on the payloads, followed by controllers.

 * Amfnd seg faulted on both the controllers during shutdown of opensafd


Core was generated by `/usr/lib64/opensaf/osafamfnd --tracemask=0x'.
Program terminated with signal 11, Segmentation fault.
 #0  0x7f827aaf39da in _IO_default_xsputn_internal () from /lib64/libc.so.6
b(gdb) bt
 #0  0x7f827aaf39da in _IO_default_xsputn_internal () from /lib64/libc.so.6
 #1  0x7f827aac332e in vfprintf () from /lib64/libc.so.6
 #2  0x7f827aaeec9b in vsnprintf () from /lib64/libc.so.6
 #3  0x7f827aacde33 in snprintf () from /lib64/libc.so.6
 #4  0x7f827c26830d in output () from /usr/lib64/libopensaf_core.so.0
 #5  0x7f827c2687b0 in _logtrace_trace () from 
/usr/lib64/libopensaf_core.so.0
 #6  0x0040829c in avnd_comp_cbq_csi_rec_del(avnd_cb_tag*, 
avnd_comp_tag*, SaNameT*) ()
 #7  0x0041a777 in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #8  0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #9  0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #10 0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #11 0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #12 0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #13 0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #14 0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #15 0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #16 0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #17 0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()
 #18 0x0041a54e in avnd_comp_csi_remove(avnd_cb_tag*, avnd_comp_tag*, 
avnd_comp_csi_rec*) ()
 #19 0x0041a7ee in avnd_comp_csi_remove_done(avnd_cb_tag*, 
avnd_comp_tag*, avnd_comp_csi_rec*) ()




---

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.--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets