Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Mar 2016 18:51:12 +0200
From:      Niklaas Baudet von Gersdorff <stdin@niklaas.eu>
To:        freebsd-questions@freebsd.org
Subject:   Re: www/obhttpd and question marks in sockstat
Message-ID:  <20160329165112.GA9259@box.niklaas.eu>
In-Reply-To: <56FA6F86.3040302@infracaninophile.co.uk>
References:  <20160329112840.GA5801@box.niklaas.eu> <56FA6F86.3040302@infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
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?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160329165112.GA9259>