NFS CLIENT SUBSYSTEM

[Raghuram Ollakal_1]

I have a new HP 9000 N-class server. I was able to finish installing OS Hpux 11.0 on this server and was running fine until yesterday. When I was mounting the CD rom for installing HP nodmanager, the server frezes, and I end up rebooting the server. When I reboot the server it went throuhg all the test and everything and when it reach to the " start NFS client subsystem" it sits there for a long time and says NFS server (pid503@/net) not responding still trying. when I hit the escape key, I got the console Login prompt and I was able to login to the machine. but I am not able to access this server from remotely other than on the console. I can telnet to any other hosts from this server no problem. What is the problem

[Sanjay_6]

Hi,

you will not be able to access the system remotely since the booting process did not complete and you were required to interrupt the boot process. To disable the error during boot, disable the automounter. Edit /etc/rc.config.d/nfsconf and set AUTOMOUNT=1 to AUTOMOUNT=0. then do a init3 or reboot the system. It should boot properly and then you will be able to access the system remotely.

hope this helps.

Regds

[G. Vrijhoeven]

Hi,

Did you look at the /etc/rc.log..

what has FAILED or gave an error. Look at the syslog.log, dmesg . please give more details.

[Uday_S_Ankolekar]

Hi,

Since you don't use NFS it's better to ask system *NOT* to look for NFS
Modify this this file
etc/rc.config.d/nfsconf
and set AUTOMOUNT=1 to AUTOMOUNT=0.

Goodluck.
-USA..

[D. Jackson_1 · Accepted solution]

If you are using NFS, did you update the /etc/hosts, DNS, or NIS database to
reflect the new IP changes? I am assuming that NFS client is hanging at boot
and this hang is an indication that the NFS client is unable to connect to the
NFS server.

If you are not using NFS / Automounter, then there is a need to set the
following variables in /etc/rc.config.d/nfsconf to the following values so that
the NFS client does not hang at boot:

NFS_CLIENT=0
NFS_SERVER=0
AUTOMOUNT=0

Even if you are using NFS and still have trouble with the boot hang, it is best
to turn NFS off. You can restart NFS from the command line:

/sbin/init.d/nfs.server start
/sbin/init.d/nfs.client start


Good Luck
DCJ

[harry d brown jr]

Try starting rpcbind.

Did you use Sept 2001 cd's for install?


live free or die
harry

[Vincent Stedema]

Hi,

Either the driver for your NIC is not installed or the NIC has gone bad. Disabling NFS/automount will take the error away, but you probably still won't be able to access the system from the network.

Are you able to access the system from its secure web console?

Regards,

Vincent

[ramesh_6]

Hi Raghu,

This is possibly the NFS subsystem is hanging because automounter is enabled. It is always a better practice to start the NFS subsystem after the server has come to the run level 3.

More than always have a look at /etc/rc.log for any errors while executing any run control scripts for different run levels.

To start an NFS subsytem

/sbin/init.d/nfs.server start

To stop an NFS subsystem
/sbin/init.d/nfs.server stop

To disable NFS subsytem from starting while boot edit the file /etc/rc.config.d/nfsconf set the following parameters to the following

NFS_ClIENT = 0
NFS_SERVER = 0
AUTOMOUNT = 0

Hope this helps

Ramesh