Skip to main content
NetApp Knowledge Base

Object-store unavailable on a single node after reboot due to connection unavailable

  1. Last updated
  2. Save as PDF
Views:
58
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • FabricPool
  • Object-storage
  • Intercluster-LIF
  • Certificates

Issue

  • After a node reboot or upgrade, object-store becomes unavailable only on one node
  • The object-store shows available on all other nodes
  • Logs similar to those shown below may be seen

EMS:

[node-01: OscLowPriThreadPool_3: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "FP-Object-store" from node <node-uuid>. Reason: Connection unavailable.
[node-01: ktlsd: ktls.failed:notice]: "The TLS connections have failed several times with remote host '10.10.10.10' in IPspace 'xxxx', for which the latest reason given is: OpenSSL: error:0A000086:SSL routines::certificate verify failed."

Sktrace:

[0:0] CLOUD_BIN_ERR:  object_store_config_ksmf_try_create: save=1, objStoreClientStoreSetup() failed for s3 handle -1fqdn="FP-Object-store",  with error 105 (No IP-address found for given hostname)
...
[1:0] OSC_ERR:  logCmd:371 HEAD CmdId 66 obj-name:  failed with OSC error: Inter-cluster LIF not configured
...

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.