[Bug 204426] Processes terminating cannot access memory
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jul 5 12:37:24 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426
--- Comment #122 from Robert Blayzor <rblayzor at inoc.net> ---
We are still seeing a problem with servers getting hosed up with hundreds and
hundreds of sockets in a CLOSED state... I've experienced this with two
different Apache2.4 servers... Both times, almost identical issue...
dmesg
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (34 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (39 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (36 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (37 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (42 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (38 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (39 occurrences)
sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in queue
awaiting acceptance (36 occurrences)
...
webmail3 [~] netstat -an | grep " CLOSED"
tcp4 113 0 127.0.0.1.80 127.0.0.1.14511 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.26064 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.57807 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.39385 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.22623 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.65280 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.27494 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.12996 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.59834 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.32036 CLOSED
tcp4 113 0 127.0.0.1.80 127.0.0.1.34364 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.35467 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.28605 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.21232 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.48099 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.65026 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.54254 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.35803 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.11435 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.46650 CLOSED
tcp6 0 0 2607:f058:110:3:.80 2607:f058:110:3:.7447 CLOSED
...
webmail3 [~] netstat -an | grep " CLOSED" | wc -l
980
webmail3 [~] sudo procstat -at | grep httpd
699 100076 httpd - 0 120 sleep select
755 100093 httpd - 3 120 sleep pipewr
4220 100124 httpd - 3 120 sleep pipewr
6812 100448 httpd - 2 120 sleep pipewr
18402 100112 httpd - 0 120 sleep pipewr
24419 100122 httpd - 3 120 sleep pipewr
24590 100142 httpd - 2 120 sleep pipewr
24591 100431 httpd - 3 120 sleep pipewr
24592 100095 httpd - 2 120 sleep pipewr
24593 100432 httpd - 0 120 sleep pipewr
24594 100134 httpd - 2 120 sleep pipewr
24595 100052 httpd - 3 120 sleep pipewr
24596 100128 httpd - 2 120 sleep pipewr
24597 100062 httpd - 2 120 sleep pipewr
24598 100047 httpd - 3 120 sleep pipewr
24599 100073 httpd - 2 120 sleep pipewr
24600 100129 httpd - 0 120 sleep pipewr
...
webmail3 [~] sudo procstat -at | grep httpd | wc -l
201
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-threads
mailing list