My question :
#######################################################################
Hope some out there has some insight.
We have just installed a 4/470 running 4.1.1 w/ 32 Mb of memory
and two IPI (911 mb) disks.
It is designed as a Sybase server/client.
There has been network problems and to further examine these we've
run netstat.
The more netstat is run the more messages similiar to :
tcp 0 0 localhost.1456 localhost.sunrpc TIME_WAIT
are displayed.
#######################################################################
Information that could have been helpful but not included was further
system config info from /etc/install/sys_info
cvms_wtc# more sys_info
hostname=cvms_wtc
sys_type=standalone
ether_name=ie0
ip=137.199.10.11
yp_type=none
domainname=noname
op_type=install
reboot=yes
rewind=no
arch_str=sun4.sun4.sunos.4.1.1
root=id000a
user=id000g
termtype=vt100
timezone=US/Eastern
server=
server_ip=
exec_path=
kvm_path=
The answer :
Apparently, though NIS is not running in this environment, processes are
still spawning, looking for the domain name "noname".
The fix is to null out the domainname by either :
1) # domainname ""
--- or ---
2) edit the /etc/defaultdomain file to reflect a null.
Many thanks for the timely responses of :
"Matt Crawford" <uunet!oddjob.uchicago.edu!matt> who suggested :
Hint: if you use "netstat -n", you don't get those. Now how do you
suppose netstat might be invoking some sort of rpc call? Hmm?
----------------------------------------------------------------------
uunet!allegra.att.com!mp (Mark Plotnick) who again pointed to NIS/YP :
We see that too. We don't run sybase. I think it's caused by the fact
that we don't run yellow pages here, so the gethost* routines do a lot
of unanswered rpc calls. Giving netstat the '-n' option doesn't
produce nearly the amount of sunrpc requests.
----------------------------------------------------------------------
uunet!sunne.East.Sun.COM!stern (Hal Stern - Consultant) who also pointed me to YP
anything talking to sunrpc (may) be talking to NIS.
looks like you're either having problems finding an NIS
server, or your netstat is trying to get info from NIS
and can.
what may be happening is that netstat is looking up
network and host names that are found via DNS, and
the NIS->DNS link is busted, which means that your
netstats are hanging around looking for help.
Thanks to all. Fran.
|\/\/\/|
* Fran Sullivan | |
* fmrco!fxs@uunet.uu.net | |
* Sun Tech Support | (o) (o)
* Fidelity Information Systems C _) ...Hey Dude!
* Boston, MA 02109 | `__|
* ( 617 ) 570-2762 | /
/ \
/ ---- \
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:18 CDT