NFS server HP-UX not responding still trying

[Engo Armand-Blaise]

While shujtting the server down (shutdown -y 0), this above message appears on the screen.

I reboot the server and while installing the Oracle 8i, it was cancelled because of this message again.

What can I do? To reboot the Server and remove the Oracle 8i?
Thanks.

[Pete Randall]

Have there been recent changes to the hostname, /etc/hosts, /etc/nsswitch.conf, /etc/resolv.conf, the dns server, or the nis server?

Pete

[Kent Ostby · Accepted solution]

You can do the following:

1) boot into single user mode (see document OZBEKBRC00000607 for details).

At this point only / and /stand will be mounted.

2) Mount /usr and /var:
mount /usr
mount /var

3) From there you could use vi to either comment out the NFS filesystems in /etc/fstab or turn off the NFS_SERVER and NFS_CLIENT in /etc/rc.config.d/nfsconf.

4) Then reboot and the system should come up without NFS issues.

[V. Nyga]

Hi,

check your /etc/fstab for entries like:
{server_name}:/dir /dir nfs ...

The nfs-server {server_name} must be aviable (ping ...).

Regards
Volkmar

[Engo Armand-Blaise]

There were no changes related to the hostname and the file /etc/hosts. Also, I don't have a file like /etc/nsswitcvh.conf or /etc/resolv.conf...

What I know is I installed "SAMBA" last week and when I shutdown the server, this problem apeears. What I've really done after is the run the command "init 0" and switch the power off... After all, I've switch the power one and use the Web Console... I'm still oberving if this message error will appear again.

[Engo Armand-Blaise]

To you all,

I'm still busy the check your suggstion. In the mean time. this what I've found when executing "ps -edf | grep nfs" :

cyb_hpux [ / ] # ps -edf | grep nfs
root 512 0 0 15:30:15 ? 0:00 nfskd
root 1021 1 0 15:30:51 ? 0:00 /usr/sbin/nfsd 4
root 1027 1021 0 15:30:51 ? 0:00 /usr/sbin/nfsd 4
root 1022 1021 0 15:30:51 ? 0:00 /usr/sbin/nfsd 4
root 1025 1021 0 15:30:51 ? 0:00 /usr/sbin/nfsd 4


=======================================

Is it normal?

[Stanimir]

Hi!
In addition for all above also:
Try to identify what is this NFS-servers.
May be you could remove some entries from
/etc/exports there. Look at sam-section:
sam > network & communications > NFS
for NFS-configuration.
Regards

[Kent Ostby]

Yes.

That is standard.

What do you get from output from:

grep nfs /etc/fstab

grep NFS /etc/rc.config.d/nfsconf

?????

[Helen French]

This error message is little misleading some times. What you have to verify is how your NFS is setup first. Check the /etc/exports and etc/rc.config.d/nfsconf files. If you have any NFS mounts configured, then make sure that you have the server and client communicating properly and all nfs daemons are running on both sides.

I 've seen this message during an Oracle installation just becuase the Oracle install media was bad. Check this too. Try installing from another media. If this is not the case, then either disable nfs temporarily (by editing /etc/rc.config.d/nfsconf) or resolve the nfs errors

[Engo Armand-Blaise]

the only entries I have from the file "/etc/fstab" are :

# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /devpt vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /tmp vxfs delaylog 0 2
/dev/vg00/lvol8 /usr vxfs delaylog 0 2
/dev/vg00/lvol9 /var vxfs delaylog 0 2
/dev/vg01/lvol1 /cyborg vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol2 /support vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol3 /consult vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
===========================================

Also the file "/etc/export" does not exist..

===========================================

Result from "grep NFS /etc/rc.config.d" :

cyb_hpux [ / ] # grep nfs /etc/rc.config.d
???emsagtconf?? ??crashconfZ?? ??savecrashce8nfsconf.Zm??
predictiv???sambaconf.Zsavecrash.Znfsconf.ZSnmpMaster.Zonswconfig.Zhpbase100conf.Z
predictive.Zf.


It seams to have a corrupted file. Isn't it?

[Engo Armand-Blaise]

Sorry I forget to check if NFS is in nfsconf file :

cyb_hpux [ /etc/rc.config.d ] # grep NFS nfsconf
#********************** NFSCONF ******************************
# NFS configuration. See nfsd(1m), mount(1m), pcnfsd(1m)
# NFS_CLIENT: 1 if this node is an NFS client, 0 if not
# NFS_SERVER: 1 if this node is an NFS server, 0 if not
# both or neither! This system is an NFS client if you will
# be NFS mounting remote file systems; this system is a server
# NUM_NFSD: Number of NFS deamons (nfsd) to start on an NFS server. Four
# NUM_NFSIOD: Number of NFS BIO daemons (biod) to start on an NFS client.
# PCNFS_SERVER: 1 if this node is a server for PC-NFS requests. This
NFS_CLIENT="0"
NFS_SERVER=1
NUM_NFSD=4
NUM_NFSIOD=4
PCNFS_SERVER=0

[Kent Ostby]

I would edit the NFS_SERVER entry in /etc/rc.config.d/ and sent that value to 0 until after the Oracle installation.

Also, you noted that /etc/export does not exist, but the actual file name is /etc/exports (with an "s" on the end).

[V. Nyga]

Hi Engo,

1. grep nfs /etc/rc.config.d looks similar at my system.
Change to /etc/rc.config.d and do a grep nfs * and grep NFS *. The result is better. Maybe you will find something with 'samba'.
2. Change NFS_CLIENT="0" to NFS_CLIENT=0 and NFS_SERVER=1 to NFS_SERVER=0.

Regards
Volkmar

[Helen French]

From the nfsconf file, it's clear that you 've enabled nfs server services on this system. You can replace the "1" with a "0" to disable this as written on the file itself. Also you need to stop the running services too.

[Engo Armand-Blaise]

Can not kill two processes :

1. nfs
2. jre (which is still running)

TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
? 2556 oracle 152 20 30816K 57944K run 33:30 2.12 2.12 jre
?


=============================================

[Gerard Leclercq]

I suggest you to check your LAN cable connexions, the message "NFS server xxxx not responding still trying" is typical for a bad wire connexion