From owner-freebsd-questions@freebsd.org Tue Mar 29 16:51:14 2016 Return-Path: Delivered-To: freebsd-questions@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 39AA7AE275C for ; Tue, 29 Mar 2016 16:51:14 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: from box.niklaas.eu (unknown [IPv6:2a00:c98:2200:af07:6::1]) by mx1.freebsd.org (Postfix) with ESMTP id 092151A03 for ; Tue, 29 Mar 2016 16:51:13 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: by box.niklaas.eu (Postfix, from userid 1001) id 20B3761FBB; Tue, 29 Mar 2016 18:51:12 +0200 (CEST) Date: Tue, 29 Mar 2016 18:51:12 +0200 From: Niklaas Baudet von Gersdorff To: freebsd-questions@freebsd.org Subject: Re: www/obhttpd and question marks in sockstat Message-ID: <20160329165112.GA9259@box.niklaas.eu> Mail-Followup-To: freebsd-questions@freebsd.org References: <20160329112840.GA5801@box.niklaas.eu> <56FA6F86.3040302@infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56FA6F86.3040302@infracaninophile.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2016 16:51:14 -0000 Thank your for your explanation. Matthew Seaman [2016-03-29 13:05 +0100] : > Looks like the obhttpd process is trying to kill of its children > individually, but they've all already been killed. Possibly by a signal to > the whole process group. It's untidy, but it has achieved your aim of > killing the obhttpd processes. So there's nothing I must worry about. Maybe I'll take a closer look on it, see whether I can improve the init script, and submit a bug report. > This connection is already closed. You can tell by the question marks. It > only still exists in the sockstat output as the kernel is hanging onto the > connection details so it can reap any stray packets that may, belatedly, > arrive. If you wait patiently, these lines will eventually disappear from > the sockstat output. Or you can just restart the daemon anyhow -- it should > come up normally. So there's nothing to worry about too. Nonetheless, I'm wondering: After more than three hours, the output is still the same? I just started www/obhttpd again and got the following: USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS www obhttpd 9308 4 tcp4 10.15.1.1:80 *:* www obhttpd 9307 4 tcp4 10.15.1.1:80 *:* www obhttpd 9305 4 tcp4 10.15.1.1:80 *:* root syslogd 4654 6 udp6 2a00:c98:2200:af07:6:0:1:1:514 *:* root syslogd 4654 7 udp4 10.15.1.1:514 *:* ? ? ? ? tcp6 2a00:c98:2200:af07:6:0:1:1:80 *:* ? ? ? ? tcp4 10.15.1.1:80 *:* ? ? ? ? tcp6 2a00:c98:2200:af07:6:0:1:1:80 *:* So it seems that www/obhttpd has problems binding again on IPv6 while IPv4 works fine. Stopping and starting again gives me an additional "closed" port on IPv6: USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS www obhttpd 9355 4 tcp4 10.15.1.1:80 *:* www obhttpd 9354 4 tcp4 10.15.1.1:80 *:* www obhttpd 9352 4 tcp4 10.15.1.1:80 *:* root syslogd 4654 6 udp6 2a00:c98:2200:af07:6:0:1:1:514 *:* root syslogd 4654 7 udp4 10.15.1.1:514 *:* ? ? ? ? tcp6 2a00:c98:2200:af07:6:0:1:1:80 *:* ? ? ? ? tcp6 2a00:c98:2200:af07:6:0:1:1:80 *:* ? ? ? ? tcp4 10.15.1.1:80 *:* ? ? ? ? tcp6 2a00:c98:2200:af07:6:0:1:1:80 *:* Something's not working properly here, is it?