Skip to main content
NetApp Knowledge Base

Object store is intermittently unable to connect due to Operation Timedout

  1. Last updated
  2. Save as PDF
Views:
241
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cbs
Last Updated:

Applies to

  • Cloud Volumes Ontap
  • Azure Blob Backup
  • Fabricpool

Issue

  • The backup object-store “Azure Blob” is going in unavailable state intermittently and coming in available state within few seconds:
  • From the event logs from CLI:

Time                Node             Severity      Event------------------- ---------------- ------------- ---------------------------
2/7/2025 11:37:53   Node-01    NOTICE        object.store.available: Able to connect to the object store "object_store" from node c2ee2f7f-7ffe-11eb-b164-d039ea254a0d.
2/7/2025 11:37:48   Node-01     EMERGENCY     object.store.unavailable: Unable to connect to the object store "object_store" from node c2ee2f7f-7ffe-11eb-b164-d039ea254a0d. Reason: Operation Timedout.

  • Event logs will trigger this event which can be seen in autosupport:

Wed Sep 17 03:14:59 +0200 [Node01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "object_store" from node c2ee2f7f-7ffe-11eb-b164-d039ea254a0d. Reason: Operation Timedout.
Wed Sep 17 03:18:59 +0200 [Node01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "object_store" from node c2ee2f7f-7ffe-11eb-b164-d039ea254a0d. 

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.