SUMMARY: Automount problems

From: Sean Ward (seanw@amgen.com)
Date: Mon Feb 28 1994 - 02:05:16 CST


I don't think anyone got this. If this a duplicate, apologies in advance.
        sean

Sorry for the delay in my summary. You know how busy us sysadmins are...
 
 
Here's my original message:
 
> I've run across an interesting problem that I can't seem to fix. I have a
> Sparc Classic running Solaris 2.3 (upgraded today from 2.2). It's /var/mail is
> supposed to be mounted from a 4/690 running 4.1.3 (recently upgraded from
> 4.1.2). When the 690 was running 4.1.2, there were no problems. However, once> we upgraded the 690 to 4.1.3, I've been getting the following messages:
 
> Dec 22 15:04:01 belgarath automountd[312]: mount usops:/var/spool/mail: Couldn't bind to reserved port
 
> My auto_direct is nothing special:
 
> belgarath{seanw}101: cat /etc/auto_direct
> /var/mail -rw,hard,intr usops:/var/spool/mail
> /usr/local/share -rw,hard,intr usops:/share
 
> I get the same message about usops:/share as well.
> The problem hasn't gone away since I upgraded the Classic to 2.3.
 
> I get a similar message when trying to use the mount command.
 
> belgarath{root}/ >mount usops:/var/spool/mail /var/mail
> nfs mount: Couldn't bind to reserved port
> nfs mount: retrying: /var/mail
> nfs mount: Couldn't bind to reserved port
> ^C
 
I got the following suggestions:

1. Mount /var/spool/mail onto /var/mail via /etc/vfstab. I tried that and the
machine hung on bootup with the same message.

2. Check the port numbers for nfsd and mountd. nfsd should be on port 2049 and
mountd should be on a port less than 1024. An rpcinfo found this to be okay.

3. See if anything was under /var/mail on my machine. There wasn't.

4. There might be a patch that turns off reserved port checking. I checked
our sunsolve cd, and I there were two bugs, one which reported this problem
with automounts, and one with nfs mounts. Unfortunately, neither one of them
resulted in a patch (at least on the cd). In fact, the text on the automount
bug simply said that it would eventually mount through retries (!).

Since that time, I've become the NIS+ guinea pig as well, and 2.x machines
running NIS+ can't nfs mount directories from a 1.x machine runnins NIS
(strange eh?). Ergo, this problem has been put on the back burner for now.
However, now that I have some patch ID's, I can bug Sun if this becomes a
problem again.

Many thanks to those who responded:

fallan@mulga.awadi.com.AU (Frank Allan (Network Mgr))
birger@sdvest.vest.sdata.no (Birger A. Wathne)
john@oncology.uthscsa.edu (John Justin Hough)
mcostel@kaman.com (Mark Costello)
lacoursj@uprc.com (Jeffrey D. LaCoursiere)
Dan Stromberg - OAC-DCS <strombrg@hydra.acs.uci.edu>

Cheers,

=============================================================================
Sean Ward +1-805-447-1774 voice
Systems Dude +1-805-499-9096 fax
Amgen Center seanw@amgen.com
Thousand Oaks, CA 91320-1789 USA ...uunet!amgen!seanw

"Hopelessly lost, but making good time..." - Letterman
=============================================================================



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:57 CDT