From owner-freebsd-threads@freebsd.org Tue Jul 5 12:37:23 2016 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3574B7189F for ; Tue, 5 Jul 2016 12:37:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7E9F1CB1 for ; Tue, 5 Jul 2016 12:37:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u65CbN5C027193 for ; Tue, 5 Jul 2016 12:37:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Tue, 05 Jul 2016 12:37:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 12:37:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #122 from Robert Blayzor --- We are still seeing a problem with servers getting hosed up with hundreds a= nd 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 qu= eue awaiting acceptance (34 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (39 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (36 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (37 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (42 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (38 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue awaiting acceptance (39 occurrences) sonewconn: pcb 0xfffff80001b34000: Listen queue overflow: 767 already in qu= eue 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 sel= ect 755 100093 httpd - 3 120 sleep pip= ewr 4220 100124 httpd - 3 120 sleep pip= ewr 6812 100448 httpd - 2 120 sleep pip= ewr 18402 100112 httpd - 0 120 sleep pip= ewr 24419 100122 httpd - 3 120 sleep pip= ewr 24590 100142 httpd - 2 120 sleep pip= ewr 24591 100431 httpd - 3 120 sleep pip= ewr 24592 100095 httpd - 2 120 sleep pip= ewr 24593 100432 httpd - 0 120 sleep pip= ewr 24594 100134 httpd - 2 120 sleep pip= ewr 24595 100052 httpd - 3 120 sleep pip= ewr 24596 100128 httpd - 2 120 sleep pip= ewr 24597 100062 httpd - 2 120 sleep pip= ewr 24598 100047 httpd - 3 120 sleep pip= ewr 24599 100073 httpd - 2 120 sleep pip= ewr 24600 100129 httpd - 0 120 sleep pip= ewr ... webmail3 [~] sudo procstat -at | grep httpd | wc -l 201 --=20 You are receiving this mail because: You are the assignee for the bug.=