[comp.sys.sun] Problems with SunOS 4.0.1, YP, and NFS mounting

ejs@goldhill.com (04/21/89)

cmcmanis@sun.com (Chuck McManis):
   Try this out :

   Bring your machine up single user and run portmap, then start ypserv,
   and do *two* things. Type domainname to see what your machine thinks
   the domain name is, then type "ls -ld /var/yp/`domainname`" to see if
   your machine really serves your domain. [Note that a common error
   here is to change the spelling, that is making a directory called
   sun.com and setting your domainname to sun.COM, this won't work.]

I brought the machine up single user (after first halting all the other
Suns on our network in case they might interfere by making NFS/RPC
requests).  Although I new that /bin/domainname is executed in rc.local
*before* portmap and ypserv are started, I followed your directions.  I
started portmap and ypserv.  I then typed "domainname" and was rewarded
with an empty string.  So I typed "domainname goldhill.com" to set the
domainname.  Then I typed "ls -ld /var/yp/`domainname`" and had the
directory "/var/yp/goldhill.com" listed on my console.  (Note that this
stuff had to work since we were able to use YP from our clients despite
our hanging problem).  

   Now, type ypbind and follow it with a ypset <your ip address>. Then
   type ypwhich. This should tell you if the bind and the subsequent
   ypset was successful. If not the ypwhich will return domain <your name>
   not bound. (It tried to ping the ypserv you started). If that is the
   case then you should make sure that the domain directory is readable
   (and /var and /var/yp are searchable). 

I typed ypbind, "ypset 128.168.1.211", and "ypwhich".  ypwhich printed
"goddard" which is the same as "hostname" would have printed/returned.

   Now try rpcinfo -p and you should get rpcinfo, ypbind, and ypserv as
   registered services. If this doesn't work report back what happened 
   and we can follow up from there.

Then I typed "rpcinfo -p" and this command hung.  Nothing new here.

So I changed the order a bit.  I booted single user and typed:


	domainname goldhill.com
	rpcinfo -p
	;; this hung.

It seems to me, one time in the past (under 3.5) I have typed "rpcinfo -p"
before starting up "portmap" and was given an error message indicating
that my attempt to contact the portmapper failed.  This is what I expected
during the above test.  Why doesn't "rpcinfo" fail if it can't contact the
"portmap" daemon?

So I tried another test.  I rebooted single user to ensure that my
previous tests wouldn't affect things, and typed:

	domainname goldhill.com
	portmap
	rpcinfo -p
	;; this hung

It also seems to me that this has worked differently in the past.  I
expected two (maybe three) lines of output which would indicate that there
were two ports associated with portmapper.  So already something is wrong
here.

Help?

Eric Swenson
Gold Hill Computers, Inc.
(617) 621-3405

ejs@goldhill.com (04/22/89)

dbd%benden@lanl.gov (Dan Davison):
   ... 
   I went thru the problems described here when we "upgraded" to 4.0.  After
   much suffering with the hotline we got working binaries of portmap,
   ypbind, and ypserv.  The magic combination:

   benden:/usr/etc[6]:sum ypbind ypserv portmap
   65054    16 ypbind
   28961    40 ypserv
   26206    16 portmap

I just checked our checksums for the above three programs running under a
vanilla SunOS 4.0.1 release and they match.

   The portmapper with the checksum of 26206 16 may also work.

What's the difference between this checksum and the one above?

   ...

   If anyone wants more info I'd try to help.

I would like more info, and help, if possible.  Thanks. 

Eric Swenson
Gold Hill Computers, Inc.
(617) 621-3405

dbd%benden@lanl.gov (Dan Davison) (04/22/89)

>> The portmapper with the checksum of 26206 16 may also work.

> What's the difference between this checksum and the one above?


A typo.  Originally the checksum of the portmapper that worked was 53902
24, and that's what I had written.  I then remembered that I changed it
for some reason and did the "sum" that I posted.  Use the 26206 16
version; I had a problem with the 53902 24 under some circumstances that I
can't recall now.


BTW, I only set the ifconfig lines in rc.boot.  Experimentation showed
that the setting in rc.local didn't always work.

dan davison
theoretical biology and biophysics
t-10 ms k710
los alamos national laboratory
los alamos, nm 87545 USA
dd@lanl.gov
505-665-1355

ejs@goldhill.com (04/22/89)

Ok, it looks like I'm using the correct versions of ypbind, ypserv, and
portmap and I'm still having the same problems.