Skip to main content
NetApp Stage KB

tridentctl get backend is very slow or fails due to 'command terminated with exit code 1'

Last Updated:

Applies to

  • Astra Trident
  • ONTAP Backend
  • ONTAP cluster has more than 99 online data LIFs


  • tridentctl get backend fails due to 'command terminated with exit code 1'

# ./tridentctl get backend  -d
Operating mode = tunnel, Trident pod = trident-csi-84c99f54d-v4psr, Namespace = trident, CLI = oc
Invoking tunneled command: oc exec trident-csi-84c99f54d-v4psr -n trident -c trident-main -- tridentctl --debug get backend
Operating mode = direct, Server =, Autosuport server =
Trident URL:
Request Method: GET
Request URL:
Request headers: map[Content-Type:[application/json]]
Request body:
Error: Get EOF
command terminated with exit code 1

  • tridentctl get backend succeeds but takes a very long time
  • If debug logging for a backend is enabled by including debugTraceFlags in the backend definition, trident controller log shows that net-interface-get-iter API was invoked repeatatively

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.