[Bug 209471] Listen queue overflow due to too many sockets stuck in CLOSED state

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209471

y2wjegieo8c2 at opayq.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |y2wjegieo8c2 at opayq.com

--- Comment #22 from y2wjegieo8c2 at opayq.com ---
I am facing the same issue with Freebsd 11.2 (freenas machine).
In the log I have this:
Aug 18 18:50:19 freenas ctld[2680]: 192.168.0.122: exiting due to timeout
Aug 18 18:50:19 freenas ctld[2683]: 192.168.0.122: exiting due to timeout
Aug 18 18:50:19 freenas ctld[2679]: 192.168.0.122: exiting due to timeout
Aug 18 18:50:19 freenas ctld[2681]: 192.168.0.122: exiting due to timeout
Aug 18 18:50:19 freenas ctld[2682]: 192.168.0.122: exiting due to timeout
sonewconn: pcb 0xfffff80045e88ae0: Listen queue overflow: 193 already in queue
awaiting acceptance (1 occurrences)
sonewconn: pcb 0xfffff80045e88ae0: Listen queue overflow: 193 already in queue
awaiting acceptance (322 occurrences)
sonewconn: pcb 0xfffff80045e88ae0: Listen queue overflow: 193 already in queue
awaiting acceptance (340 occurrences)
sonewconn: pcb 0xfffff80045e88ae0: Listen queue overflow: 193 already in queue
awaiting acceptance (340 occurrences)

netstat -Lan reported the issue about the port 3260 (iscsi)
It seems to happened while I try to rename a ZVOL (zfs rename ...)

I tried to stop the iscsi service from the GUIwith no luck:
/etc/rc.d/ctld stop did not produce any effect (process was stuck)
I tried to kill the process manually: (2281 is for /usr/sbin/ctld) 
kill -9 2481
kill -HUP 2481
kill -KILL 2481
kill -19 2481
but no luck.

For a strange reason: /etc/rc.d/ctld stop returned:
ctld not running? (check /var/run/ctld.pid). (the service was definitely
running)

ps aux | awk '$8=="Z" {print $2}' returns nothing

At the end, I rebooted the VM (I had to force the poweroff as I was getting
extra message on the console about sonewconn after the sync message)

Hope it helps

-- 
You are receiving this mail because:
You are the assignee for the bug.