- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: automout issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 07:21 AM
тАО08-02-2006 07:21 AM
automout issue
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 07:36 AM
тАО08-02-2006 07:36 AM
Re: automout issue
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 08:05 AM
тАО08-02-2006 08:05 AM
Re: automout issue
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2006 08:17 AM
тАО08-02-2006 08:17 AM
Re: automout issue
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
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2006 06:45 AM
тАО08-03-2006 06:45 AM