Operating System - HP-UX
1834222 Members
2921 Online
110066 Solutions
New Discussion

NFS server not responding boot problem

 
Nick M_1
Frequent Advisor

NFS server not responding boot problem

I have had a boot problem reported on a rp5470 and will go to the computer centre tomorrow to investigate.

The system hasn't come up to multi user mode and it kept putting out a message "NFS server (pid 741@/net) not responding still trying".

An ip address was altered on a GB ethernet card which connects to a VLAN. I have another NIC which has an inet connection, this hasn't changed.

I don't really want to disable the NFS service - except possibly in the short term to get the box to boot.

Any thoughts on how I get the box back into multi user mode and get to resolve the NFS server problem?

Thanks

Nick
4 REPLIES 4
Todd McDaniel_1
Honored Contributor

Re: NFS server not responding boot problem

You are hung till you kill it...

Your box is waiting on the NFS to become available before it will continue with the boot process to multi user mode.

Get the box up then investigate the NFS problem.
Unix, the other white meat.
Todd McDaniel_1
Honored Contributor

Re: NFS server not responding boot problem

IP address shouldnt matter if you have DNS name resolution active...

but might depending on how yoru /etc/resolv.conf file is setup.
Unix, the other white meat.
RAC_1
Honored Contributor

Re: NFS server not responding boot problem

"NFS server (pid 741@/net) not responding still trying".

Makes me think that autmounter is in play here. Is it??

Seems that the nfs server ip was changed and client is not aware of new address.
You need to make the client aware of new ip address. Depending on what you use for name resolution, you will have to change /etc/hosts, dns, nis.

If you are using /etc/hosts, reboot the server, mount everything and correct nfs serve ip address and boot. Problem should go away after this.

Anil
There is no substitute to HARDWORK
MarkSyder
Honored Contributor

Re: NFS server not responding boot problem

I've seen this when entries in one of the NFS files had been hashed out.

If you have access to the NFS server, check the file /var/adm/syslog/syslog.log for any error messages.

Mark Syder (like the drink but spelt different)
The triumph of evil requires only that good men do nothing