跳转到主内容

"Restapi/zapi connection timeout" 和 "httpd.api.expired.session.limit" 错误

  1. 最后更新
  2. 另存为PDF
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 保留在 ONTAP 中，后缀为"TO_DELETE"，不会自动删除

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.