From owner-freebsd-questions@freebsd.org Wed Mar 30 07:24:18 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 084D0AE28E4 for ; Wed, 30 Mar 2016 07:24:18 +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 CC6281CE1 for ; Wed, 30 Mar 2016 07:24:17 +0000 (UTC) (envelope-from stdin@niklaas.eu) Received: by box.niklaas.eu (Postfix, from userid 1001) id 73BE861FA9; Wed, 30 Mar 2016 09:24:16 +0200 (CEST) Date: Wed, 30 Mar 2016 09:24:16 +0200 From: Niklaas Baudet von Gersdorff To: freebsd-questions@freebsd.org Subject: Re: www/obhttpd and question marks in sockstat Message-ID: <20160330072416.GB1256@box.niklaas.eu> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459321158.1873218.563290050.42B38184@webmail.messagingengine.com> <56FAFACF.5040404@FreeBSD.org> 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: Wed, 30 Mar 2016 07:24:18 -0000 Matthew Seaman [2016-03-29 22:59 +0100] : > Three hours does seem a little excessive for closing down a listening > socket. Yeah, that's not right. Those already-closed connections > should disappear after a few seconds. Actually, it's also quite odd now > I come to think of it, to see them for the listening socket of a server > process. It's common for them to appear for the point to point link > when a particular client connects and then disconnects -- you can see > the effect in sockstat on either the server or the client machines. > > This is possibly related to the other odd output you've been seeing. > Looks like the obhttpd process is not getting shutdown properly; rather > it seems to be being killed in an excessively brutal way, which prevents > it from cleaning up after itself. Sounds reasonable. > It might be worth trying some alternate web servers. If you want a > pretty bare-bones but fast alternative, I like www/nginx-devel with most > of the port's OPTIONS turned off. > > I know that nginx doesn't normally suffer from anything like this > effect. If you still see it with nginx, then you've good evidence it's > not something to do with a specific httpd implementation, but something > systemic in your server setup. > > Do you see anything similar for any other network servers on your > machine? Assuming, that is, you can afford to turn them off and > on-again a few times while checking. I've already installed www/nginx, started/stopped it, and it works, that is, no "open" ports once I stopped it. So I'm sure that mail/obhttpd is malfunctioning has something to do with mail/obhttpd and not the system. Priyadarshan [2016-03-30 06:59 +0000] : > As alternative to obhttpd, we have been using Caddy with good results. > > It is not on Freshports (yet) but one could get most configurations for > FreeBSD here: https://caddyserver.com/download Wow. Looks interesting. Probably I'll wait until v1.0 and a port though.