Skip to main content
NetApp Knowledge Base

ONTAP object store becomes unavailable unexpectedly

  1. Last updated
    Mar 13, 2024
  2. Save as PDF
Views:
175
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
3/13/2024, 12:57:53 PM

Applies to

  • ONTAP 9
  • FabricPool

Issue

An object store becomes unavailable due to the connection timing out or being unavailable when no changes were made within ONTAP or the object store

Sat Feb 24 22:29:29 -0600 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node 100e2b24-c7dc-11ed-b055-d039eaa24e12. Reason: Operation Timedout.

Sun Mar 03 23:12:13 -0600 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node 100e2b24-c7dc-11ed-b055-d039eaa24e12. Reason: Connection unavailable.

 

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.