topic Re: automout issue in Operating System - HP-UX

automout issue

Asya — Wed, 02 Aug 2006 14:21:34 GMT

Hi,

I've added a new automount point on our solaris NIS+ master. In other words, I've created an automount to /emc, which should mount to my home directory /emc/lisansa

It works just fine on NFS solaris server.

When i go to our HP server, it doesn't.

This is from Solaris server:

bash-2.05# niscat auto_emc.org_dir |grep lisansa
lisansa buildvault-p2.smarts.com:/dev001/&

On HP server the same command doesn't produce any results.

This is from messages:
Aug 2 15:13:40 glorious automountd[27993]: nis_list: NIS+ error Not found encountered on name auto_emc.org_dir.domain.com. in table auto_emc.org_dir.domain.com.'s path.

Do you know why this is happening..? Did i forget to run a command?

The thing is...it did create /emc directory after i restarted NFS on the client, but i can't get to my home directory.

Thank you.

Re: automout issue

Victor Fridyev — Wed, 02 Aug 2006 14:36:36 GMT

Hi,

Do you mean that auto_master file is one of NIS maps ?

In this case you have to check whether in /etc/rc.config.d/nfsconf
NFS_CLIENT=1
AUTOMOUNT=1

and parameters
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"

are correct.

Agter that you have to restart NFS client:

/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start

HTH

Re: automout issue

Asya — Wed, 02 Aug 2006 15:05:15 GMT

No no...automount works just fine. I can mount to other places without any problems.

it seems like the problem has to do with NIS+ permissions...

# niscat -o auto_misc.org_dir
Object Name : "auto_misc"
Directory : "org_dir.company.com."
Owner : "just.smarts.com."
Group : "nisadmin.company.com."
Access Rights : r---rmcdrmcdr---
Time to Live : 12:0:0
Creation Time : Sun Dec 22 23:34:02 2002
Mod. Time : Sun Dec 22 23:34:02 2002
Object Type : TABLE
Table Type : automount_map
Number of Columns : 2
Character Separator :
Search Path :
Columns :
[0] Name : key
Attributes : (SEARCHABLE, TEXTUAL DATA, CASE SENSITIVE)
Access Rights : r---rmcdrmcdr---
[1] Name : value
Attributes : (TEXTUAL DATA)
Access Rights : r---rmcdrmcdr---
# niscat -o auto_emc.org_dir
Object Name : "auto_emc"
Directory : "org_dir.company.com."
Owner : "just.company.com."
Group : ""
Access Rights : ----rmcdr---r---
Time to Live : 12:0:0
Creation Time : Tue Aug 1 08:55:08 2006
Mod. Time : Tue Aug 1 08:55:08 2006
Object Type : TABLE
Table Type : automount_map
Number of Columns : 2
Character Separator :
Search Path :
Columns :
[0] Name : key
Attributes : (SEARCHABLE, TEXTUAL DATA, CASE SENSITIVE)
Access Rights : ----rmcdr---r---
[1] Name : value
Attributes : (SEARCHABLE, TEXTUAL DATA, CASE SENSITIVE)
Access Rights : ----rmcdr---r---

I just need to figure out how to change all that...

Re: automout issue

Dave Olker — Wed, 02 Aug 2006 15:17:42 GMT

Hi Asya,

You say you can niscat the automount map and see the entry for lisansa just fine on the Solaris system. Does the same command return the same results from the HP-UX system? That would at least show whether the HP-UX NFS client can see the map entry in the proper syntax.

Once we know that you can try turning on extensive debug AutoFS logging and try the failing mount again so that I can see the log file entries made during the mount.

To enable/disable debug logging of AutoFS, send the running automountd pid a SIGUSR2 signal. This will cause logging to start in the /var/adm/automount.log file. If you can reproduce the failing mount with debug logging enabled, I'd be happy to look at the log file to see what AutoFS thinks is happening.

Again, the first thing to verify is the niscat stuff on the HP-UX box.

Regards,

Dave

Re: automout issue

Asya — Thu, 03 Aug 2006 13:45:20 GMT

It's actually working fine now. I think it just needed time to fully work. Thank you everyone.