Skip to main content
NetApp Knowledge Base

KTLS failed and object store unavailable messages

  1. Last updated
  2. Save as PDF
Views:
48
Visibility:
Public
Votes:
0
Category:
fsx-ontap
Specialty:
cloud
Last Updated:

Applies to

Amazon FSx for NetApp ONTAP

Issue

You see the following messages occurring regularly in EMS:

Fri Jan 05 00:23:45 +0000 [FsxId0000000-02: kernel: ems.engine.suppressed:debug]: Event 'ktls.cnxnHandshakeLimit' suppressed 10939 times in last 61 seconds.
Fri Jan 05 00:23:45 +0000 [FsxId0000000-02: kernel: ktls.cnxnHandshakeLimit:notice]: ONTAP reached the maximum limit of 170 concurrent TLS connection handshakes. If this limit is reached, subsequent TLS connections will fail.

These can be accompanied by the following:

Fri Jan 05 00:25:25 +0000 [FsxId0000000-02: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "FSxFabricpoolObjectStore" from node 1234-1234-1234-1234-1234. Reason: Connection unavailable.
Fri Jan 05 00:25:26 +0000 [FsxId0000000-02: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "FSxFabricpoolObjectStore" from node 1234-1234-1234-1234-1234.

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.