NFS problem ??

[H_17]

I am receiving in the syslog (on HPUX)

Sep 24 11:12:22 lsgpdv01 vmunix: NFS server lpgpdg01 not responding still trying
Sep 24 11:12:47 lsgpdv01 vmunix: bindresvport:loop_twice port assigned 512
Sep 24 11:27:57 lsgpdv01 vmunix: bindresvport:loop_twice port assigned 512
Sep 24 11:29:31 lsgpdv01 vmunix: NFS server lsgpmo01 not responding still trying

I cant access my server from one IP address..however I can access the system using the other IP...Both Lancards are up...and when running bdf it hangs

Any ideas what could be the problem??

[T G Manikandan]

check this doc

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065011111

[T G Manikandan]

I would recommend first to load the latest NFS patches!

[Robert-Jan Goossens]

Hi H,

Take a look at Patch

s700_800 11.04 (VVOS) ONC/NFS General Release/Perf Patch

or for 11.11
http://www5.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_28983&context=hpux:800:11:11

http://www5.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=PHNE_28882

Regards,

Robert-Jan.

[T G Manikandan]

check the patch for 11.0

http://www1.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=PHNE_28567

[Kevin Wright]

try to umount the filesystem that is mounted via nfs, sometimes it seems to work. Bdf is hanging because it cannot contact your nfs server, lpgpdg01.

[Paddy_1]

(a)lsgpdv01 vmunix: NFS server lpgpdg01 not responding still trying

Resolution : While attempting to access the server even though the server system is up. In this case, NFS/TCP onthe server has become inoperable due to a hang.



(b)vmunix: bindresvport:loop_twice port assigned 512

Resolution:
Provide a kernel variable that by default disables these messages. To re-enable these messages, the kernel parameter 'loop_twice_msg' must be set to
one, by patching the vmunix file and rebooting, or by patching the kernel image in memory. To patch the vmunix file (survives a reboot), use this command:
echo 'loop_twice_msg?W 0d1' |
adb -w /stand/vmunix /dev/kmem

To patch the in-memory kernel (does not survive a reboot), use this command:
echo 'loop_twice_msg/W 0d1' |
adb -w /stand/vmunix /dev/kmem

A kernel regeneration will require these steps to be done again.

[Balakumar M]

Hi

Check this link, which is similar to your problem.

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x8f807d4cf554d611abdb0090277a778c%2C00.html&admit=716493758+1064404715632+28353475

Regards,
Bala

[Suresh Patoria]

Hi,

First you pls check in the /etc/hosts
file. check the entry for remote hostname

using the rpcinfo -p command check the locally all the service running

and one more thing, are you able to access that server from the other host.

If not then pls check in the server side check the nfsd, mountd, biod, lockd, statd. these daemons are running or not

issue the rpcinfo -p command to check the which service is register.

Thanx