From nobody@FreeBSD.org  Wed Apr 25 14:14:28 2012
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CB2961065672
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 25 Apr 2012 14:14:28 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 9E0908FC21
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 25 Apr 2012 14:14:28 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q3PEESEe027770
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 25 Apr 2012 14:14:28 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id q3PEER3G027759;
	Wed, 25 Apr 2012 14:14:27 GMT
	(envelope-from nobody)
Message-Id: <201204251414.q3PEER3G027759@red.freebsd.org>
Date: Wed, 25 Apr 2012 14:14:27 GMT
From: Alexander <st41ker@yandex.ru>
To: freebsd-gnats-submit@FreeBSD.org
Subject: sockstat(1) missing output
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         167292
>Category:       bin
>Synopsis:       sockstat(1) missing output
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jilles
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 25 14:20:06 UTC 2012
>Closed-Date:    Sun Apr 29 23:10:33 UTC 2012
>Last-Modified:  Sun Apr 29 23:10:33 UTC 2012
>Originator:     Alexander
>Release:        8.3-RELEASE
>Organization:
>Environment:
FreeBSD ferry-n1.megacom.ua 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Mon Apr  9 21:23:18 UTC 2012     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
After the binary upgrade from 8.2 to 8.3 I've noticed that sockstat started getting ? ? ? in its output.

I have no idea which exactly sockets are messing this out, it could be some kernel or sockstat(1) problem.

Example:


root     rpcbind    1122  12 tcp4   127.0.0.1:111         *:*
root     rpcbind    1122  13 tcp4   192.168.255.253:111   *:*
bind     named      1115  3  dgram  -> /var/run/logpriv
bind     named      1115  20 tcp4   192.168.255.253:53    *:*
bind     named      1115  21 tcp4   127.0.0.1:53          *:*
bind     named      1115  22 tcp4   193.28.177.4:53       *:*
bind     named      1115  23 tcp4   193.28.177.8:53       *:*
bind     named      1115  24 tcp4   193.28.177.2:53       *:*
bind     named      1115  25 tcp4   127.0.0.1:953         *:*
bind     named      1115  512 udp4  192.168.255.253:53    *:*
bind     named      1115  513 udp4  127.0.0.1:53          *:*
bind     named      1115  514 udp4  193.28.177.4:53       *:*
bind     named      1115  515 udp4  193.28.177.8:53       *:*
bind     named      1115  516 udp4  193.28.177.2:53       *:*
root     syslogd    1028  4  dgram  /var/run/log
root     syslogd    1028  5  dgram  /var/run/logpriv
root     syslogd    1028  6  dgram  /var/run/log
root     syslogd    1028  7  dgram  /var/named/var/run/log
root     syslogd    1028  8  udp6   *:514                 *:*
root     syslogd    1028  9  udp4   *:514                 *:*
root     devd       783   4  stream /var/run/devd.pipe
?        ?          ?     ?  tcp4   193.28.177.4:53452    193.28.177.2:3306
?        ?          ?     ?  tcp4   193.28.177.4:53959    193.28.177.2:3306
?        ?          ?     ?  tcp4   127.0.0.1:28521       127.0.0.1:10023
?        ?          ?     ?  stream -> ??
?        ?          ?     ?  udp6   *:2049                *:*
?        ?          ?     ?  udp6   *:736                 *:*
?        ?          ?     ?  udp4   *:2049                *:*
?        ?          ?     ?  tcp4   *:639                 *:*
?        ?          ?     ?  stream -> ??
?        ?          ?     ?  tcp4   192.168.255.253:823   192.168.255.249:2049
?        ?          ?     ?  udp4   *:825                 *:*
?        ?          ?     ?  udp6   *:881                 *:*
?        ?          ?     ?  tcp6   *:925                 *:*
?        ?          ?     ?  stream -> ??
?        ?          ?     ?  tcp4   192.168.255.253:1006  192.168.255.249:2049
?        ?          ?     ?  udp4   *:*                   *:*
?        ?          ?     ?  stream -> ??

>How-To-Repeat:
Just run the sockstat program.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jilles 
State-Changed-When: Sun Apr 29 23:09:08 UTC 2012 
State-Changed-Why:  
The question marks in sockstat are intended behaviour and not a bug. 

The change between 8.2 and 8.3 is that sockstat now also shows 
sockets that are not associated with a file descriptor. 
Formerly, these were not shown, causing a discrepancy between 
sockstat and netstat -a because netstat has always shown them. 

In your case, the sockets on port 2049 are associated with the 
kernel NFS client and server. The other TCP sockets are likely 
in TIME_WAIT or a similar state. 


Responsible-Changed-From-To: freebsd-bugs->jilles 
Responsible-Changed-By: jilles 
Responsible-Changed-When: Sun Apr 29 23:09:08 UTC 2012 
Responsible-Changed-Why:  
I closed it. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=167292 
>Unformatted:
