Skip to main content
NetApp Knowledge Base

Node rebooted with an Error: bsdsocket.queueLimit.reached

  1. Last updated
    Apr 26, 2022
  2. Save as PDF
Views:
451
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:
4/26/2022, 12:50:42 PM

Applies to

  • Cloud Volumes ONTAP
  • Microsoft Azure
  • nvram flushing

Issue

Azure CVO instance rebooted with the following errors:
 
  • 3/3/2021 09:32:39   Azurenode1-01 ERROR bsdsocket.queueLimit.reached: Number of connection requests for the socket bound to port 63002 having the IP address * has reached the limit of 7 connections. The socket uses TCP protocol. This event has occurred 1 times since the last warning.
  • 3/3/2021 09:32:27   Azurenode1-01 ERROR bsdsocket.queueLimit.reached: Number of connection requests for the socket bound to port 63000 having the IP address * has reached the limit of 7 connections. The socket uses TCP protocol. This event has occurred 1 times since the last warning.
  • 3/3/2021 09:31:57   Azurenode1-01 ALERT vnvram.dma.long.wait: vNVRAM flush taking over 10 seconds.

 

 

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.