HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NFS server (pid729@/net) not responding still tryi...
Operating System - HP-UX
1834926
Members
2482
Online
110071
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
04-01-2010 12:07 AM
04-01-2010 12:07 AM
Dear All,
While trying to start ignite backup on my hp-ux I receive this warning:
“WARNING: hostname is an unknown host” and followed by the message
“NFS server (pid729@/net) not responding still trying”
I was reading on some previous threads that I need to change “AUTOMOUNT=1” to 0 in /etc/rc.config.d/nfsconf file.
I still did not try this because it is business critical server so I am waiting for a maintenance window to try this.
My question is, if this is secure operation because I do not have ignite backup and I can not do it write now.
Second question is if there are any additional parameters to check, I am pretty sure that I have some problem with my dns but my /etc/hosts file looks to be ok.
Thank you in advance,
While trying to start ignite backup on my hp-ux I receive this warning:
“WARNING: hostname is an unknown host” and followed by the message
“NFS server (pid729@/net) not responding still trying”
I was reading on some previous threads that I need to change “AUTOMOUNT=1” to 0 in /etc/rc.config.d/nfsconf file.
I still did not try this because it is business critical server so I am waiting for a maintenance window to try this.
My question is, if this is secure operation because I do not have ignite backup and I can not do it write now.
Second question is if there are any additional parameters to check, I am pretty sure that I have some problem with my dns but my /etc/hosts file looks to be ok.
Thank you in advance,
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2010 09:10 AM
04-01-2010 09:10 AM
Solution
I am not sure if this will apply but I had a DNS resolution issue once when trying to take an ignite backup of one of my servers,so here were my steps:
1./etc/rc.config.d/nfsconf
nfs_server=1 (for ignite server)
nfs_client=1 (for ignite client to be backed up)
/sbin/init.d/nfs.server stop/start (ignite server)
/sbin/init.d/nfs.client stop/start (ignite client)
2.uncomment tftp and inetd -c on ignite host (recomment and inetd -c after backup)
3./var/opt/ignite/recovery/archives/clientname (must be hostname of client)
4./var/opt/ignite/clients/MAC address must be the lan that the hostname resolves to. (esp with multiple interfaces configured) also be sure ownership is bin:bin
5.edit etc/exports and add the lines /var/opt/ignite/clients -anon=2 & /var/opt/ignite/recovery/archives/clientname -anon=2 (this makes it for everyone so be sure to unexport when your backup is complete)
6.exportfs -av
7.run your make net recovery command from client
8. when done exportfs -ua
1./etc/rc.config.d/nfsconf
nfs_server=1 (for ignite server)
nfs_client=1 (for ignite client to be backed up)
/sbin/init.d/nfs.server stop/start (ignite server)
/sbin/init.d/nfs.client stop/start (ignite client)
2.uncomment tftp and inetd -c on ignite host (recomment and inetd -c after backup)
3./var/opt/ignite/recovery/archives/clientname (must be hostname of client)
4./var/opt/ignite/clients/MAC address must be the lan that the hostname resolves to. (esp with multiple interfaces configured) also be sure ownership is bin:bin
5.edit etc/exports and add the lines /var/opt/ignite/clients -anon=2 & /var/opt/ignite/recovery/archives/clientname -anon=2 (this makes it for everyone so be sure to unexport when your backup is complete)
6.exportfs -av
7.run your make net recovery command from client
8. when done exportfs -ua
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2010 10:03 AM
04-01-2010 10:03 AM
Re: NFS server (pid729@/net) not responding still trying
From Ignite Server:
showmount -e
What NFS filesystem you are exporting. This should be your image archive directory. It's size should be approximately
( 2 * Clients * 4 GB )
From Client Server
showmount -d
what you are mounting as a client. Should be of the form:
Ignite_Server:/ignite/images/archive/recovery
Paste in these response for further debugging, after you have verified /etc/exports from the server and /etc/fstab from the clients.
showmount -e
What NFS filesystem you are exporting. This should be your image archive directory. It's size should be approximately
( 2 * Clients * 4 GB )
From Client Server
showmount -d
what you are mounting as a client. Should be of the form:
Ignite_Server:/ignite/images/archive/recovery
Paste in these response for further debugging, after you have verified /etc/exports from the server and /etc/fstab from the clients.
Support Fatherhood - Stop Family Law
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