---
** [tickets:#855] immnd crash on payload node**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Apr 15, 2014 10:11 AM UTC
**Owner:** nobody
case:
1) A component calls exit() when active_cbk is received.
- **status**: unassigned --> assigned
- **assigned_to**: Anders Bjornerstedt
- **Comment**:
I need to know exactly which release and changeset problem was
observed on.
---
** [tickets:#855] immnd crash on payload node**
**Status:** assigned
**Milestone:** future
**Created:** Tue Apr 15, 201
OpenSAF4.3.2 changeset 5143
---
** [tickets:#855] immnd crash on payload node**
**Status:** assigned
**Milestone:** future
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Apr 15, 2014 10:37 AM UTC
**Owner:** Anders Bjornerstedt
case:
1) A component calls
- **Milestone**: future --> 4.3.3
- **Comment**:
I have a problem with the syslogs provided for #855.
Only the syslog provided for PL4 covers the time period of the crash of the
immnd which also occurrs on PL4.
The crash of PL4 is right after the commit of CCB 260 at
Apr 15 15:12:01 PL-4 os
New logs attached. Reproduced with other scenario
Attachment: logs.tgz (5.3 MB; application/x-compressed-tar)
---
** [tickets:#855] immnd crash on payload node**
**Status:** assigned
**Milestone:** 4.3.3
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Wed A
logs attached again.
steps to reproduce.
1) Brinup up 2n model
2) Make sure components which receive active cbk report error on self with
recovery=componentFailover
3) lock/unlock active Su.
Due to continuous faults on all nodes, a crash is observed on payload and
cluster as expected will go fo
- **status**: assigned --> accepted
---
** [tickets:#855] immnd crash on payload node**
**Status:** accepted
**Milestone:** 4.3.3
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Thu Apr 24, 2014 09:44 AM UTC
**Owner:** Anders Bjornerstedt
case:
1) A componen
In the new set of logfiles I can not find the IMMND crash anywhere.
Also there is missing the syslog file for pl4.
I think there was a mistake when creating the sub-tarfile for pl3,
see below.
The logs_new.tgz contains four files:
pl3_logs.tgz
pl4_logs.tgz
sc1_logs.tgz
sc2_lo
- **status**: accepted --> assigned
---
** [tickets:#855] immnd crash on payload node**
**Status:** assigned
**Milestone:** 4.3.3
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Mon Apr 28, 2014 06:57 AM UTC
**Owner:** Anders Bjornerstedt
case:
1) A componen
- **status**: assigned --> unassigned
- **Comment**:
There have been difficulties in obtaining a correct set of syslog files
and no success in reproducing the problem reported by this ticket.
So I am un-assigning it for now.
In case anyone encounters the problem again, plesae save the syslog
file
- **assigned_to**: Anders Bjornerstedt --> nobody
---
** [tickets:#855] immnd crash on payload node**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Wed Apr 30, 2014 06:41 AM UTC
**Owner:** nobody
case:
1) A com
- **Milestone**: 4.3.3 --> 4.4.2
---
** [tickets:#855] immnd crash on payload node**
**Status:** unassigned
**Milestone:** 4.4.2
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Mon Aug 18, 2014 07:47 AM UTC
**Owner:** nobody
case:
1) A component calls exit()
- **status**: unassigned --> needinfo
- **Comment**:
To solve this ticket, the problem needs to be reproduced and a
complete set of syslogs for the SC's and the (at least one)) payload
affected.
Or we should close this ticket.
---
** [tickets:#855] immnd crash on payload node**
**Status:** n
Could not reproduce in 4.5
---
** [tickets:#855] immnd crash on payload node**
**Status:** needinfo
**Milestone:** 4.4.2
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Oct 28, 2014 10:02 AM UTC
**Owner:** nobody
case:
1) A component calls exit() when act
We still support 4.4 so in principle the problem could be tried to be
reproduced on 4.4.
Also, I dont think there have been any major change in finalizeSync in 4.5.
So the reason it has not been reproduced on 4.5 is probably timing related.
An attempt to reproduce on 4.5 should proabably not have
Tried to reproduce in 4.4 but could not reproduce it.
---
** [tickets:#855] immnd crash on payload node**
**Status:** needinfo
**Milestone:** 4.4.2
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Oct 28, 2014 10:36 AM UTC
**Owner:** nobody
case:
1) A com
- **status**: needinfo --> not-reproducible
- **Comment**:
Could not be reproduced on 4.4
---
** [tickets:#855] immnd crash on payload node**
**Status:** not-reproducible
**Milestone:** 4.4.2
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Oct 28, 2014 1
- **Milestone**: 4.4.2 --> never
---
** [tickets:#855] immnd crash on payload node**
**Status:** not-reproducible
**Milestone:** never
**Created:** Tue Apr 15, 2014 10:11 AM UTC by surender khetavath
**Last Updated:** Tue Oct 28, 2014 01:05 PM UTC
**Owner:** nobody
**Attachments:**
- [logs.tg
n 15 april 2014 12:12
To: opensaf-tickets@lists.sourceforge.net
Subject: [tickets] [opensaf:tickets] #855 immnd crash on payload node
[tickets:#855]<http://sourceforge.net/p/opensaf/tickets/855/> immnd crash on
payload node
Status: unassigned
Milestone: fu
19 matches
Mail list logo
