sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow:

[avalon60]

I have been getting a lot of emails over the last 10 days or so from my FreeNAS-9.10.2-U6 (561f0d7a1) server as a freenas.daily security run output. I have upto now ignored them.
And this is what it showing:

freenas.local kernel log messages:

sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow: 151 already in queue awaiting acceptance (3 occurrences)
There are many lines of what look to be the same with the exception of the number of occurences.

I think this is to do with the nic , and having trouble keeping up, from what I have seen about this problem.
My motherboard is the Supermicro X9SCM(-F) with onboard NIC, and the cpu is Intel Xeon E3-1240v2 CPU 8M Cache 3.4GHz, and Kingston Value Ram 16GB ECC Server Ram DDR3 1666MHz.

Should I be worried about these messages, or ignore them as before.

 

[m0nkey_]

Do you have any jails running? Specifically anything that creates a lot of connections, like BitTorren?

 

[avalon60]

Thanks for getting back to me, and yes I have 3 jails, 1 being emby_server, 2nd is Plex, and the other being miniDLNA, which I don't really use. Emby and Plex are the main ones I do use

 

[m0nkey_]

I would suggest restarting your jails and watch /var/log/messages for the next 24 hours to see if it stops.

 

[avalon60]

That seems to have stopped the multiple messages about
Oct 25 14:17:56 freenas kernel: sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow: 151 already in queue awaiting acceptance $

An now this:

Oct 25 14:18:23 freenas kernel: arp: 192.168.0.5 moved from 02:ff:20:00:06:0a to 0c:c4:7a:0c:1e:ef on epair1b
Oct 25 14:18:34 freenas kernel: epair1a: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: epair1a: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: epair1b: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: epair1b: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: em0: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: em0: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: em0: promiscuous mode disabled
Oct 25 14:18:34 freenas kernel: bridge0: link state changed to DOWN
Oct 25 14:18:34 freenas kernel: bridge0: link state changed to DOWN
Oct 25 14:18:38 freenas kernel: em0: link state changed to UP
Oct 25 14:18:38 freenas kernel: em0: link state changed to UP
Oct 25 14:18:38 freenas bridge0: Ethernet address: 02:77:f9:17:40:00
Oct 25 14:18:38 freenas kernel: em0: promiscuous mode enabled
Oct 25 14:18:38 freenas kernel: bridge0: link state changed to UP
Oct 25 14:18:38 freenas kernel: bridge0: link state changed to UP
Oct 25 14:18:38 freenas epair0a: Ethernet address: 02:ff:20:00:05:0a
Oct 25 14:18:38 freenas epair0b: Ethernet address: 02:ff:70:00:06:0b
Oct 25 14:18:38 freenas kernel: epair0a: link state changed to UP
Oct 25 14:18:38 freenas kernel: epair0a: link state changed to UP
Oct 25 14:18:38 freenas kernel: epair0b: link state changed to UP
Oct 25 14:18:38 freenas kernel: epair0b: link state changed to UP
Oct 25 14:18:38 freenas kernel: epair0a: promiscuous mode enabled

 

[avalon60]

The multiple messages about
Oct 25 14:17:56 freenas kernel: sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow: 151 already in queue awaiting acceptance $
have now stopped,

but now these messages:
Oct 25 19:08:27 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Oct 25 19:08:27 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Oct 25 20:08:38 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Oct 25 20:08:38 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name

Are these messages related to the motherboard etc at all.

 

[m0nkey_]

Are these messages related to the motherboard etc at all.

Those messages can be ignored.

 

[avalon60]

I got another email from my FreeNAS box earlier, and there is a mixture of different messages. The soneconn messages were included but they may have been from before I restarted the Jails.

From the first line of the email, many lines of this:
fstab: /etc/fstab:2: Inappropriate file type or format

Then these:
freenas.local changes in mounted filesystems:
1d0
< /mnt/WinShare/Media/Music /mnt/Backup_Data/jails/MiniDLNA/media/music nullfs rw 0 0
35d33
< devfs /mnt/Backup_Data/jails/MiniDLNA/dev devfs rw,multilabel 0 0
40d37
< procfs /mnt/Backup_Data/jails/MiniDLNA/proc procfs rw 0 0


Then these again:
freenas.local kernel log messages:

sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow: 151 already in queue awaiting acceptance (12 occurrences)
sonewconn: pcb 0xfffff801ba3bf310: Listen queue overflow: 151 already in queue awaiting acceptance (10 occurrences)

I have also just checked the /var/log/messages, and there is nothing showing this morning about the above messages.