メインコンテンツへスキップ

「Restapi/zapi接続タイムアウト」および「httpd.api.expired.session.limit」エラー

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

環境

  • ONTAP 9
  • Trident/OpenShift 環境(Kubernetes)
  • REST API/ZAPI

問題

  • API呼び出しの数が多い環境、特にTridentでOpenShiftおよびREST API/ZAPIを使用している場合、次のエラーが発生する可能性があります:
  • エラーメッセージ:
httpd.api.expired.session.limit: A Manage ONTAP(R) API request deadline exceeds the configured session limit, after 180s
  • または
bsdsocket.queueLimit.reached:error]: Number of connection requests for the socket bound to port 443 having the IP address * has reached the limit of 766 connections. The socket uses TCP protocol.
  • 症状:
    • すべてのZAPI/REST API呼び出しが失敗する
    • Tridentバックエンドがオフラインになる
    • クライアントが新しいPVCを接続または作成できない
    • System ManagerのGUIが応答しなくなる
    • 多数のqtreeが「TO_DELETE」サフィックスでONTAPに残り、自動的には削除されない

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.