HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NFS startup error - code 3 - interfaces
Operating System - HP-UX
1826337
Members
3912
Online
109692
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
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
12-16-2003 01:52 PM
12-16-2003 01:52 PM
NFS startup error - code 3 - interfaces
Hi,
Forgive me if this is posted twice...I cannot find my original post.
I have an A500 running 11.00 with the 9/03 patch set. I get the following error in rc.log:
Output from "/sbin/rc2.d/S430nfs.client start":
----------------------------
starting NFS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 434
starting up the BIO daemons
/usr/sbin/biod 4
Reading in /etc/exports
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
starting up the AutoFS daemon
/usr/lib/netsvc/fs/autofs/automountd
Running the AutoFS command interface
/usr/sbin/automount
FAILURE CODE: 3
mounting remote NFS file systems ...
"/sbin/rc2.d/S430nfs.client start" FAILED
NIS is bound and runs fine. DNS is also fine. The automounter starts but will not automount a filesystem. I get the same error when I stop/start nfs.client.
One thing about this system that may offer a clue. It has two network interfaces but only one is up. lan0 is 100BT and is down. lan1 is 1000SX and is up, responding, and working well. The IP, netmask, etc. are all correct in hosts, DNS, and NIS, both forward and reverse.
Is there something that I have to tell the automounter to point to this interface?
Or could there be another problem?
How do I figure out the failure code?
Any help is greatly appreciated.
Chris
Forgive me if this is posted twice...I cannot find my original post.
I have an A500 running 11.00 with the 9/03 patch set. I get the following error in rc.log:
Output from "/sbin/rc2.d/S430nfs.client start":
----------------------------
starting NFS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 434
starting up the BIO daemons
/usr/sbin/biod 4
Reading in /etc/exports
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
starting up the AutoFS daemon
/usr/lib/netsvc/fs/autofs/automountd
Running the AutoFS command interface
/usr/sbin/automount
FAILURE CODE: 3
mounting remote NFS file systems ...
"/sbin/rc2.d/S430nfs.client start" FAILED
NIS is bound and runs fine. DNS is also fine. The automounter starts but will not automount a filesystem. I get the same error when I stop/start nfs.client.
One thing about this system that may offer a clue. It has two network interfaces but only one is up. lan0 is 100BT and is down. lan1 is 1000SX and is up, responding, and working well. The IP, netmask, etc. are all correct in hosts, DNS, and NIS, both forward and reverse.
Is there something that I have to tell the automounter to point to this interface?
Or could there be another problem?
How do I figure out the failure code?
Any help is greatly appreciated.
Chris
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2003 09:20 PM
12-16-2003 09:20 PM
Re: NFS startup error - code 3 - interfaces
Chris,
I don't think it's lan-interface problem. If all your TCP/IP traffic is running and routes are OK.
You should check settings in the next files:
/etc/rc.config.d/nfsconf (next part)
# automount configuration
#
# AUTOMOUNT = 0 Do not start automount
# AUTOMOUNT = 1 Start Automount.
# AUTO_MASTER = filename of the master file passed to automount
# AUTO_OPTIONS = options passed to automount
#
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
Also the part of AUTOFS is importend, because it tells if you use the new or old version of the automounter.
Check also the /etc/auto_master file.
Another topic is the NIS configuration to check. The auto_mounter man page tells:
The Name Service Switch configuration
file, /etc/nsswitch.conf, determines where the automount command willlook for the maps.
Hope all of this give you a hint to a solution for your problem.
Regards,
Peter
I don't think it's lan-interface problem. If all your TCP/IP traffic is running and routes are OK.
You should check settings in the next files:
/etc/rc.config.d/nfsconf (next part)
# automount configuration
#
# AUTOMOUNT = 0 Do not start automount
# AUTOMOUNT = 1 Start Automount.
# AUTO_MASTER = filename of the master file passed to automount
# AUTO_OPTIONS = options passed to automount
#
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
Also the part of AUTOFS is importend, because it tells if you use the new or old version of the automounter.
Check also the /etc/auto_master file.
Another topic is the NIS configuration to check. The auto_mounter man page tells:
The Name Service Switch configuration
file, /etc/nsswitch.conf, determines where the automount command willlook for the maps.
Hope all of this give you a hint to a solution for your problem.
Regards,
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2003 01:10 AM
12-18-2003 01:10 AM
Re: NFS startup error - code 3 - interfaces
Hi Chris,
This manual describes how to set up autofs
http://www.docs.hp.com/hpux/onlinedocs/B1031-90048/B1031-90048.html
And the t-shooting section has the steps you want to take if the mounts are failing. There is a section for NIS and NFS/Automount.
What you want to do is first check the /etc/rc.config.d/nfsconf directory.
Make sure you set Automount to 1 and Autofs to 1.
Next, you should confirm if you are using local maps in /etc/ for automounter or if you are using the NIS maps for automounter.
For local Maps
Check the /etc/auto_master to make sure your master map is set correctly. The manual has references.
If you are using a NIS map for your automounter maps issue the ypwhich -m and ypcat -k auto.master or ypcat -k auto_master ( the names can be in either format ). Also check the contents of the actual map names.
If your using NIS for your maps make sure the /etc/nsswitch.conf entry for automounter points to NIS. A typical entry is this:
automount: files nis
You can change the order to NIS first / files second etc.
You can also add the +map_name to the /etc/auto_master file. This is going to be whatever is returned from the nis ypwhich command. An example is +auto.master.
When you make changes to autofs you can issues a automount -v to re-read the maps.
Aside from all of this try to mount the same files from the command line that you are trying to mount via Automounter.
Some commands that will help:
# showmount -e NFS_SERVER_NAME
This will show you what is exported from the server.
# rpcinfo -p NFS_SERVER_NAME
This will show you what NFS programs are registered on the NFS server.
# mount nfs_server:/exported_file /local_file
Thats a basic mount command for NFS, see "man mount_nfs" for more details.
Hope this helps,
Todd
This manual describes how to set up autofs
http://www.docs.hp.com/hpux/onlinedocs/B1031-90048/B1031-90048.html
And the t-shooting section has the steps you want to take if the mounts are failing. There is a section for NIS and NFS/Automount.
What you want to do is first check the /etc/rc.config.d/nfsconf directory.
Make sure you set Automount to 1 and Autofs to 1.
Next, you should confirm if you are using local maps in /etc/ for automounter or if you are using the NIS maps for automounter.
For local Maps
Check the /etc/auto_master to make sure your master map is set correctly. The manual has references.
If you are using a NIS map for your automounter maps issue the ypwhich -m and ypcat -k auto.master or ypcat -k auto_master ( the names can be in either format ). Also check the contents of the actual map names.
If your using NIS for your maps make sure the /etc/nsswitch.conf entry for automounter points to NIS. A typical entry is this:
automount: files nis
You can change the order to NIS first / files second etc.
You can also add the +map_name to the /etc/auto_master file. This is going to be whatever is returned from the nis ypwhich command. An example is +auto.master.
When you make changes to autofs you can issues a automount -v to re-read the maps.
Aside from all of this try to mount the same files from the command line that you are trying to mount via Automounter.
Some commands that will help:
# showmount -e NFS_SERVER_NAME
This will show you what is exported from the server.
# rpcinfo -p NFS_SERVER_NAME
This will show you what NFS programs are registered on the NFS server.
# mount nfs_server:/exported_file /local_file
Thats a basic mount command for NFS, see "man mount_nfs" for more details.
Hope this helps,
Todd
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP