1825805 Members
2373 Online
109687 Solutions
New Discussion

Re: find issue

 
SOLVED
Go to solution
wish_1
Frequent Advisor

find issue

dear friends,

when i have type
# find / -name sp*.ora -print
NFS server db1 not responding still trying
NFS server db1 not responding still trying

and #(promt) is not coming, even when i type #bdf #(promt) is not coming..

we are using HP-UX 11i with rp 7400 server

Thanks in adv

happy new year

Wish
21 REPLIES 21
Arunvijai_4
Honored Contributor

Re: find issue

Hello,

There may be some problem with the NFs server "db1". Do you have shares from "db1" connected to your rp7400 ? Better option is keeping find to local serverby adding -local

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor

Re: find issue

It is problem with NFS shares from db1 server. Try to search local files only if you don't want to get any error or unmount file systems.

To search local file systems then,

# find / -local -name sp*.ora -print
# bdf -l

will help you out.

-Muthu
Easy to suggest when don't know about the problem!
wish_1
Frequent Advisor

Re: find issue

dear muthu / arun,
in the syslog ie #more /var/adm/syslog/syslog.log its showing

Jan 2 11:09:20 db1 vmunix: NFS server db1 not responding still trying

and when i do #ll and / the prompt in not comming only...

do i need to stop and start NFS server if so, how to do... please tell its URGENT!!!

Thanx

Wish
Arunvijai_4
Honored Contributor

Re: find issue

Yes, you can stop/start the NFS server "db1". Or it could be some network issues, Just check you are able to ping to "db1"

You can stop and start NFS servers by,

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

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

-Arun

http://forums1.itrc.hp.com/service/forums/helptips.do?#28
P.S Kidly remember to assign points.
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor

Re: find issue

If you are logged in db1 machine then,

# /sbin/init.d/nfs.client stop (If required)
# /sbin/init.d/nfs.client start

# /sbin/init.d/nfs.core stop (Must)
# /sbin/init.d/nfs.core start

# /sbin/init.d/nfs.server stop (must)
# /sbin/init.d/nfs.server start

Now try to check syslog and showmount command output for nfs status.

-Muthu
Easy to suggest when don't know about the problem!
Cem Tugrul
Esteemed Contributor

Re: find issue

hi wish,

the following commands also as Arunvijai mentioned for to stop/start command your
nfs consept

/sbin/init.d/nfs.core stop
/sbin/init.d/nfs.core start
/sbin/init.d/nfs.server stop
/sbin/init.d/nfs.server start

also visit the link below;
http://docs.hp.com/en/5991-1811/ch02.html#cihbhchj

Good Luck,
Our greatest duty in this life is to help others. And please, if you can't
wish_1
Frequent Advisor

Re: find issue

dear muthu / arun,

in the syslog ie #more /var/adm/syslog/syslog.log its showing

Jan 2 11:09:20 db1 vmunix: NFS server db1 not responding still trying

and when i do #ll and / the prompt in not comming only...

I WANT TO KNOW SHOULD -- > i need to stop and start NFS server, WILL THIS SOLVE MY PROBLEM.

Thax and regards,
Wish
Muthukumar_5
Honored Contributor

Re: find issue

yes. IT will solve the problem. Nfs server is not running there.

-Muthu
Easy to suggest when don't know about the problem!
Muthukumar_5
Honored Contributor

Re: find issue

see man page of nfs(7).

--- man 7 nfs ---

If the server is down or inaccessible, the client receives the message:

NFS: file server not responding: still trying.

The client continues resending the request until it receives an acknowledgement from the server. Therefore, the server can crash or power down, and come back up without any special action required by
the client. The client process requesting the I/O will block, but
remains sensitive to signals (unless mounted with the nointr option)
until the server recovers. However, if mounted with the soft option,
the client process returns an error instead of waiting indefinitely.

Answer: Restart nfs.server and nfs.core available in /sbin/init.d/ directoy.

-Muthu
Easy to suggest when don't know about the problem!
Arunvijai_4
Honored Contributor

Re: find issue

Hi Wish, Make sure you are able to reach "db1" by pinging it. If you are able to ping to "db1" , then its a problem with NFS server. Restarting NFS server will solve your problem.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor
Solution

Re: find issue

Another cause of this problem is bcas of heavy load in nfs server access. What is the configuration you are using in /etc/rc.config.d/nfsconf file?

grep -Ev '^$|^#' /etc/rc.config.d/nfsconf

post this.

More related threads:

http://www1.itrc.hp.com/service/james/search.do?todo=search&admit=-682735245+1136191171824+28353475&searchtext=NFS+server+not+responding+still+trying&from=forums&origin=0&wpa=forums1.itrc.hp.com%3A80&searchcategory=ALL&hpl=1&searchcriteria=allwords&rn=25&source=7000&presort=rank&chkServStor=on&esc=support.itrc.hp.com

-Muthu
Easy to suggest when don't know about the problem!
wish_1
Frequent Advisor

Re: find issue

dear Muthukumar

i have done following but -- problem is still there

# /sbin/init.d/nfs.core stop
stopping rpcbind
# /sbin/init.d/nfs.core start
starting NFS CORE networking

starting up the rpcbind
/usr/sbin/rpcbind
# /sbin/init.d/nfs.server stop
killing nfsd
killing rpc.mountd
# /sbin/init.d/nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 3101
exportfs error: /maharaja/praxisdmp: No such file or directory
Reading in /etc/exports
starting up the mount daemon
/usr/sbin/rpc.mountd
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 721
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 727

any other clu

Thax & regds
wish
Arunvijai_4
Honored Contributor

Re: find issue

Hi Wish, How many NFSD can be run from your server ? Check with /etc/rc.config.d/nfsconf
and post your information.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor

Re: find issue

Remove the /etc/exporfs file for the content of /maharaja/praxisdmp.

Do this steps,

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

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

Do this steps. Post these:

a) /etc/rc.config.d/netconf file contents.
b) mount
c) exportfs -v
d) showmount

after doing above steps.


-Muthu
Easy to suggest when don't know about the problem!
wish_1
Frequent Advisor

Re: find issue

Dear Muthu,

pl find the attachment

thanx and regards
wish
Muthukumar_5
Honored Contributor

Re: find issue

Is nfsd running in console?

# ps -ef | grep nfs

What are you getting for this:

# grep -Ev '^$|^#' /etc/rc.config.d/nfsconf
# showmount -ede

Are you still getting same errors?

Which file system you are trying to mount in remote NFS clinet?

-Muthu
Easy to suggest when don't know about the problem!
wish_1
Frequent Advisor

Re: find issue

dear Muthu,

# grep -Ev '^$|^#' /etc/rc.config.d/nfsconf
NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=16
NUM_NFSIOD=16
PCNFS_SERVER=0
LOCKD_OPTIONS=""
STATD_OPTIONS=""
MOUNTD_OPTIONS=""
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
START_MOUNTD=1
AUTOFS=1
AUTOMOUNT_OPTIONS=""
AUTOMOUNTD_OPTIONS=""
# showmount -ede
export list for finess_p:
/var/opt/ignite/clients (everyone)
/praxis_dump
#

yes, bdf / ll / ls -l still are in hung
do i need to restart the server if so will there be any problem.

thanx and Regards
vishal
Arunvijai_4
Honored Contributor

Re: find issue

Hello,

Post the content of /etc/rc.config.d/nfsconf
You have posted netconfig, which is not required per se.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor

Re: find issue

I hope bdf / ls -l is getting hung on NFS client right?

Try to restart nfs.client in client side.

Remove the mount which mounted from db1 server as,

# umount

I hope bdf and ls -l is working on server side.

-Muthu
Easy to suggest when don't know about the problem!
Muthukumar_5
Honored Contributor

Re: find issue

In NFS Server Side:

Export the file system:

# exportfs -iv -o root=

In NFS Client Side:

# mount -p

Remove the already mounted file system from NFS server with umount command.

Remount as,

# mkdir
# mount NFSSErver:

Are you still getting problem in nfs client side. Please ellaborate back where you are getting errors or issues?

-Muthu
Easy to suggest when don't know about the problem!
Bill Hassell
Honored Contributor

Re: find issue

I would always assume that your NFS server is dead and remove the NFS mountpoint first. This will stop the hang condition for your commands. NFS is not a reliable connection for a production machine, especially if you share the network with PCs or the network is overloaded. Is the NFS server providing data to any otgher machines? If so, are they having problems too? Get the server working first, then see if your local machine can get the connection established.


Bill Hassell, sysadmin