nfs server is still responding.

[hpuxhelp]

I would like to disable the nfs server...which file should I look in at ?
when doing bdf, it kept reporting nfs is not responding...
thanks

[Patrick Wallek · Accepted solution]

To stop NFS right now do

# /sbin/init.d/nfs.client stop

# /sbin/init.d/nfs.server stop

# /sbin/init.d/nfs.core stop

Now if you do not want NFS to start next time you reboot the machine, edit the /etc/rc.config.d/nfsconf file so that the following lines are like:

NFS_CLIENT=0
NFS_SERVER=0
PCNFS_SERVER=0

[Shannon Petry]

The solution in your problem, is different than you think. The problem you have with the NFS SERVER NOT RESPONDING error on a bdf command is Not related to itself, unless your mounting a served directory locally, which makes 0 sense unless your testing. Hence, shutting down the NFS server processes on the seat where this error occurs will do no good.

The problem you have is that you have a directory mounted, and that server is not responding. If the server is not responding, you can not un-mount the CD.

Fix this by taking the entry out of /etc/fstab which does the mount of the file system erroring. Then reboot.

Second option is to check the NFS server. If it exists, you can make sure that NFS is running, and then issue a umount command.

Regards,
Shannon

[hpuxhelp]

can you be more specific by "taking out the mount " in the /etc/fstab

[hpuxhelp]

This nfs server is not responding, error message have
prevent us to loginto as root. We connected to the console, but the error message is still on. We can't do a reboot on this, what else can we do ?

[Jeff Schussele]

Hi Dido,

While it's "waiting" on the NFS section of bootup do a ctrl-backslash.
This will break out of the wait loop.
Then edit the nfsconf file as Patrick stated & run shutdown -ry now
to reboot & let all the rc scripts run for a proper boot.

HTH,
Jeff

[hpuxhelp]

However, the problem is that we can reboot this machine...

is there any other way to bypass this problem without having to do a reboot

[Jeff Schussele]

Well, the problem is that the ctrl-backslash stops all further execution of the init scripts - not just NFS.
So sure, if you know which scripts have yet to run - hint...look at an old /etc/rc.log to see just what runs...then you *could* run them manually. A lot of work though......but possible.

Rgds,
Jeff

[Shannon Petry]

First, if you are not familiar enough with UNIX to find a nfs mount in /etc/fstab, then proceed with caution.

First, type this on the command line.

% grep nfs /etc/fstab

You should see something like

somthin:/nfs_export /network nfs defaults 0 0

If you try to use SAM it will try to check the mounts, hanging your shell. You need to manually edit the /etc/fstab file to remove the entry.

For precaution, copy your fstab file to a backup.
% cp /etc/fstab /etc/fstab.bak

% vi /etc/fstab

Now move your cursor over the line that says "nfs" in the third field.
type "dd", press the escape key, press shift+q, type "wq!" press enter.

man vi for more information.

Then you need to reboot. If init was running the mountall command, you can not just stop this command.

Regards,
Shannon

[W.C. Epperson]

This is a universal NFS problem: NFS client still has remote volume mounted after the NFS server is no longer serving it up. Easiest fix without rebooting is to figure out what server and mount point are involved and re-export the mount point at the server (Shannon's instructions on finding the line in fstab should help identify this). At that point you'll be able to "umount " to get rid of the dead mount. Then you can apply Shannon's instructions to make sure you don't have problems with it on reboot.