[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

- **Milestone**: 4.7.RC1 --> never --- ** [tickets:#1514] Opensaf on payload failed to come up and IMMD on active controller faulted** **Status:** duplicate **Milestone:** never **Created:** Mon Oct 05, 2015 10:03 AM UTC by Ritu Raj **Last Updated:** Fri Oct 16, 2015 07:21 AM UTC **Owner:**

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

- **status**: assigned --> duplicate - **Comment**: I tested with Anders Bjornerstedt suggested below solution , and issue is NOT reproducible. please find below example steps to reduce the value for the opensafImmSyncBatchSize : On 10/15/2015 1:18 PM, Anders Bjornerstedt wrote: > > I see

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

I see this as a duplicate of #1291, which is closed as invalid. The basic problem is communication overload. The only available current solution for deployments that see this issue is to reduce the value for the opensafImmSyncBatchSize config attribute in the OpensAF IMM service object:

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

New logs are attached. Below is the time-stamp at which issue has been reproduced. Oct 6 11:12:54 SLES-32BIT-SLOT4 osafimmnd[32302]: WA Resending introduce-me - problems with MDS ? 50 Oct 6 11:12:55 SLES-32BIT-SLOT4 osafimmnd[32302]: ER Failed to load/sync. Giving up after 51 seconds,

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

- **assigned_to**: A V Mahesh (AVM) - **Component**: unknown --> base - **Priority**: major --> minor - **Milestone**: 4.5.2 --> 4.7.RC1 - **Comment**: This issue is reproducible in some version of TIPC. Currently the on Opensaf start up after the duplicate discovery logic is continuing with

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

Looks to be an MDS problem. can you share new logs --- ** [tickets:#1514] Opensaf on payload failed to come up and IMMD on active controller faulted** **Status:** assigned **Milestone:** 4.5.2 **Created:** Mon Oct 05, 2015 10:03 AM UTC by Ritu Raj **Last Updated:** Mon Oct 05, 2015 12:35

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

- **status**: unassigned --> assigned - **assigned_to**: Neelakanta Reddy --- ** [tickets:#1514] Opensaf on payload failed to come up and IMMD on active controller faulted** **Status:** assigned **Milestone:** 4.5.2 **Created:** Mon Oct 05, 2015 10:03 AM UTC by Ritu Raj **Last Updated:**

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

- Description has changed: Diff: --- old +++ new @@ -6,9 +6,10 @@ * Payload failed to join the cluster and later active controller rebooted Steps performed: -* Started OpenSAF On both controllers (SC-1 and SC-2) with a gap of 10 minutes. SC-1 took the active role and SC-2 took the

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

This issue is observed when OpenSAF is started on two nodes simultaneously. It is also observed when cluster reset has been triggered. --- ** [tickets:#1514] Opensaf on payload failed to come up and IMMD on active controller faulted** **Status:** assigned **Milestone:** 4.5.2 **Created:**

[tickets] [opensaf:tickets] #1514 Opensaf on payload failed to come up and IMMD on active controller faulted

--- ** [tickets:#1514] Opensaf on payload failed to come up and IMMD on active controller faulted** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Mon Oct 05, 2015 10:03 AM UTC by Ritu Raj **Last Updated:** Mon Oct 05, 2015 10:03 AM UTC **Owner:** nobody **Attachments:** -