Detecting AKD Running Out of Mapped Memory Due to Many REST or CLI Logins Over Time
(Doc ID 2664999.1)
Last updated on JANUARY 17, 2024
Applies to:
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
The appliance kit daemon (akd) can grow very large and can run out of memory causing the Browser User Interface (BUI) and CLI to be slow or to hang complete. Log files (only found in bundles) may show messages about out of memory or resource unavailable. This document addresses large anonymous memory mappings within the akd process. The large akd memory usage will not show up in the analytics dataset for heap memory, however, the process size as show by ps or prstat will show a size greater than 7 GB.
Other symptoms include:
- REST or CLI access may fail.
- Cluster link may show as down from the other head of the cluster.
- Listing the hardware components in the BUI or CLI may hang.
- Unable to create new analytics datasets or unable to access analytics.
Changes
This issue can occur in OS8.8.0 through OS8.8.6.
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 |
| Troubleshooting Steps |