Skip to main content
NetApp Knowledge Base

"Restapi/zapi connection timeout" and "httpd.api.expired.session.limit" Errors

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

Applies to

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

Issue

  • Users may experience the following errors in environments with high numbers of API calls, especially when using Trident with OpenShift and REST API/ZAPI:
  • Error messages:
httpd.api.expired.session.limit: A Manage ONTAP(R) API request deadline exceeds the configured session limit, after 180s
  • or
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.
  • Symptoms:
    • All ZAPI/REST API calls fail
    • Trident backend goes offline
    • Clients cannot attach or create new PVCs
    • System Manager GUI becomes unresponsive
    • High number of qtrees remain in ONTAP with a “TO_DELETE” suffix and are not deleted automatically

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.