Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2180809.1
Update Date:2016-09-12
Keywords:

Solution Type  Problem Resolution Sure

Solution  2180809.1 :   Oracle ZFS Storage Appliance: System Log reports sshd "key_from_blob" Errors  


Related Items
  • Sun ZFS Storage 7420
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Sun Storage 7110 Unified Storage System
  •  
  • Oracle ZFS Storage ZS4-4
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun ZFS Storage 7120
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • 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
  •  


System generating  sshd "key_from_blob" Errors  message in system.sys and debug.sys

In this Document
Symptoms
Cause
Solution


Created from <SR 3-13217362251>

Applies to:

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-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Oracle ZFS Storage ZS3-BA - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

System generating the following message in system.sys and debug.sys

Aug 22 21:04:47 nas18 sshd[15850]: [ID 800047 auth.error] error: buffer_get_string_ret: bad string length 813827233
Aug 22 21:04:47 nas18 sshd[15850]: [ID 800047 auth.error] error: key_from_blob: can't read key type
Aug 22 21:04:47 nas18 sshd[15850]: [ID 800047 auth.error] error: key_read: key_from_blob MIIEoQIBAAKCAQEAxnHuRwHYCbqcCPfPwMee9sOjfSwfPj3dLXb8iJkJqta1I2/Tb7uuv1bIn+yS/k+9dR4ywzFvNQH4Lto5KUiqatztPU5XvRsi+dDQh7qXmg3PoHMDrzEF1N/QCtE2JK1sYalb331LVg8KMZ8X0o8hXKB/OM5KyU4074IUBrq5iWZM5Fe2OBPV/7S5AiRhIHc13f0z3SzhQC6WCRMVzBwLlc/GjJ2kmUoJU2R2e3NsGwFge8INBswGaIj9390qXk+asOScBtzrP0XwePBk6ukBDUNlw7kU3QryhG1R8jTnMHNK02nVgfklcuOoYxz6VCqSuJlDevqwdeC0YhuWpHPdmQIBIwKCAQAWre9Ykn8XDgM0OZQWCC9sqKT4XNBe4n+tbK8ljdU4GIm66DVr2u9mUw+dP5vFSvEUsv58tTFH4vfK1xx5vylrTHLib1p8AxnwqiZ16

 

 

Cause

SSH keys were generated for some user accounts and installed on the appliance.

One of the trusted ssh keys was created with the "id_rsa" key instead of the "id_rsa.pub" key.

This caused the ssh key to exceed the maximum size of 256K supported by the appliance.

 

Solution

Remove any user defined ssh or public keys listed in the error logs and recreate the ssh key with the id_rsa.pub key.

Install the new key on the appliance.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback