What Information Do I Need to Gather to Allow GSC to Diagnose Heap Issues on HNAS

What Information Do I Need to Gather to Allow GSC to Diagnose Heap Issues on HNAS?

Environment

• Hitachi Network Attached Storage (HNAS)
  • 3100/3200
  • 3080/3090
  • 4000 series

Answer

A set of HNAS server diagnostics containing the last_dblog.txt of the node that crashed with a "failed to allocate" panic or a current_dblog.txt covering the time period when the problem was being reported.  If the reset was the last time time the system rebooted then the crash diagnostics for that panic should be in the last_dblog.txt in the most recent diagnostics.  

Additional Notes

Heap memory related events/issues may include:

• Failed to allocate panics ("start of "FailedToAllocate" panic"),
• Heap fragmentation ("No big free heap blocks left"),
• Heap related enforced limits:
  • Insufficient free heap:
    • "There is insufficient heap: dropping new connection from"
    • "There is insufficient heap: dropping additional connection request from"
  • Insufficient free heap in big sized heap blocks:
    • "There is insufficient heap: dropping new connection from"
    • "There is insufficient heap: dropping additional connection request from"