Skip to main content
NetApp Knowledge Base

SnapMirror transfers fail when object.store.unavailable in EMS for "Skewed time"

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

Applies to

  • ONTAP 9
  • SnapMirror
  • FabricPool

Issue

  • NFS read\writ hang
  • SnapMirror transfers fail
  • EMS reports:

[Node_name: OscHighPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "object_name" from node Node_name. Reason: Skewed time

  • Checking the cluster time with the date command reveals that the time has drifted from the correct time
  • NTP is 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.