My Oracle Support Banner

APG43L LLV31_RM001: OSAFIMMND Crashed On Both Nodes During A Node Reboot (Doc ID 1525006.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle Communications OpenSAFfire - Version 6.2.0 and later
Information in this document applies to any platform.

Symptoms

The problem occurrs when the standby node was being rebooted.

That standby node then came up and requested sync with the active one. Meanwhile one of the processes, a runtime object, update failed lead to the sync abort.

The core dump may be generated on both nodes for IMMND for  two different reasons:

  - ‘Node is in a state 2 that cannot acceptfinalize of sync, will terminate 1 0’ on active node

  - ‘Node is in a state 0 that cannot accept a sync message, will terminate’ on standby node

The following is the back trace of the core dump from the standby node:

Core was generated by `/usr/lib64/opensaf/osafimmnd'.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.