Oracle ZFS Storage Appliance: Phonehome Error After Upgrade - call for param #1 to system.push failed: call for param #1 to array.create failed: attempted to end an open structure as an array

Asset ID:	1-72-2266627.1
Update Date:	2017-05-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2266627.1 : Oracle ZFS Storage Appliance: Phonehome Error After Upgrade - call for param #1 to system.push failed: call for param #1 to array.create failed: attempted to end an open structure as an array

Related Items


Sun ZFS Storage 7420
 Oracle ZFS Storage ZS5-2
 Oracle ZFS Storage ZS3-2
 Oracle ZFS Storage ZS4-4
 Oracle ZFS Storage ZS5-4
 Oracle ZFS Storage ZS3-4
 Sun ZFS Storage 7120
 Oracle ZFS Storage Appliance Racked System ZS4-4
 Sun ZFS Storage 7320
 Oracle ZFS Storage ZS3-BA

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS

Phonehome errors seen after reboot or upgrade.  Error message is

    faultString: call for param #1 to system.push failed: call for param #1 to array.create failed: attempted to end an open structure as an array

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-14830673771>

Applies to:

Oracle ZFS Storage ZS5-4 - Version All Versions and later
Oracle ZFS Storage ZS5-2 - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

System phones home correctly, but when trying to view the scrk logs in the BUI it shows an error.

Cause

This looks to be due to a non-UTF-8/ASCIIT character being put into a log message, and this causes problems when trying to read the log file.

Solution

Logs show the following error:

failed to make request: error connecting to support service (Failed to connect to 194.218.xxx.xxx: Network is unreachable).

This address is not an Oracle address. I see connections made to the ASR server after this. This looks to have been an intermittent network issue.

The cause of the non-UTF-8 character in the log file is still under investigation. Contact Oracle Support to obtain a workaround to clear the log file

scrk-fix.aksh workflow can be used to clear the log file.

References

<BUG:25050520> - AKD UI BOMBS OUT DUE TO MALFORMED LOG ENTRIES

Attachments

This solution has no attachment