HPUX 10.20 : NIS & automount problem

[Raymond Brennan_1]

Hello,

I have a NIS master running on Solaris 8 (Sparc). I also have a number of NIS slaves running on Solaris (Intel).
I have set up a large number of clients which run various flavours of Solaris which work fine. I also have a large number of clients running HPUX 11.00 which run fine. Home directories etc. are all automounted OK, as are other NIS maps. I am happy with the master and slave set-up.

However, I have tow HPUX 10.20 clients who can bind to slaves and see the NIS maps. What they cannot do is to mount them, most notably users' home directories.

If I stop and start the /sbin/init.d/nfs.client on one of the 10.20 servers, here is what I get :

# ./nfs.client start
starting NFS CLIENT networking

starting up the portmapper
portmap already started, using pid: 606
starting up the BIO daemons
/usr/sbin/biod 4
Reading in /etc/exports
starting up the Status Monitor daemon
rpc.statd already started, using pid: 4110
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 4116
starting up the AutoFS daemon
/usr/sbin/automountd -T
Running the AutoFS command interface
/usr/sbin/automount
automount: mount /user: No such device
automount: mount /xfn: No such device
automount: mount /net: No such device
mounting remote NFS file systems ...

The three maps referenced(/user, /xfn and /net) are all in the /etc/auto_master file on the NIS master. All clients mount these Ok except for HPUX 10.20. Why is this ?

Any help/suggestions greatly appreciated.

[Tim D Fulford]

I've got a horrible feeling that you may have covered these...

o My first stab is that are you SURE nothing else is mounted on /user, /xfn & /net...
o Can you mount them just using straight NFS.
o Hows the network....

supply the bdf, auto_master & auto_user,xfn & net maps please. are the auto_user... maps under NIS?

Regards

Tim

[Raymond Brennan_1]

Tim,

The auto_user and other maps are all under NIS. There is nothing local that I want to mount.

Here is the bdf :

Filesystem kbytes used avail %used Mounted on
/dev/root 83733 22621 52738 30% /
/dev/vg00/lvol1 47829 43469 0 100% /stand
/dev/vg00/lvol7 491869 372303 70379 84% /var
/dev/vg00/lvol6 446741 313927 88139 78% /usr
/dev/vg01/lvol3 99669 62368 27334 70% /users
/dev/vg00/lvol5 30597 18965 8572 69% /tmp
/dev/vg01/lvol2 800811 189172 531557 26% /rdbms
/dev/vg00/lvol4 1196821 607825 469313 56% /opt
/dev/vg04/lvol2 498645 63859 384921 14% /maint
/dev/vg00/lvol9 378965 252044 89024 74% /home
/dev/vg02/lvol1 4007201 1912391 1694089 53% /development
/dev/vg05/lvol1 3005449 180701 2524203 7% /data2
/dev/vg04/lvol1 3005449 614937 2089967 23% /data1
/dev/vg03/lvol1 3907177 657684 2858775 19% /ckp_jnl
/dev/vg04/lvol3 498645 89695 359085 20% /cdr
/dev/vg01/lvol4 718037 643112 3121 100% /apps


As you can see, nothing remote.

Here is the "mount" :
/ on /dev/root defaults on Fri Jun 14 03:10:43 2002
/stand on /dev/vg00/lvol1 defaults on Fri Jun 14 03:10:45 2002
/var on /dev/vg00/lvol7 defaults on Fri Jun 14 03:10:53 2002
/usr on /dev/vg00/lvol6 defaults on Fri Jun 14 03:10:53 2002
/users on /dev/vg01/lvol3 defaults on Fri Jun 14 03:10:53 2002
/tmp on /dev/vg00/lvol5 defaults on Fri Jun 14 03:10:53 2002
/rdbms on /dev/vg01/lvol2 defaults on Fri Jun 14 03:10:53 2002
/opt on /dev/vg00/lvol4 defaults on Fri Jun 14 03:10:53 2002
/maint on /dev/vg04/lvol2 defaults on Fri Jun 14 03:10:53 2002
/home on /dev/vg00/lvol9 defaults on Fri Jun 14 03:10:54 2002
/development on /dev/vg02/lvol1 defaults on Fri Jun 14 03:10:54 2002
/data2 on /dev/vg05/lvol1 defaults on Fri Jun 14 03:10:54 2002
/data1 on /dev/vg04/lvol1 defaults on Fri Jun 14 03:10:54 2002
/ckp_jnl on /dev/vg03/lvol1 defaults on Fri Jun 14 03:10:54 2002
/cdr on /dev/vg04/lvol3 defaults on Fri Jun 14 03:10:54 2002
/apps on /dev/vg01/lvol4 defaults on Fri Jun 14 03:10:54 2002
/pure on stamford:/pure ro on Fri Jun 21 06:47:41 2002
/components on stamford:/components ro on Fri Jun 21 06:47:41 2002


There are a few NFS mounts there, but they are done via the /etc/fstab file , not NIS, and work OK.

Here is the auto.master map (from the client) :

ypcat auto.master
auto_user -nobrowse
-xfn
-hosts -nosuid,nobrowse

and here is the auto.user map :

ypcat auto.user
oak:/user/brennanr
oak:/user/houghj

I can see that the automount cannot mount the NIS map directories. However, the client can see and display all NIS maps.
What can you see ?
Thanks for any replies.

[Tim D Fulford]

Hmmm... I've used the auto_master & auto_users in a different way to you, so I'm just going to clarify what I THINK you want as I do it differently.

mount oak:/user/brennar /users/brennar
mount oak:/user/houghj /users/houghj

If this is the case then you might need to re-name /users to /user or do you already have a /user

Whilst this is not part of the question I usually do this

# cat /etc/auto_master
.. (headder stuff)
/users auto_user

# cat /etc/auto_user
* oak:/user/&

This mounts ALL dirs on oak on :/user/

BUT you will not be able to do this because you have /dev/vg01/lvol3 mounted there... Just a thought.

If the above does not help, or is just plain wibble then I think it could be
o Patches
o HP-UX 10.20 might not support this method of mounting (as your other machines do). Instead of using NIS for auto_.., try using files for auto_master & auto_users etc)
o Did you NFS mount oak:... successfully?

Tim

[John Carr_2 · Accepted solution]

Hi Raymond

first you need to clarify if this is an automount problem or a simple mount problem.
Please try manually mounting these file systems from the 10.20 clients as root and as the user. If you succeed then the problem is in fact related to automount but if not then its a mount problem until this has been checked you may be wasting time looking at the automount.

cheers
John.

[sven verhaegen]

hi,

is the auto_master file in any way handeled/distributed by the NIS master server or is it specific to each client ?? if it is NIS originated you might have to see if the map is readable from the client and conatins the correct data, use the ypcat command to do so (see manpage).

If it is a local file then still it depends on user permission etc... wether you can mount and read data , is the mounting done as root or as a user ? there is some difference as the HP-UX implementation considers Rooot user as nothing at all , it guid is -2 so the exports might happen with annon=65534 and root=clientname set on the nfsservers

last but not leasat , name resolving could play a roll , also here NIS could come in to play , can you easily resolve the names of the NFS servers , if not and this is NIS related , then do a ypcat on the hostfile from the NIs server on the client and cHeck the ypbinding ....

thaths some small steps , woith more info we could perhaps continue this

[Steve Labar]

If your you can mount these file systems using standard NFS, I believe your problem is automounter vs. autofs. HP-UX 10.20 uses automounter and HP-UX 11 uses autofs. These two are not compatible. There are patch sets available to upgrade your 10.20 box to use autofs.
Good Luck

Steve

[Tim D Fulford]

Raymond

take a look at this http://66.216.15.50/ITRCForumsEtiquette/

0pts please

Tim

[Raymond Brennan_1]

Thanks to all so far for the suggestions etc.

To the person who directed me to a patronising web page about etiquette etc., I refer you in turn to the Oxford English Dictionary. Look up the word "trust"-it will do you good. I have not been back for a number of days due to a bereavement in my family. This is actually none of your business, but I am telling you anyway in the hope that you will not offend other people in the same way as you have me.

To everyone else,
I have tried a number of things as suggested and have now narrowed it down to an automounter problem. If I run "/usr/sbin/automount" it complains about /user & /net, which are the two NIS maps it gets from the auto.master map. I have copied over /usr/newconfig/etc/rc.config.d/nfsconf to /etc/rc.config.d/nfsconf and stopped and restarted the NFS client and server, but am still getting the same error. I have verified it can be mounted manually.

Any other suggestions ?

[Tim D Fulford]

Now you know it is an automounter/autofs problem it may just be a case of patching..

A quick search for "NFS automountautofs" gave

phne_22877 - NFS/NIS General release/perf. patch
phne_22288 - NFS/NIS Gen Rel/perf patch
phco_22268 - Cumu SAM/ObAM patch
phne_15159 - nsswitch.conf patch for automounter

Tim

[Raymond Brennan_1]

Thanks to all, the problem has now been fixed. I simply removed the options from "AUTOMOUNT" and set "AUTOFS"=1 in /etc/rc.config.d/nfsconf. After a reboot, the server worked fine.

[K.Srinivasan]

Hi ,

I have received hp server from onsite.

So project purpose i have added entry in the /etc/fstab for mounting

after sometimes old entry will displayed on mount points.

How can i resolv this.

Thanks,
Srini.