HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- autofs problem
Operating System - HP-UX
1830868
Members
1808
Online
110017
Solutions
Forums
Categories
Company
Local Language
back
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
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
02-11-2009 07:20 PM
02-11-2009 07:20 PM
HI
i am having NIS master server and i am having one NIS slave,
i had shared out two drive from NIS slave thorugh AMD (autofs) for few stations, i had verified on station all configuration looks ok, below few stuff i had verified at workstation.
/etc/auto_* all ok
ypcat -k = able to get that drive
rpcinfo -p = portmapper is working.
what should be issue, please guide me on this, thanks in advance for your help.
i am having NIS master server and i am having one NIS slave,
i had shared out two drive from NIS slave thorugh AMD (autofs) for few stations, i had verified on station all configuration looks ok, below few stuff i had verified at workstation.
/etc/auto_* all ok
ypcat -k = able to get that drive
rpcinfo -p = portmapper is working.
what should be issue, please guide me on this, thanks in advance for your help.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2009 12:12 AM
02-12-2009 12:12 AM
Solution
hello,
Can you provide us with the output of :
rpcinfo -p
have you tried a showmount -e from your client ?
What's in the log file on the client in /var/adm/automount.log ?
What you can do is to enable tracing by modifying the line :
AUTOMOUNTD_OPTIONS="-T" in /etc/rc.config.d/nfsconf
and stop/start the daemon.
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start
hope this helps
kenavo
Pat.
Can you provide us with the output of :
rpcinfo -p
have you tried a showmount -e
What's in the log file on the client in /var/adm/automount.log ?
What you can do is to enable tracing by modifying the line :
AUTOMOUNTD_OPTIONS="-T" in /etc/rc.config.d/nfsconf
and stop/start the daemon.
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start
hope this helps
kenavo
Pat.
Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2009 01:10 AM
02-12-2009 01:10 AM
Re: autofs problem
HI
thanks for reply
at client
thorugh showmount -e i am able to see the exported drive
at client rpcinfo out put is as below.
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100007 2 tcp 1027 ypbind
100007 2 udp 1026 ypbind
100007 1 tcp 1027 ypbind
100007 1 udp 1026 ypbind
100029 1 udp 805 keyserv
100024 1 udp 836 status
100024 1 tcp 838 status
100021 1 tcp 4046 nlockmgr
100021 1 udp 4046 nlockmgr
100021 3 tcp 4047 nlockmgr
100021 3 udp 4047 nlockmgr
100021 4 tcp 4048 nlockmgr
100021 4 udp 4048 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 4049 nlockmgr
100099 1 udp 2155 automountd
100001 2 udp 1035 rstatd
100001 3 udp 1035 rstatd
100001 4 udp 1035 rstatd
395183 1 tcp 1045
395180 1 tcp 1046
100083 1 tcp 1047 ttdbserver
100068 2 udp 1036 cmsd
100068 3 udp 1036 cmsd
100068 4 udp 1036 cmsd
100068 5 udp 1036 cmsd
100005 1 udp 903 mountd
100005 3 udp 903 mountd
100005 1 tcp 906 mountd
100005 3 tcp 906 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
1342177279 4 tcp 2100
1342177279 1 tcp 2100
in automount log below error
Feb 12 16:48:06 Unable to bind to socket 3
Feb 12 16:48:10 Unable to bind to socket 3
i had enabled -T in nfsconf how to trace it now?
i also restarted nfs.client but it doest help me.
thanks for reply
at client
thorugh showmount -e
at client rpcinfo out put is as below.
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100007 2 tcp 1027 ypbind
100007 2 udp 1026 ypbind
100007 1 tcp 1027 ypbind
100007 1 udp 1026 ypbind
100029 1 udp 805 keyserv
100024 1 udp 836 status
100024 1 tcp 838 status
100021 1 tcp 4046 nlockmgr
100021 1 udp 4046 nlockmgr
100021 3 tcp 4047 nlockmgr
100021 3 udp 4047 nlockmgr
100021 4 tcp 4048 nlockmgr
100021 4 udp 4048 nlockmgr
100020 1 udp 4045 llockmgr
100020 1 tcp 4045 llockmgr
100021 2 tcp 4049 nlockmgr
100099 1 udp 2155 automountd
100001 2 udp 1035 rstatd
100001 3 udp 1035 rstatd
100001 4 udp 1035 rstatd
395183 1 tcp 1045
395180 1 tcp 1046
100083 1 tcp 1047 ttdbserver
100068 2 udp 1036 cmsd
100068 3 udp 1036 cmsd
100068 4 udp 1036 cmsd
100068 5 udp 1036 cmsd
100005 1 udp 903 mountd
100005 3 udp 903 mountd
100005 1 tcp 906 mountd
100005 3 tcp 906 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
1342177279 4 tcp 2100
1342177279 1 tcp 2100
in automount log below error
Feb 12 16:48:06 Unable to bind to socket 3
Feb 12 16:48:10 Unable to bind to socket 3
i had enabled -T in nfsconf how to trace it now?
i also restarted nfs.client but it doest help me.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP