Mailing List Archive

bsdsocket.queueLimit.reached
Hello,

We have been receiving this alert below intermittently and from what i believe
this only reared its head after an upgrade to 9.1, we are operating on a version
(9.1P2) where this supposed bug is fixed and it causes no issues that I am
aware.

Does anyone had any dealings with this alert? or know how to find out more about
the potential cause?

We are not aware of any network misconfigurations in the environment, but when I
run a 'network connections active show' I see his port being used by our ESXi
hosts for NFS. This also is reported by the other node in the cluster too and
also at a remote site by another cluster. The alerts are random and appear maybe
once a day. Maybe nothing to worry about but any information or help much
appreciated......


Filer: filer-a

Time: Tue, Jun 27 13:19:38 2017 +0100

Severity: LOG_ERR

Message: bsdsocket.queueLimit.reached: Number of connection requests for the
socket bound to port 924 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.

Description: This message occurs when the number of connection requests for a
socket reaches the maximum. These connection requests include partially
completed connections and connections that are ready to be accepted.

Action: Network misconfigurations can cause connectivity issues such as
asymmetric routing, which causes loss of ACKs. Check the network for any such
misconfigurations. A Denial of Service attack and an overloaded system can also
be reasons for such an event. Contact NetApp technical support.

Source: kernel

Index: 6771598

[.Note: This email message is sent using a deprecated event routing mechanism.

For information, search the knowledgebase of the NetApp support web site for
"convert existing event configurations in Data ONTAP 9.0."]
Re: bsdsocket.queueLimit.reached [ In reply to ]
On Tue, Jun 27, 2017 at 9:40 AM, TAYLOR DANIEL <dantaylor@ntlworld.com>
wrote:

> bsdsocket.queueLimit.reached


https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1006687

No worries. Disregard

--tmac

*Tim McCarthy, **Principal Consultant*

*Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>*

*I Blog at TMACsRack <https://tmacsrack.wordpress.com/>*
Re: bsdsocket.queueLimit.reached [ In reply to ]
Hi Tim,

Yeh I had seen this but was slightly confused, this was introduced in 9.1 but
appears to be fixed in 9.1?

Thanks

> On 27 June 2017 at 14:47 tmac <tmacmd@gmail.com> wrote:
>
>
> On Tue, Jun 27, 2017 at 9:40 AM, TAYLOR DANIEL <dantaylor@ntlworld.com
> mailto:dantaylor@ntlworld.com > wrote:
>
> >
> > >
> https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1006687
> https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1006687
>
> No worries. Disregard
>
> --tmac
>
> Tim McCarthy, Principal Consultant
>
> Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam
>
> I Blog at TMACsRack https://tmacsrack.wordpress.com/
>
>
Re: bsdsocket.queueLimit.reached [ In reply to ]
If you are still seeing it, you may want to open a P4 case so they can at
least fix the BURT description and where is is (not) fixed.

I agree, the description is awful in this case...


Description: In ONTAP 9.1, the number of listener ports for use by
Counter Manager...."

Fixed in: 9.1

something is off!

--tmac

*Tim McCarthy, **Principal Consultant*

*Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>*

*I Blog at TMACsRack <https://tmacsrack.wordpress.com/>*



On Tue, Jun 27, 2017 at 9:51 AM, TAYLOR DANIEL <dantaylor@ntlworld.com>
wrote:

> Hi Tim,
>
> Yeh I had seen this but was slightly confused, this was introduced in 9.1
> but appears to be fixed in 9.1?
>
> Thanks
>
> On 27 June 2017 at 14:47 tmac <tmacmd@gmail.com> wrote:
>
>
> On Tue, Jun 27, 2017 at 9:40 AM, TAYLOR DANIEL <dantaylor@ntlworld.com>
> wrote:
>
> bsdsocket.queueLimit.reached
>
>
> https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1006687
>
> No worries. Disregard
>
> --tmac
>
> *Tim McCarthy, **Principal Consultant*
>
> *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>*
>
> *I Blog at TMACsRack <https://tmacsrack.wordpress.com/>*
>
>
>
>
>