---
** [tickets:#1313] opensaf does not start when long dn object is present in
imm.db and cluster is reset**
**Status:** unassigned
**Milestone:** 4.5.1
**Created:** Mon Apr 13, 2015 08:57 AM UTC by Sirisha Alla
**Last Updated:** Mon Apr 13, 2015 08:57 AM UTC
**Owner:** nobody
This is
- **status**: unassigned -- accepted
- **assigned_to**: Anders Bjornerstedt
---
** [tickets:#1313] opensaf does not start when long dn object is present in
imm.db and cluster is reset**
**Status:** accepted
**Milestone:** 4.5.1
**Created:** Mon Apr 13, 2015 08:57 AM UTC by Sirisha Alla
This is not an old test. Stale object because of another test bumped into this
scenario.
---
** [tickets:#1313] opensaf does not start when long dn object is present in
imm.db and cluster is reset**
**Status:** unassigned
**Milestone:** 4.5.1
**Created:** Mon Apr 13, 2015 08:57 AM UTC by
- **Comment**:
Question: is this an old test that worked on 5.0 ?
---
** [tickets:#1313] opensaf does not start when long dn object is present in
imm.db and cluster is reset**
**Status:** unassigned
**Milestone:** 4.5.1
**Created:** Mon Apr 13, 2015 08:57 AM UTC by Sirisha Alla
**Last
Before starting cluster services export
export SA_ENABLE_EXTENDED_NAMES=1
Then opensaf will start sucessfully
May be logsv missed exporting the variable.
---
** [tickets:#1313] opensaf does not start when long dn object is present in
imm.db and cluster is reset**
**Status:** accepted
- **Comment**:
Updated and sent version 2 of the patch. The patch is updated to use the
current service names pid when sending the SIGABRT signal.Nodeinit when sending
SIGKILL uses the parent pid from the fork.
---
** [tickets:#1300] nid: cleanup should generate a core dump **
**Status:**
