Freenas 9.2 Error - Listen Queue Overflow

[Smeeghead]

Hi Guys,

I've searched the forums for this and only seen mention in a french posting (asking the same question I presume).

I started getting disconnects from my PS3 from Plexmedia server which I used to have occasionally with the previous 9.1 version (as an aside I had to fresh install the 'upgrade'!!!)

Since v9.2, I've noticed the PS3 is constantly disconnecting from the plex media server YET the plex server is still running as I CAN access it using plex media app on my IPAD. It's only when I looked at a LOG email this afternoon that I suspected that things were seriously wrong.
the email was the nightly security log and contained :-


freenas.local kernel log messages:

sonewconn: pcb 0xfffffe000c32aab8: Listen queue overflow: 151 already in queue awaiting acceptance
sonewconn: pcb 0xfffffe000c32aab8: Listen queue overflow: 151 already in queue awaiting acceptance
sonewconn: pcb 0xfffffe000c32aab8: Listen queue overflow: 151 already in queue awaiting acceptance
sonewconn: pcb 0xfffffe000c32aab8: Listen queue overflow: 151 already in queue awaiting acceptance

with the offending line repeated hundreds of times!!

Anybody have the slightest inkling just what may be wrong, as i know I haven't, and this is ONLY since i UPGRADED to v9.2 from v9.1

Apart from that, great job fellahs, such a great system!!!

 

[dlavigne]

In a nutshell, it means that the NIC can't keep up: http://lists.freebsd.org/pipermail/freebsd-net/2013-July/036017.html.

What's type of NIC is it and which driver (from ifconfig) is it using?

 

[Smeeghead]

HI There

thanks for replying,. from what I can gather from the manual for my HP N54L microserver its a Broadcom BCM5723 single-port Gigabit Ethernet controller

Also, the issue is that before the v9.2 upgrade it was working fine(ish) on v9.1 but after installing the v9.2 update, there was an upgrade available for the plex plugin which when I attempted to install it cabbaged half way through the installation process, so I had to delete the jail for plex and re-install it.

If you could let me know what specific info you require from ifconfig i.e. what to run at the cmd prompt, then I'll get the relevant output when I get back home later.

Cheers
smeeghead

 

[cyberjock]

Surprise! Not the recommended Intel brand NIC...

 

[dlavigne]

With that model, it is probably the bge driver (will look something like bge0 in ifconfig, next to the active Ethernet device). Broadcom isn't known for creating great NIC drivers, so if you can, take cyberjock's advice and invest in an Intel and let us know if that fixes the issue.

 

[Smeeghead]

Hi Guys,

Thanks for the reply, but the issue is not that its a broadcom NIC and not up to spec BUT that it was working fine for months with no mention EVER of this error in v9.1 before the v9.2 upgrade.

The issue seems to be with the v9.2 upgrade and not the NIC.

Sorry I didn't get the ifconfig output last night, but had to take the Mrs to the hospital (nothing too serious!!!), so I'll try to get it later today and post it.

As an aside, IF I have to put in a new NIC, just what would you recommend??

 

[mstinaff]

I'm seeing a very similar error filling my logs:
sonewconn: pcb 0xfffffe000da02e10: Listen queue overflow: 8 already in queue awaiting acceptance

And also only saw this after updating from 9.1 to 9.2
My NIC is and Intel 82579LM

I don't have plex installed on this machine, it is just shares a drive over NFS and runs twice daily rsync pulls from a few dozen unix workstations.

Thank you all for your time and help, and please let me know if there is anything else I can do to assist.

 

[Smeeghead]

Hi guys

Finally got the output from ifconfig.....

ifconfig
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether 38:ea:a7:a0:27:de
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x9
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:2d:97:df:7e:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 13 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 12 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 11 priority 128 path cost 2000
member: bge0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 200000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:0b:32:00:0b:0a
inet6 fe80::b:32ff:fe00:b0a%epair0a prefixlen 64 scopeid 0xb
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:c3:b6:00:0c:0a
inet6 fe80::c3:b6ff:fe00:c0a%epair1a prefixlen 64 scopeid 0xc
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:b4:6d:00:0d:0a
inet6 fe80::b4:6dff:fe00:d0a%epair2a prefixlen 64 scopeid 0xd
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

 

[dlavigne]

Please create a bug report at bugs.freenas.org and post the issue number here.

 

[Smeeghead]

Bug report created :- Issue #3983

 

[dniq]

I'm seeing the same issue with 10 gigabit Intel X520 NICs :(

dmesg | grep Intel:

Code:

ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15> port 0xfcc0-0xfcdf mem 0xdde80000-0xddefffff,0xddff8000-0xddffbfff irq 40 at device 0.0 on pci3
ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15> port 0xfce0-0xfcff mem 0xddf00000-0xddf7ffff,0xddffc000-0xddffffff irq 44 at device 0.1 on pci3

The card is: "Intel X520 DP 10Gb DA/SFP+ Server Adapter".

 

[Ismael Duarte]

Same here, since 9.2

 

[xaibex]

Same Hardware here (BCM5723). Running 9.2.1.9
Never had any Problems for about 2 Years.

Today a few of this errors show up. And The "Console" from the Web-GUI stopped working. For me it looks like some Bug with the Web-GUI Console/Shell as this Error Message appears only after trying to open the Web-GUI Console.
After Reboot everything was fine again just like before.

 

[russnas]

sorry to bring up an old thread i just realised we are in 2015, googled to find a result , i did a rsync within freenas and the shell window closed, cant open the window - FreeNAS-9.3-STABLE-201505130355 - Intel NIC

Jun 10 16:35:42 Nas kernel: sonewconn: pcb 0xfffffe022c1d93c0: Listen queue overflow: 8 already in queue awaiting acceptance (6 occurrences)

 

[Grogdor]

Also have bge0: <Broadcom NetXtreme Gigabit Ethernet Controller> and got this today on FreeNAS-9.3-STABLE-201601181840, but mine seemed to be triggered by a drive dropping out. There's no encrypted pools, the geli below is the swap partition. Have not seen this during normal/heavy use, just mentioning here for completeness:

Code:

ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD5000AAKS> detached
GEOM_ELI: Device ada0p1.eli destroyed.
GEOM_ELI: Detached ada0p1.eli on last close.
(ada0:ata0:0:0:0): Periph destroyed
...
Jan 28 10:46:36 transmission_1 transmission-daemon[4542]: read failed for "": Device not configured (inout.c:127)
...
sonewconn: pcb 0xffffffffffffffff: Listen queue overflow: 191 already in queue awaiting acceptance (54 occurrences)
...

To read more about kern.ipc.somaxconn mentioned in 3983 go to https://www.freebsd.org/doc/handbook/configtuning-kernel-limits.html (n.b. this sysctl is being replaced in FreeBSD 10...)