- **status**: review --> fixed
- **Comment**:
Closing this ticket. Please raise separate tickets if you find further issues.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** fixed
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Ha
changeset: 7791:bff5e886bd26
branch: opensaf-4.7.x
tag: tip
parent: 7785:5def8dd64c24
user:Nagendra Kumar
date:Thu Jul 07 16:32:21 2016 +0530
summary: amfnd: process su instantiation in a separate thread [#517]
[staging:bff5e8]
---
** [tickets:#517] Amfnd
changeset: 7784:1f7499ca3ec0
tag: tip
parent: 7782:74d3640dd115
user:Nagendra Kumar
date:Tue Jul 05 14:41:54 2016 +0530
summary: amfnd: commit imm.cc [#517]
changeset: 7783:8126120683ed
branch: opensaf-5.0.x
parent: 7781:2dd8f6e500e9
user:Nage
I will be pushing the patch for 4.7.x in 1-2 days.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Tue Jul 05, 2016 07:04 AM UTC
**Owner:** Nag
changeset: 7781:2dd8f6e500e9
branch: opensaf-5.0.x
parent: 7779:4be46c68ab50
user:Nagendra Kumar
date:Tue Jul 05 12:05:56 2016 +0530
summary: amfnd: process su instantiation in a separate thread [#517]
changeset: 7782:74d3640dd115
tag: tip
parent: 778
I would be pushing the latest flaoted patch today.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Mon Jun 27, 2016 10:53 AM UTC
**Owner:** Nag
- **Type**: enhancement --> defect
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Thu May 12, 2016 10:18 AM UTC
**Owner:** Nagendra Kumar
a
Ticket #1620 cs 7411 solves one of the issues in this ticket, the case where
ImmutilWrapperProfile was used with default values, e.g. errorsAreFatal. Now
errorsAreFatal is set to false.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milest
Can I make it a defect because another similar defect #1819 has been raised.
Please comment.
Thanks
-Nagu
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last
- **status**: unassigned --> review
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Wed May 04, 2016 10:28 AM UTC
**Owner:** Nagendra Kumar
changeset: 7591:8b7ff9e7ee50
branch: opensaf-5.0.x
parent: 7583:34aa67561642
user:Mathivanan N.P.
date:Wed May 04 15:50:00 2016 +0530
summary: amfnd: revert changeset:7541:9cf09e277bd8 - ticket [#1728]
changeset: 7592:149ab1204a06
branch: opensaf-5.0.x
user:
changeset: 7588:dcf5c3c090fa
user:Mathivanan N.P.
date:Wed May 04 15:40:43 2016 +0530
summary: amfnd: revert changeset:7412:f2b5abde4d71 - ticket [#517]
changeset: 7589:ede9089137bc
user:Mathivanan N.P.
date:Wed May 04 15:41:44 2016 +0530
summary: amfn
- **Milestone**: future --> 5.1.FC
- **Comment**:
Reverted the changes from 5.0.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Milestone:** 5.1.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Mon Mar
- **status**: review --> unassigned
- **Milestone**: 5.0.FC --> future
- **Comment**:
Moving it to future release as I don't have any plan to fix other issues
reported in this ticket as of now.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassi
changeset: 7356:4ee6e611100a
tag: tip
user:Nagendra Kumar
date:Mon Mar 28 19:08:31 2016 +0530
summary: amfnd: process su instantiation in a separate thread [#517]
[staging:4ee6e6]
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**S
So, after this patch, we need to work on the following work items in this
ticket:
1. Pushing Imm reading information in other flows of the code in the
separate thread created in the floated patch: This is not going to be easy as
Amfnd execution and Reading Imm goes together and segregating
- **status**: accepted --> review
- **Comment**:
I have floated the patch, please review.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** review
**Milestone:** 5.0.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Tue
Any comment before I float the patch ?
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Fri Mar 11, 2016 07:11 AM UTC
**Owner:** Nagendra Kuma
From the ticket description, I can't find the exact issue. I am not able to
reproduce a case where immnd is down and it is returning TRY_AGAIN to the
Amfnd. During Immnd down case, Imm API call stuck at Imma at the following
location:
"immutil_saImmOmInitialize->initialize_common->imma_startup->
- **status**: assigned --> accepted
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by Hans Nordebäck
**Last Updated:** Tue Nov 03, 2015 05:50 AM UTC
**Owner:** Nagendra Kumar
- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar
- **Part**: - --> nd
- **Milestone**: future --> 5.0.FC
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Milestone:** 5.0.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC
- **Type**: defect --> enhancement
- **Milestone**: 4.5.2 --> future
- **Comment**:
As part of ticket cleanup, evaluated and decided to keep it as enhancement. The
one of the solution proposed is to use a separate reader thread and will need
to revamp the code.
---
** [tickets:#517] Amfnd: c
- **Milestone**: 5.0 --> 4.5.2
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Tue Jan 20, 2015 08:44 AM UTC
**Owner:** nobody
avnd_comp_config_get_
- **Milestone**: 4.6.FC --> 5.0
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Milestone:** 5.0
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Wed Sep 03, 2014 06:28 AM UTC
**Owner:** nobody
avnd_comp_config_get_s
- **Milestone**: future --> 4.6.FC
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Milestone:** 4.6.FC
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Fri May 16, 2014 09:22 AM UTC
**Owner:** nobody
avnd_comp_config
- **status**: assigned --> unassigned
- **assigned_to**: Nagendra Kumar --> nobody
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Fri May 16, 201
We have seen this problem again.
I suggest we create an additional "IMM reader" thread in amfnd.
Just trying to understand the messaging protocol between the main thread and
this helper thread.
One idea is to delegate the reading done in context of REG_SU message to the
new thread. For each obje
As a start I suggest that:
1) AVSV_D2N_INFO_SU_SI_ASSIGN_MSG_INFO is extended with SI-rank
=> get_sirank() can be removed
2) AVSV_D2N_REG_SU_MSG_INFO is extended with SU-Failover
=> su_get_config_attributes() can be removed
This requires to bump the MDS protocol level between amfd and amfn
The problem just occurred in avnd_comp_cap_x_act_or_1_act_check().
saImmOmInitialize() fails with code 5, TIMEOUT. That code was introduced in
#1317.
The test case was SI swap of an application SI. In this particular case the
read is unnecessary. Is this a separate defect or should we keep them
Since I am more worried about #2 situation, we can adopt approach of an applier
in the main thread and amfnd can be applier for SU/Comp class only if possible.
We can remove reading imm data from Amfnd.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:*
>From Hans :
For more info see: http://devel.opensaf.org/~hafe/AMF/amfnd-start.png
Getting the config from amfd kind of means reverting back to the 3.0 state.
Good or bad I don't know yet. But it seems unnecessary to distribute
information that is already available locally on the node. At the sam
Or If Amfnd fails to get information from local Immnd(Timeout), it can get the
information from any other non-local Immnd.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** F
In broad level, Amfnd reads configuration from Immnd in below scenario:
1. During CSI Assignment.
2. SU instantiation.
3. Amfnd comming up.
4. During clc script running.
Mostly, we are getting stuck at #2.
One Solution looks to me for #2 : In case Amfnd fails to get information from
local Immnd
- **Version**: --> 4.3
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Mon Aug 19, 2013 09:40 AM UTC
**Owner:** Nagendra Kumar
avnd_comp_config_get_su calls immutil_saImm
First there are logs but they are still internal. And immnd is restarted by AMF
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Mon Aug 19, 2013 04:37 AM UTC
**Owner:** Nage
>>The question still remains what amfnd should do when IMM communication times
>>out.
If Immnd is not responsive for configured timeout, then Amfnd aborts and it
traslates into rebooting the node. It looks justifiable for Amfnd as untill it
doesn't get configurable information, it can't proceeds
What triggered this problem was that they powered off SC-2 after a cluster
reboot. This causes immnd on some of the PL's to restart (OUT OF ORDER
messages). On one of the PL's (PL-5) the immnd failed to contact the immd after
the restart causing the amfnd OmInitialize to timeout with TRY AGAIN.
We need some more information on this issue. Is it an application SU or
middleware SU instantiation ? I guess this is an application SU instantiation
when opensafd is stoppoing and amfnd is not available. Please confirm.
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitia
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Tue Aug 13, 2013 12:26 PM UTC
**Owner:** Nagendra Kumar
avnd_comp_config_get_su calls immutil_saImmOmInitialize and
Immuti
This kind of problem is also related to imm enhancement ticket [#27]
https://sourceforge.net/p/opensaf/tickets/27/
Not much help right now for solving this ticket.
The idea in (#27) is that a select few operations, such as implementer-set,
class-implementer-set, class-implementer-release
could
Old ticket: https://sourceforge.net/p/opensaf/tickets/395/
not sure if this one is needed. it contains no logs nothing...
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Tue
This could happen if the local immnd is down, then there would be a deadlock
like this. I think there are some old tickets on devel.opensaf.org that touches
this
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013
- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** assigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Wed Jul 24, 2013 08:32 AM UTC
**Owner:** Nagendra Ku
- **summary**: Amfnd: --> Amfnd: coredumps when calling
immutil_saImmOmInitialize
---
** [tickets:#517] Amfnd: coredumps when calling immutil_saImmOmInitialize**
**Status:** unassigned
**Created:** Wed Jul 24, 2013 08:29 AM UTC by hano
**Last Updated:** Wed Jul 24, 2013 08:29 AM UTC
**Owner:
44 matches
Mail list logo
