Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!news.kei.com!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul From: wpaul@ctr.columbia.edu (Bill Paul) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FBSD 2.0.5R: "Port mapper failure" and NFS lockups Date: 1 Jul 1995 04:28:55 GMT Organization: Columbia University Center for Telecommunications Research Lines: 61 Message-ID: <3t2iu7$dpa@sol.ctr.columbia.edu> References: <1995Jun30.214222.10887@tellab5.tellabs.com> NNTP-Posting-Host: startide.ctr.columbia.edu X-Newsreader: TIN [version 1.2 PL2] Daring to challenge the will of the almighty Leviam00se, Mike Borowiec (mikebo@tellabs.com) had the courage to say: : Greetings - : I'm running FreeBSD 2.0.5R on a 16MB Dell 486/50DX2. I'm using Yellow : Pages (NIS) and NFS. I've a Novell NE2000 Plus and have an Adaptec : AHA1542CF SCSI controller. Nothin' much else, but see my dmesg output : at the end of this... I would ditch the NE2000 in favor of an SMC Elite Combo or practically anything els; the ed driver runs NE2000 in programmed I/O mode. That's not your problem though. : I haven't changed anything significant over the past few days of solid : running, so I'm concerned by my machine locking up solid during periods : of intense NFS activity - during software builds for example. When I : reboot, I get the message: : clnttcp_create: RPC: Port mapper failure - RPC: Unable to receive : once after the line: : add net default gateway : and twice more after the line: : add net 224.0.0.0 I'm pretty sure the RPC error you're seeing is coming from the NIS routines inside libc (I've seen them a lot durnig debugging). If something's causing RPC problems, it would make sense that both NFS and NIS would be affected. I have a sneaky suspicion that this is yet another routing problem. (I've already answered a couple other posts with the words 'Kill routed!' -- it would just figure of that's the answer in this case too.) If somebody suddenly started broadcasting different rounting information on your network, routed on your FreeBSD box would detect it and cheerfully alter your routing tables for you. If the routing changes make your NFS server unreachable, it would certainly hang your mounts. This is a guess though. You'd have to play around a bit to see if this is actually the problem. If you can still ping the server at both its interfaces, then it's something else. Hope this helps. -Bill : -------------------------------------------------------------------------- : Michael Borowiec Network Operations Tellabs Operations, Inc. : mikebo@TELLABS.COM 1000 Remington Blvd. MS109 : 708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440 : -------------------------------------------------------------------------- -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~