Skip to main content
NetApp Knowledge Base

tridentctl get backend fails with the error command terminated with exit code 1

  1. Last updated
  2. Save as PDF
Views:
122
Visibility:
Public
Votes:
1
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Astra Trident 23.04
  • Netapp ONTAP 9.X
  • Veeam backup tool (Kasten)

Issue

  • When running the command to get the status of the Trident backend, it fails with the error message:

user@hostname:~# tridentctl get backends -n trident
command terminated with exit code 1

  • In the ontap EMS log file, it is possible to see traces like the following:

[Node_name: kernel: bsdsocket.queueLimit.reached:error]: Number of connection requests for the socket bound to port 443 having the IP address * has reached the limit of XXX connections. The socket uses TCP protocol

 

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.