Asset ID: |
1-72-2030069.1 |
Update Date: | 2018-05-30 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2030069.1
:
Oracle ZFS Storage Appliance: AKD dumping core (ABORT: "../common/nas_usage.c", line 735: assertion failed: nvlist_lookup_string(props, "com.sun.ak:type", &dstype) == 0)
Related Items |
- Sun ZFS Storage 7420
- Oracle ZFS Storage ZS3-2
- Oracle ZFS Storage ZS4-4
- Sun ZFS Storage 7120
- Oracle ZFS Storage ZS3-4
- Sun ZFS Storage 7320
- Oracle ZFS Storage ZS3-BA
|
Related Categories |
- PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
|
In this Document
Created from <SR 3-10861993821>
Applies to:
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
Sun ZFS Storage 7420 - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
7000 Appliance OS (Fishworks)
Symptoms
The appliance BUI appears to have hung.
The customer is also running a script which collects data from the appliance - they had the following errors:
From: xxxxxxxx
Sent: 05 June 2015 09:06
To: xxxxxxxx
Subject: Cron xxxxxxxxxx
aksh: uncaught internal exception: { stack:
'akshExit(255)@:0\n()@akInterpreter.js:2036\n@/usr/lib/ak/js/shell/akLocore.js:630\n', lineNumber:
2036, fileName: 'akInterpreter.js', message: 'couldn\'t make door call: Bad file number' }
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
aksh: fatal error: could not connect to akd; is it both enabled and running?
The customer is running Appliance Software Release 2013.1.4.0
Cause
From the AKD corefile, the stack trace appears to match Bug 20852911 (akd panic ""assertion failed: nvlist_lookup_string"" when running workflow)
Bug comment is:
> "Customer is running the attached ""Apply Default User Quotas to Shares"" workflow every 15 minutes.
> Periodically the workflow appears to cause akd to panic and a core to be taken"
Solution
Upgrade to Appliance Firmware Release 2013.1.4.6 (or later).
***Checked for relevance on 30-MAY-2018***
References
<BUG:20852911> - BACKPORT 21309980 TO AK-2013-REL - AKD PANIC "ASSERTION FAILED: NVLIST_LOOKUP_ST
Attachments
This solution has no attachment