Pillar Axiom: Slammer Control Unit Recovery Succeeded on Axiom Releases below 03.03.25 (Doc ID 1475984.1)

Last updated on FEBRUARY 08, 2016

Applies to:

Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
This specific issue only affects Ax600, Ax500, and Ax300 systems on releases below 03.03.25

Symptoms

The Axiom Slammer will run continuously for several months, then warm start, with a corrupt core dump.   The warm start may succeed, or there may not be enough memory to complete the warm start, so the CU fails over and fails back.

Either of these will resolve the causing memory leak and allow the Slammer CU to run for several more months until it runs out of memory again.  

If the load on the Axiom is reasonably well balanced, the two Slammer CU's in any given slammer will tend to see the warm starts or CU failovers within a few days of each other.

In the scanlog summary Slammer Log section, the signature is: PSG_NMQ    PANIC_ASSERT: buf pointer is NULL

The dumper will attempt to run, but there is insufficient memory, and the dumper will fail to produce a core, or will produce a corrupt, incomplete core.

The duration the Slammer has been running continuously is encoded in the name of the Slammer log file.

For example:  100130.200703-101127.213342.GMT.podr-pa.OUTLOG  where the dates are encoded as YYMMDD.HHMMSS-YYMMDD.HHMMSS GMT

This indicates that the Slammer CU has been running continuously since 2010, Jan 30 at 20:07:03 GMT. 

The time of the panic is 2010, November 27th at 21:33:42 GMT

If the CU has been running continuously for more than 5-6 months, the specific memory leak is BUG 13746588 - [Legacy defect 49027][SLOW MEMORY LEAK]

If the CU has been running continuously for 2-3 months, the specific memory leak is Bug 13750977 [Legacy defect 55860] [MEMORY LEAK]  

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms