Hi Pham,
We had applied the patch on 5.0 GA and observed that the issue is still
observed.
Below are the steps and the apis used in the application to reproduce the issue.
Application :
-> Invoke saCkptInitialize
-> Invoke saCkptCheckpointOpen with create flag and
SA_CKPT_WR_ACTIVE_REPLICA
- **Milestone**: 4.6.2 --> 4.7.2
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after couple of failover**
**Status:** accepted
**Milestone:** 4.7.2
**Created:** Fri Apr 15, 2016 06:26 AM UTC by Ritu Raj
**Last Updated:** Mon Apr 25, 2016 07:20 AM
The attachment is the fix. Please try to run testing with this fix.
Attachments:
-
[1765_cpd_delete_the_existing_object_and_create_a_new_one_during_creating_ckpt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/8ea9d424/be87/attachment/1765_cpd_delete_the_existing_object_and_create_a_
Irrespective of the callbacks order, this issue should not be observed.
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after couple of failover**
**Status:** accepted
**Milestone:** 4.6.2
**Created:** Fri Apr 15, 2016 06:26 AM UTC by Ritu Raj
**Last
It looks like the test case is depending on SA_AMF_PRESENCE_INSTANTIATED
callback_state
to determine fail-over is competed , but some time the standby is not
completely up ( CPND not yet copltely up) on standby, so this will cause
problem .
Please try to detect standby completely up and then
Is this setup 32bit & 64 bit combination ?
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after couple of failover**
**Status:** accepted
**Milestone:** 4.6.2
**Created:** Fri Apr 15, 2016 06:26 AM UTC by Ritu Raj
**Last Updated:** Tue Apr 19, 2016
- **Priority**: major --> minor
- **Comment**:
Its is observed that checkpoint creation failed if earlier replica objects are
not deleted, while checkpoint cretaion with other name is succeeded.
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after
Yes, the problem is reproducible. Below is the immfind output replicas
SOFO-64BIT-S3:~ # immfind |grep -i ckpt
safApp=safCkptService
safCkpt=all_replicas_ckpt_name_101
safReplica=safNode=PL-3\,safCluster=myClmCluster,safCkpt=all_replicas_ckpt_name_101
safReplica=safNode=SC-1\,safCluster=myClmClus
Hi,
According the log, the problem "saCkptCheckpointOpen: API return code = 2"
happened because the IMM object connecting to the created checkpoint existed
although the checkpoint didn't existed in the CPSv database. This happened
because the previous unlink checkpoint action had not finished y
- **status**: unassigned --> accepted
- **assigned_to**: Pham Hoang Nhat
- **Comment**:
Hi,
Can you send me the test application?
What is the interval between failovers?
Best regards,
Nhat Pham
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after
---
** [tickets:#1765] saCkptCheckpointOpen api call failed and returing
SA_AIS_ERR_LIBRARY after couple of failover**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Fri Apr 15, 2016 06:26 AM UTC by Ritu Raj
**Last Updated:** Fri Apr 15, 2016 06:26 AM UTC
**Owner:** nobody
**Attachm
11 matches
Mail list logo
