Date: Fri, 7 Jul 1995 03:38:08 -0400 (EDT) From: "Kenneth D. Merry" <ken@rflab1.gtri.gatech.edu> To: freebsd-bugs@freebsd.org Subject: strange netstat errors Message-ID: <199507070738.DAA24977@rflab1.gtri.gatech.edu>
next in thread | raw e-mail | index | archive | help
I've been getting occasional strange error messages from netstat,
usually something like this: (this is under 2.0.5)
----
Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 wc206.auth wc115.1123 TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 localhost.1684 localhost.domain TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 0.6.0.20.32512 *.* TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 localhost.1683 localhost.domain TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 0.193.0.2.33152 40.0.0.0.56418 TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 76.1.5.0.4352 60.0.0.0.56418 TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 1.1.1.1.257 48.0.0.0.* TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 1.1.1.1.257 48.0.0.0.* TIME_WAIT
netstat: kvm_read: kvm_read: Bad address
netstat: kvm_read: kvm_read: Bad address
tcp 0 0 0.6.0.20.32512 *.* TIME_WAIT
udp 0 0 localhost.domain *.*
udp 0 0 wc206.domain *.*
----
System: 486/100, 3c509 combo
2.0.5-ALPHA with a 2.0.5-RELEASE kernel
The version of netstat I'm using, however, is from current as of
June 22. As far as I can tell, it hasn't changed since.
I've gotten similar errors on a friend's machine (running 2.0.5R)
who also has a 3c509 combo. (his netstat is from 2.0.5R) I'm not running
anything really net-intensive. I am running named, though, if that makes
a difference. I don't have anyone (that I know of) using my box as a
nameserver, though. I increased NMBCLUSTERS to 4096, in an attempt to get
rid of the errors, but it didn't have any effect. My friend's box is
using the stock number of NMBCLUSTERS, with 30 users declared, and I saw
the same errors there. The above kvm_read errors occur randomly (at least
as far as I can tell) and they don't occur very often.
Another strange thing I've noticed with netstat is that it is much
slower in printing out individual entries now than it was under 2.0 or
1.x. I've got a 2.0 and a 1.1 box sitting around (yeah, I know they're
old) and the output from netstat comes out significantly faster. I think
it has something to do with the speed of resolving ip addresses to
hostnames, because netstat -n is a good bit faster. The speed of
netstat's output doesn't seem to be affected in any way by running a local
copy of named.
Oh yeah, one other strange thing with netstat -- netstat -f unix
doesn't produce any output. (and just plain 'netstat' doesn't produce
any "Active UNIX domain sockets", like it did before 2.0.5)
My guess is that I'm missing something here....would someone care
to tell me what's going on? :)
Thanks,
Ken
--
Kenneth Merry
ken@rflab1.gtri.gatech.edu
Disclaimer: I don't speak for GTRI, GT, or Elvis.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507070738.DAA24977>